I’m using zigbee2mqtt and all those properties are available, so it’s somehow an issue with OH, as it can’t discover the device properly. As I’m new there, I don’t know all the OH capabilities. Is there a way to add a thing manually, with its all configuration?
I have the exact same issue.
OH discover the thing with all the possible channels.
But OH doesn’t activate alle the channels.
I have this issue since Upgrade to OH 4.x (from 3.x).c
It only appears in combination with the “HomeAssistant MQTT Components Binding”.
Manually configured mqtt things (config file) are working as expected and rock solid.
All topics are available. So its not an issue with the mqtt broker…
Why OH doesn’t add all channels …
Not an expert, but recently set up zwave via mqtt and had numerous issues with the homeassistant configs, so much so that I set up over 100 channels using the generic mqtt, not using homeassistant configs at all.
As to possible thoughts,;
Are there any logged warnings?
Is the jinja transform installed?
What are the channel configs in JSON?
For example: Looking at the issue in github I see one device switch has “ON”, “OFF” & “Toggle”. That is not going to work with a Switch item (IMO).
It could work I think. The switch should never enter the state of Toggle. That’s just a command that should result in the state of ON or OFF. As long as nothing sends “Toggle” to the state topic OH should be fine. OH won’t easily be able to send a Toggle command to the device through the Switch Item, but it would still work.
actually it’s a radom. I have a few different TuYa switches (same model), but each one presented a different channels. E.g. one exposed only ‘link quality’ … so there is nothing much which can be done with that option.
Anyway I have managed to add the thing in the OH configuration file.
I can’t argue with your logic, but let me be more precise with
It is not going to survive the rigorous channel verification. My guess is that’s why it is not appearing as channel but is on the UI tab as a config. I am puzzled by the lack of a log entry, but some of the very early validation routines (in early 2022) were at the debug level.