Sonoff B1 RGBCW WiFi Bulb w/ Sonoff-Tasmota

Tutorials & Examples Solutions
, ,
41

Hi Gary, i tried that, but without any change in effect.
Until now i was testing this on a test Pi, but i have also tried it now on my production Pi (changed the IP in Tasmota mqtt, and changed the broker-id in the items and rules files).
However the behaviour is exactly the same… I am able to switch the B1 on/off, and i am able to set the color of the color leds with the color picker. But the sliders do not appear as sliders in my sitemap…
But with the Tasmota web-if everything is working OK.
I get the same error messages from mqtt as with the other platform:

2018-07-30 12:17:25.486 [ERROR] [.mqtt.internal.MqttMessageSubscriber] - Error processing MQTT message.
org.openhab.core.transform.TransformationException: Invalid path '$.Color' in '{"POWER":"ON"}'

mqtt messages:

openhab@openhab:~ $ mosquitto_sub -v -h 192.168.178.54 -p 1883 -t '+/Sonoff_1B1/#'
tele/Sonoff_1B1/LWT Online
cmnd/Sonoff_1B1/DIMMER INCREASE
cmnd/Sonoff_1B1/COLOR ff1a160000
cmnd/Sonoff_1B1/POWER ON
stat/Sonoff_1B1/POWER OFF
cmnd/Sonoff_1B1/DIMMER INCREASE
stat/Sonoff_1B1/RESULT {"Dimmer":49}
cmnd/Sonoff_1B1/DIMMER DECREASE
stat/Sonoff_1B1/RESULT {"Dimmer":49}
cmnd/Sonoff_1B1/COLOR 0000002953
stat/Sonoff_1B1/RESULT {"POWER":"ON","Dimmer":32,"Color":"0000002851","HSBColor":"0,0,0","Channel":[0,0,0,16,32],"CT":500}
cmnd/Sonoff_1B1/POWER OFF
stat/Sonoff_1B1/RESULT {"POWER":"OFF"}
stat/Sonoff_1B1/POWER OFF
cmnd/Sonoff_1B1/POWER ON
stat/Sonoff_1B1/RESULT {"POWER":"ON"}
stat/Sonoff_1B1/POWER ON
cmnd/Sonoff_1B1/POWER OFF
stat/Sonoff_1B1/RESULT {"POWER":"OFF"}
stat/Sonoff_1B1/POWER OFF
cmnd/Sonoff_1B1/POWER ON
stat/Sonoff_1B1/RESULT {"POWER":"ON"}
stat/Sonoff_1B1/POWER ON
tele/Sonoff_1B1/STATE {"Time":"2018-07-30T11:22:54","Uptime":"0T01:25:17","Vcc":3.634,"POWER":"ON","Dimmer":32,"Color":"0000002851","HSBColor":"0,0,0","Channel":[0,0,0,16,32],"CT":500,"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"OFF","Wifi":{"AP":1,"SSId":"NoAccess-3","RSSI":42,"APMac":"5C:49:79:51:78:1E"}}
cmnd/Sonoff_1B1/COLOR 0204022851
stat/Sonoff_1B1/RESULT {"POWER":"ON","Dimmer":31,"Color":"010301264F","HSBColor":"120,67,1","Channel":[0,1,0,15,31],"CT":500}
cmnd/Sonoff_1B1/COLOR 7dcc6d264F
stat/Sonoff_1B1/RESULT {"POWER":"ON","Dimmer":80,"Color":"7CCC6C254E","HSBColor":"110,47,80","Channel":[49,80,42,15,31],"CT":287}
cmnd/Sonoff_1B1/COLOR 89df78254E
stat/Sonoff_1B1/RESULT {"POWER":"ON","Dimmer":87,"Color":"87DC77244D","HSBColor":"110,46,86","Channel":[53,86,47,14,30],"CT":275}
42

Yeah those errors are just because the format of the message changes depending on what the light is doing, so sometimes the RESULT message doesn’t have “Dimmer” or “Color” parts for the JSON parser to find, it doesn’t affect the working of anything.

It’s probably possible to catch the INCREASE and DECREASE commands in the rule and send an updated value, but I don’t have time to write and test that at the moment. Best workaround I can suggest is using the iOS app or Habmin or something that renders sliders instead of buttons.

43

Hi Cary, The Slider issue seems to be a problem with the Classic UI, which for some reason i still use by default… In Basic UI the slider works fine.
In the mean time, i switched to ThomDietrichs example and that is working without the INCREASE and DECREASE errors. I do not know if that also was related to the Classic UI as well…
Thank you for trying to help me with this.