Moes UFO-R11 - No converter available for 'state' ("ON")

[DKanarsky]

Description of the issue

After successful connection UFO-R11 the switch control related to the device is created in Homeassistant . But trying to turn on or turn off the switch results in error message in zigbee2mqtt add-on:

No converter available for 'state' ("ON")
or
No converter available for 'state' ("OFF")

The switch control activates learning IR codes. Sending messages using MQTT service works as expected

Addon version

1.33.0-1

Platform

Core: core-2023.9.1
Supervisor: supervisor-2023.08.3
Operating System: HassOS 10.5

Logs of the issue (if applicable)

No response

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[marspd]

Description of the issue

After successful connection UFO-R11 the switch control related to the device is created in Homeassistant . But trying to turn on or turn off the switch results in error message in zigbee2mqtt add-on:

No converter available for 'state' ("ON") or No converter available for 'state' ("OFF")

The switch control activates learning IR codes. Sending messages using MQTT service works as expected

Addon version

1.33.0-1

Platform

Core: core-2023.9.1 Supervisor: supervisor-2023.08.3 Operating System: HassOS 10.5

Logs of the issue (if applicable)

No response

Hi there
Did you ever find a fix for this at all? I have the same issue.
Regards
Paul

[DKanarsky]

No. My workaround is to use Homeassitant mqtt.publish service with payload according to the device documentation there. It worked for me.

[marspd]

Thanks for the reply, that's what I did on the end myself.

[alienatedsec]

Maybe this should be reopened whenever possible as it is still an issue on 1.36.1 @Koenkk

[dwellexity]

This is still an issue. UFO-R11 can not learn codes through home assistant interface. Activating the learning mode directly from z2m web interface works without any issues.

[Koenkk]

Could you provide me:

• The debug log when starting z2m and waiting for 15 seconds
• The debug log when triggering this from the z2m frontend.
  See this on how to enable debug logging.

[dwellexity]

I have attached the log here.
log.log
@Koenkk Thank you for your efforts.

[Koenkk]

Fixed the issue!

Changes will be available in the dev branch in a few hours from now.

[dwellexity]

Thanks @Koenkk. The fix works.
However, there is still an issue. If the learned IR code is a bit too long, the HA web interface doesn't show the full code, which makes the learning process useless. If I go into Zigbee2MQTT web interface, the full code is available there without any need to learn it again.
Is it something that can be solved?

[Koenkk]

@dwellexity how long is it? The HA limit is 254 chars.

[dwellexity]

@Koenkk I got this for an AC remote -
H5YBVQNlAC8MigDgCVUD4AlEBDIIMghEBEQE4AlkFKIGBWQUMghkFOADB0ALwAMTMggvDCEBswUyCCEBPQJEBD0C4AlAGx/gCUQElgGiBkQECAIyCLMFuwKKADIIlgEyCAgCCAI9AgezBZYBVQO7AkA9EaIGPQIIAiEB//81I2QUCAIIAkAPAD1gAQcIArsClgG7AkAJAD2gAQKiBgggA8AHA7sCswVACwO7AqIGQAcJPQIIAj0Coga7AkAHQAMFogY9AggC4AMPgAsBogZAAwIIAj0gAQOiBrsCgEcJCAJGmjUjMgg9Ag==
It has 312 characters.

[Koenkk]

So I don't think this can be solved, as the limit for HA is 254 chars.