I have reed switches on my doors sending MQTT state updates of 0 for CLOSED and 1 for OPEN.
Here is what the log is showing.
2021-03-31 10:39:11.226 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '0' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.0
I know I need to tell the system that 0=CLOSED and 1=OPEN but I can’t find any documentation about how to do that in the GUI. I’ve tried every transformation value I can and nothing works.
You don’t want ‘incoming value transformation’, clear that one out.
If you set ‘Custom On/Open Value’ to “0=CLOSED,1=OPEN” that is the message it will look for. You don’t have your thingy sending a message “0=CLOSED,1=OPEN” so that won’t work.
As I understand you, your thingy sends 0 and 1, so these are the custom values you want to look for?
But every time I open or close the door here is what is shown in the log viewer.
2021-03-31 13:33:18.445 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '0' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.0
2021-03-31 13:33:30.063 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '1' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.1
2021-03-31 13:33:31.163 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '0' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.0
2021-03-31 13:33:31.863 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '1' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.1
2021-03-31 13:33:32.662 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '0' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.0
When I change the Custom On/Open Value and save it I do get this in the log.
2021-03-31 13:39:30.111 [me.event.ThingUpdatedEvent] - Thing 'mqtt:topic:ESP_B11D69_Basement_Door' has been updated.
So I know it’s doing something just not what I want.
Well I made some improvement because it now showed an ItemStateChangeEvent
2021-03-31 14:01:58.852 [vent.ItemStateChangedEvent] - ESP_B11D69 changed from NULL to CLOSED
2021-03-31 14:01:58.910 [me.event.ThingUpdatedEvent] - Thing 'mqtt:topic:ESP_B11D69_Basement_Door' has been updated.
==> /var/log/openhab2/openhab.log <==
2021-03-31 14:01:58.945 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '0' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.0
2021-03-31 14:02:34.768 [WARN ] [ab.binding.mqtt.generic.ChannelState] - Command '1' not supported by type 'OpenCloseValue': No enum constant org.eclipse.smarthome.core.library.types.OpenClosedType.1
You can’t tell from the log which channel is complaining.
You might be able to tell which MQTT message triggers the WARNs, by the timing.
Otherwise you have to look them all over carefully.
People have had trouble setting these due to some UI quirk, as I understand it they appear to have default values 0 and 1 but in reality you have to change them to something else, save, change them to 0 and 1, save again, to get the Thing properly updated.
2021-03-31 14:49:01.394 [me.event.ThingUpdatedEvent] - Thing 'mqtt:topic:ESP_B11D69_Basement_Door' has been updated.
2021-03-31 14:49:24.333 [vent.ItemStateChangedEvent] - ESP_B11D69 changed from CLOSED to OPEN
2021-03-31 14:49:25.728 [vent.ItemStateChangedEvent] - ESP_B11D69 changed from OPEN to CLOSED
2021-03-31 14:49:26.235 [vent.ItemStateChangedEvent] - ESP_B11D69 changed from CLOSED to OPEN
2021-03-31 14:49:27.127 [vent.ItemStateChangedEvent] - ESP_B11D69 changed from OPEN to CLOSED
I open and close the door several times to make sure I’m looking at the correct one.
