The MQTT binding successfully discovers the devices (via homeassistant discovery),
properly reports them as online, but it then fails to control them.
Expected Behavior
Flipping an MQTT bound Item from PaperUI/Control should cause the appropriate MQTT message to be sent to the broker.
Current Behavior
Flipping an MQTT bound Item from PaperUI/Control causes the following WARNs in openhab.log. The MQTT message is actually sent, but with the wrong content.
Details
Configuration JSON of the discovered Thing attached to the Item (discovered with homeassistant discovery):
2019-02-05 21:22:14.710 [WARN ] [eneric.internal.generic.ChannelState] - Command '1' not supported by type 'OnOffValue': No enum constant org.eclipse.smarthome.core.library.types.OnOffType.1
2019-02-05 21:22:17.224 [WARN ] [eneric.internal.generic.ChannelState] - Command '0' not supported by type 'OnOffValue': No enum constant org.eclipse.smarthome.core.library.types.OnOffType.0
content in the MQTT message actually sent contains the text "true"/"false" rather than "1"/"0", which the device does not recognize.
Steps to Reproduce (for bugs)
Via Paper UI:
Discover a Thing via homeassistant discovery from MQTT with discovered content as mentioned in JSON configuration.
Link the Thing to an Item.
Operate the Item flipping the switch on and off.
Check the MQTT output carrying the wrong payload.
Additionally, I suspect that the capture of the actual state from MQTT is failing as well for similar reasons.
Environment
OpenHab reinstalled from scratch, no other configurations or status in the way.
Version used: OpenHab and addons 2.5.0.M1
Java: both
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
Operating System and version: both
Ubuntu 16.04.5 LTS
QNAP TS-669 Pro, QTS 4.3.4.0752
The MQTT binding successfully discovers the devices (via homeassistant discovery), properly reports them as online, but it then fails to control them.
Expected Behavior
Flipping an MQTT bound Item from PaperUI/Control should cause the appropriate MQTT message to be sent to the broker.
Current Behavior
Flipping an MQTT bound Item from PaperUI/Control causes the following WARNs in openhab.log. The MQTT message is actually sent, but with the wrong content.
Details
Configuration JSON of the discovered Thing attached to the Item (discovered with homeassistant discovery):
note "payload_on":"1","payload_off":"0"
Warning registered in logs:
content in the MQTT message actually sent contains the text "true"/"false" rather than "1"/"0", which the device does not recognize.
Steps to Reproduce (for bugs)
Via Paper UI:
Additionally, I suspect that the capture of the actual state from MQTT is failing as well for similar reasons.
Environment