User input malformed

[SeLLeRoNe]

Version information:

1.0.14
HA core-2021.11.0b2

Description:

This is from console:

POST https://HOST/api/config/config_entries/options/flow/795dd180c8ba4de585a5d8ad13c29162 400
I @ styles.ts:365
(anonymous) @ styles.ts:365
callApi @ styles.ts:365
s @ ha-card.ts:5
value @ step-flow-form.ts:69
handleEvent @ styles.ts:365

This is the POST payload:

{lights: ["21"], prefer_rgb_color: false, initial_transition: 1, transition: 45, interval: 90,…}
detect_non_ha_changes: true
initial_transition: 1
interval: 90
lights: ["21"]
0: "21"
max_brightness: 100
max_color_temp: 5500
min_brightness: 1
min_color_temp: 2000
only_once: false
prefer_rgb_color: false
separate_turn_on_commands: false
sleep_brightness: 1
sleep_color_temp: 1000
sunrise_offset: 0
sunrise_time: "None"
sunset_offset: 0
sunset_time: "None"
take_over_control: true
transition: 45

Which returns:

{"message": "User input malformed"}

Hope I've provided enogh information, if not, please feel free to ask.

Thanks
Andrea

[jk1993]

Having the same issue. Assumed it was something related to the beta. Think the workaround for this integration is to use yaml for the config. That seems to work, but would be nice to be able to set it up in the UI

[DTTerastar]

I saw this in 2021.11.0b4

[SeLLeRoNe]

Yes it started with the latest beta

[sambarlick]

I also have this issue, experienced it on 2021.119b3 and 4 and 5.

[luisleonardo]

Same here since 2021.11.0b1 and also with Passive BLE monitor.

[stevenjev]

Also noticing this error using the release version of 2021.11

[felix63]

I have the same issue. It also occurs in other custom integrations such as 'Magic Area'

[sambarlick]

I think this might have something to do with the new drop down list. It's the only thing I can think of that's changed in n 2021.11.

…

On Fri, 5 Nov 2021, 10:58 felix63, ***@***.***> wrote: [image: Schermafbeelding 2021-11-05 om 00 55 29] <https://user-images.githubusercontent.com/16501940/140436326-d8567314-72c5-4845-b975-52e77c4c2796.png> I have the same issue. It also occurs in other custom integrations such as 'Magic Area' — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALKDPDAVFWJWWNF7FXTMTM3UKMM3RANCNFSM5HA4LFOA> . 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>.

[SeLLeRoNe]

Yep, I believe so @sambarlick

[thomclae33]

Same issue. 😢

[pnm1977]

I've also got this issue. Updated to core-2021.11.1 and lost ability to add new rooms or edit existing ones through the integration option.

[maccident]

+1 Same "User input malformed" issue.

[oksibutch]

+1 have a problem too

[de-Techneut]

+1 Same here, tried to delete some lights, now I also have "User input malformed". Deleting the integration and re-adding it, does not solve it.

[randomlyalex]

Following this as i have the same issue, and also have it with programmable thermostat which is using the same input fields maybe?

[basnijholt]

I have looked into it, but cannot figure out what changed. Even HomeKit is generating these errors: https://community.home-assistant.io/t/homekit-error-user-input-malformed/353390

[randomlyalex]

I couldnt see an issue in the front end related to this, and its across many integrations, so either some kind of breaking change update needs releasing so people can adapt, or there is a bug in the front end and it needs looking it :)

[poelzi]

When I open the light dropdown menu does not have the entries selected which are written in the field. Toggeling the checkbox adds an aditional entry, so there is definitily also some desync happening.

[bgreet]

Having same issue. Integration no longer works if adding anything new from the UI

[andrewfitz]

Same issue, broke on update to 2021.11 from 2021.10.6, or from enabling hue groups support.

[LEJOUI]

Same issue was found in the ble custom component. He found a solution, might be helpfull?

[SeLLeRoNe]

So it seems to be something related to how the data payload is sent?
Should be dictionary but it is list instead?

[Boggie]

Is it cause by frontend bug in HA?
home-assistant/frontend#10567

[SeLLeRoNe]

It could be but hasn't been picked up by HA Staff yet

[liudger]

home-assistant/frontend#10585
it looks like this is the issue?

[basnijholt]

Great, a fix has just been merged by @bramkragten, I imagine it will make it to the next patch release.

[lucasfr]

When is the next patch release expected to happen?

[Syfaro]

After upgrading to Home Assistant 2021.11.3, it seems to work again.

[poelzi]

Strange, I can not even select any entry anymore, the whole selection box is missing. Pressing save still causes the error message.

[SeLLeRoNe]

Confirmed to be fixed by 2021.11.3 that includes the related Frontend updates: home-assistant/core#59451

[poelzi]

Ok, I see the problem now. It is not completly fixed:
I had a lamp which was controlled by adaptive lighting. I then renamed this lamp and created a light group of the same name as the old lamp was.
The old entry is now still shown as selected in the combo box, but the entry does not actually exist anymore to select. This causes the malformed data to be sent. It is not possible to deselect the now not shown entry, causing the dialog to be broken with no way to fix it.

[SeLLeRoNe]

I had the same, but not related to this issue.
It's a bug but a different one.
To fix I had to remove that specific ntegration and add it back.

[poelzi]

I opened #10608 for that. Yes, I think it's a different problem that is partially related