"User input malformed" when re-configuring interation

[felix63]

Can not edit options anymore since upgrading to core-2021.11.0. Multi-selects specifically doesn't work. Gives 'User input malformed'. Similar issue in other custom integrations, see https://github.com/basnijholt/adaptive-lighting/issues/213

System Health

version	core-2021.11.0
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.9.7
os_name	Linux
os_version	5.11.0-37-generic
arch	x86_64
timezone	Europe/Amsterdam

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	4747
Installed Version	1.16.0
Stage	running
Available Repositories	889
Installed Repositories	41

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	failed to load: timeout

Lovelace

dashboards	5
resources	28
views	22
mode	storage

Spotify

api_endpoint_reachable	ok

[jseidl]

Yeah that's pretty unfortunate. Also some multi-selects became checkboxes... sigh... will work on this issue this Sunday.

[jseidl]

        vol.Optional(
            CONF_PRESENCE_DEVICE_PLATFORMS,
            default=DEFAULT_PRESENCE_DEVICE_PLATFORMS,
        ): cv.ensure_list,
        vol.Optional(
            CONF_PRESENCE_SENSOR_DEVICE_CLASS,
            default=DEFAULT_PRESENCE_DEVICE_SENSOR_CLASS,
        ): cv.ensure_list,

These two options are declared the same way and one renders as checkboxes and one as a multi select 🤷

[felix63]

Watching the launch party I remember hearing that depending on the number of items there would be a difference how a list would be shown. Could that be the case here?

…

Op 7 nov. 2021, om 06:12 heeft Jan Seidl ***@***.***> het volgende geschreven: vol.Optional( CONF_PRESENCE_DEVICE_PLATFORMS, default=DEFAULT_PRESENCE_DEVICE_PLATFORMS, ): cv.ensure_list, vol.Optional( CONF_PRESENCE_SENSOR_DEVICE_CLASS, default=DEFAULT_PRESENCE_DEVICE_SENSOR_CLASS, ): cv.ensure_list, These two options are declared the same way and one renders as checkboxes and one as a multi select 🤷 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#150 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD54ZNHHSMQF3RX5MJI33MDUKYKGLANCNFSM5HMVGI7Q>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jseidl]

Hmmm, possibly. That sucks, the config menu will be a mess... sigh. Still investigating this issue.

[felix63]

Is related to home-assistant/frontend#10567 (comment)

[jseidl]

Seems to be resolved in latest HA Frontend update. Still would prefer a way to enforce selects instead of checkboxes.

[jseidl]

Spoke too soon. Worked when I first updated but now it's giving me the same error when I'm trying to update areas.

[jseidl]

Weird thing if you delete the area, restart and configure the area, it works fine. If you try to re-configure the area, it gives User Input Malformed. Need to dig further.

[jseidl]

Original bug seems to be partially fixed. Remainder seems related to home-assistant/frontend#10608

[felix63]

Closing this one as it is being fixed frontend.