Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
User Input Malformed
See original GitHub issueAdding the component with all entities works but trying to select only specfic sensors to add I get a User Input Malformed errors
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
HomeKit error "User input malformed" - Configuration
"User Input Malformed" error when re-configuring integrations in the front end GUI ... fgonza2: the issue, is that if a non-existing entity was...
Read more >"User Input Malformed" error when re-configuring integrations ...
I'm experiencing the same on my integration. Removing the config entry through the UI and re-setting it up works. First time setup works....
Read more >HA Configuration Fails Error Message
"User input malformed: extra keys not allowed @ data['8']". My HA has just been updated to 2021.12.1. Any thoughts or help?
Read more >After updating to latest Home Assistant the HomeKit ... - Reddit
After updating to latest Home Assistant the HomeKit integration can't save: "User input malformed". Suggestions?
Read more >Input is malformed. Reason: Could not get entity details for ...
Input is malformed. Reason: Could not get entity details for pipeline6. If this entity is a linked service, please ensure it has been...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
an unsupported work around would be to edit the
.storage/core.config_entitiesto your liking… changes there also require a restart of home-assistant once saved. use at your own risk. that being said… it worked for me. 😃2021.11.3 fixed this for me