-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Checklist
- I have updated to the latest available Home Assistant version.
- I have cleared the cache of my browser.
- I have tried a different browser to see if it is related to my browser.
- I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
got error when adding an automation in home assistant "Message malformed: not a valid value for dictionary value @ data['type']"
I had tried to rename the automation when first saving it.
I couldn't save it initially... so started over, and this time i let the name default and then i could save it, and then i could rename it.
so it only seems to happen when initially creating it and giving it a new name on the initial create.
Describe the behavior you expected
no error when saving with non-default tname
Steps to reproduce the issue
1.create new automation
2. set When to: When the time is equal to 5:00 AM on Monday, Wednesday, or Friday
3.Then do: When the time is equal to 5:00 AM on Monday, Wednesday, or Friday
4.Then: Delay for 30 seconds
5.Then: Switch 'Turn on' on Smart Plug - living room - tv
6.then change the name from the default to: Reboot TV
Then try to save it... and get the error.
Drop above step 6 and it works with no error, and then can rename it with no error
What version of Home Assistant Core has the issue?
Installation method Home Assistant OS Core 2025.10.2 Supervisor 2025.10.0 Operating System 16.2 Frontend 20251001.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue?
Windows Edge Version 141.0.3537.57 (Official build) (64-bit)
Which operating system are you using to run this browser?
Windows 11
State of relevant entities
This was for a Minoston z-wave mini plug 800s MP31Z, using ZWA-2 for the zwave
Problem-relevant frontend configuration
I didn't really do these steps:
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
JavaScript errors shown in your browser console/inspector
Additional information
No response