Aeon Smart Switch 6 Color channel behaviour changed after 2.4 release upgrade

  • Platform information:

    • Hardware: Raspberry Pi 3 Model B Rev 1.2
    • OS: Raspbian GNU/Linux 9 (stretch)
    • Java Runtime Environment: OpenJDK Runtime Environment (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 1.8.0_152-b76)
    • openHAB version: openHAB 2.4.0-1 (Release Build)
  • Issue of the topic:

I recently upgraded from openHAB 2.4 M5 to the 2.4 Release version and have noticed a change in behaviour in the color channel of my Aeon Smart Switch 6 thing.

According to the documentation the color channel can be used to change the switch LED color and also dim and/or switch the LED ON and OFF so I linked two items to this channel, a Color item to control the LED color and a Switch item to control it’s ON/OFF state.
This worked fine in openHAB up to the 2.4 M5 version but not so much anymore with the 2.4 Release version.
I can still use the Switch item to send ON and OFF command and these will still result in the LED being switched on or off but the state of the Switch item will always revert back to ON automatically.
In the log I see the following sequence reported after sending an OFF command:

2019-01-03 11:44:32.440 [ome.event.ItemCommandEvent] - Item 'cNightlight' received command OFF
2019-01-03 11:44:32.458 [nt.ItemStatePredictedEvent] - cNightlight predicted to become OFF
2019-01-03 11:44:32.475 [vent.ItemStateChangedEvent] - cNightlight changed from ON to OFF
2019-01-03 11:44:34.090 [vent.ItemStateChangedEvent] - cNightlightColor changed from 62,52,100 to 62,52,0
2019-01-03 11:44:34.556 [vent.ItemStateChangedEvent] - cNightlight changed from OFF to ON
2019-01-03 11:44:34.577 [vent.ItemStateChangedEvent] - cNightlightColor changed from 62,52,0 to 62,52,100

And although the state of the Switch and Color items reverts back to ON values the LED is NOT turned on again. Sending an actual ON command WILL however turn the LED on again.

Does anybody know if this is an intended behavioral change?
Thanks!

1 Like

To confirm, I see the same behavior in 2.4. I was trying the color channel for first time today and it logs events etc, but the device doesn’t change at all.