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" error when submitting integration options

See original GitHub issue

Installation details

Description	Value
HACS version	1.03
Home Assistant version	0.110.3
Installation method for HA	HA Image / RasPi

Checklist

[ X] I’m running the newest version of HACS https://github.com/hacs/integration/releases/latest
[X ] I have enabled debug logging for my installation.
[X ] I have filled out the issue template to the best of my ability.
[X ] I have read https://hacs.xyz/docs/issues
[X ] This issue is related to the backend of HACS.
[X ] This issue only contain 1 issue (if you have multiple issues, open one issue for each issue).

Describe the issue

Cannot change any integration options for HACS. When clicking submit, receive “User input malformed” error.

Steps to reproduce

Navigate: HA Configuration --> Integrations --> HACS card --> Options
Change any value (or don’t) and click “submit”.

Current values Side panel title:
Side panel icon: Number of releases to show: 5 Filter with country code: ALL Enable AppDaemon apps discovery & tracking: unchecked Enable NetDaemon apps discovery & tracking: unchecked Enable debug: checked Enable experimental features: checked

Debug logs

Logs


None generated around this error

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:9 (1 by maintainers)

Top GitHub Comments

2reactions

nathan-marchcommented, Jul 1, 2020

I also ran into this on 1.1.2 was able to fix it by settings and unsetting netdaemon support. Looks like the default value is set to null rather than false, which results in a 400 error from the backend (and no errors logged).

1reaction

flozsccommented, Jul 3, 2020

I also ran into this on 1.1.2 was able to fix it by settings and unsetting netdaemon support. Looks like the default value is set to null rather than false, which results in a 400 error from the backend (and no errors logged).

Thanks! Solved it by checking everything and entering values in all text boxes. Then I could save and also disable everything that I don’t need again.

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 in ......

Input is malformed. Reason: Could not get entity details for ...

The Pipeline executes successfully on first run. Once the ADF is refreshed it fails with below error. Input is malformed. Reason: Could not...

HA Configuration Fails Error Message

On uninstalling / reloading the Integration, I continue to receive the following error message: "User input malformed: extra keys not allowed @ data['8']"....

How to Fix a 400 Bad Request Error (Causes and Fixes) - Kinsta

1. Check the Submitted URL · 2. Clear Browser Cache · 3. Clear Browser Cookies · 4. File Upload Exceeds Server Limit ·...

ignore_malformed | Elasticsearch Guide [8.5] | Elastic

Sometimes you don't have much control over the data that you receive. One user may send a login field that is a date...