MQTT: Payload is not supported

[dahelles]

The problem

After adding adapters of type "NEXENTRO Blinds Actuator" (Manufacturer Insta, model 57008000 I get the following error in HA logs:

Logger: homeassistant.components.mqtt.cover
Source: components/mqtt/cover.py:415
integration: MQTT (documentation, issues)
First occurred: March 14, 2024 at 10:44:30 PM (2407 occurrences)
Last logged: 9:55:07 PM

Payload is not supported (e.g. open, closed, opening, closing, stopped): None

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MQTT

Link to integration documentation on our website

https://www.home-assistant.io/integrations/mqtt

Diagnostics information

config_entry-mqtt-314a35b91e9e6810e928a920d0555e15.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Has never worked, started with those a few months (releases) ago. Tried with several ZigBee Coordinators (Sonoff Dongle P, SkyConnect, now SLZB-06

[home-assistant]

Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

[jbouwh]

The None is text, possible rendered from a value template. This is the info Mqtt receives, and it is not a valid state, so that will cause an error being logged.
If the device dies not work at all, please contact the developer of the integration that is supplying the Mqtt entity.

[dahelles]

Thanks for your support! Let me ask to better understand your feedback.

So this is a Zigbee shutter relay. I added it to HA via Zigbe2Mqtt, so I assume "the integration that is supplying the Mqtt entity" is then the Zigbe2Mqtt add-on, right?

If so, I have already addressed this issue there but did not get any response yet. See Koenkk/zigbee2mqtt#21812

Do you think there is anyhthing I can do better or in addition? Since the error is flooding my logs when adding more of these relays (I have 17 of them in my house), this is completely blocking the build-up of my zigbee network.

[jbouwh]

Ah okay, I understand. If there is no state to report a value template could return an empty string instead of a "None" string, this would stop the warnings.

[dahelles]

I have not created such a value template myself. So this must have come with addition of the device. So are you saying I should adjust this template? If so, where could I find it?

[jbouwh]

It must be added byZ2M somewhere.

[ercsey]

I have almost the same error with the Aqara ZNCLDJ14LM cover motor.

Payload is not supported (e.g. open, closed, opening, closing, stopped): stop

[jbouwh]

I have almost the same error with the Aqara ZNCLDJ14LM cover motor.

Payload is not supported (e.g. open, closed, opening, closing, stopped): stop

In such a case a value template can be used to ensure a supported payload is rendered. This is not an issue with Home Assistant MQTT. Please address this issue at the Zigbee2Mqtt.

[dahelles]

Please allow one more question to the topic of value templates and the reference to #117813:

• I already addressed this topic to Z2M over 2 months ago, but without any response yet (see Nexentro Shutter relay: Payload is not supported  Koenkk/zigbee2mqtt#21812). Is there any way I can help myself here?

• I don't really understand the content of the mentioned reference Consequently ignore empty MQTT state payloads and set state to unknown on "None" payload #117813 despite reading carefully, as I am not used to CI/CD practices and Github. Does that mean a "fix" is on the way? Sorry for this dumb question.

Not to forget: Many thanks for your quick and patient replies!

[jbouwh]

Please allow one more question to the topic of value templates and the reference to #117813:

* I already addressed this topic to Z2M over 2 months ago, but without any response yet (see [Nexentro Shutter relay: Payload is not supported  Koenkk/zigbee2mqtt#21812](https://github.com/Koenkk/zigbee2mqtt/issues/21812)). Is there any way I can help myself here?

As a developer you can help. I am not a user of Z2M at the moment.

* I don't really understand the content of the mentioned reference [Consequently ignore empty MQTT state payloads and set state to `unknown` on "None" payload #117813](https://github.com/home-assistant/core/pull/117813) despite reading carefully, as I am not used to CI/CD practices and Github. Does that mean a "fix" is on the way? Sorry for this dumb question.

Actually this will solve the warnings in your case as a "None" payload will be assumed to reset the state to unknown without warnings in the logs.

Not to forget: Many thanks for your quick and patient replies!

[dahelles]

How can I spot when this "fix" will be part of a new vesion?

[jbouwh]

How can I spot when this "fix" will be part of a new vesion?

Fixed wel be the logged warnings. You could install the beta version of Home Assistant

[dahelles]

Prefer to wait for stable version as this shall be the foundation for complete new installation that is meant to last. Can I see it somehwhere on GitHub when this will be part of a regular HA Release or am I misunderstanding the process here entirely?