controller do not switch

[jogibear9988]

From @fmsmuc on February 14, 2017 13:23

have three controllers - all controllers are detected as HF-LPB100-ZJ200
it seams that my HF-LPB100-ZJ200 is LD868 (five channels)
and the UFO HF-LPB100-ZJ100 (LD??? )

one Contoller is UFO with 4 channel RGBW (in MagicHome shown as version 3)

two Controllers are 5 channel with RGBWW (and same charge - in MagicHome shown as version 1)
(https://www.amazon.de/gp/product/B01J5A7ABW/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1)

in ioBroker you can see the status change but one of the four Controller do not switch or only sometimes - the other one does. Sometimes the four channel Controller UFO works - sometimes not.
the same with the four channel controller - one is working, the other works only sometimes even if status change is shown in ioBroker.
port (5577) has to be correct because sometimes it is working.
devicename: HF-LPB100-ZJ200' - port: 5577
Found that there is a possibility to switch between 4 and 5 channel controllers see here:
https://github.com/steve228uk/homebridge-magichome/blob/master/flux_led.py

1.) why does UFO do not switch or only sometimes? (found solution - see below)
2.) why does one five channel controller switch and the other only sometimes?
3.) would it be possible do create a datepoint for cold white so that we have w (warm white) and cw (cold white) if it is a 5 channel RGB warmwhite coldwhite controller ?
4.) "ct" Paramater does not work (have one Controller with warm/coldwhite LED)
5.) Status of Pramameters show wrong values in ioBroker

I did a capture of the TCP traffic - Magic home sends "81 8A 8B 96" gets response and then the "on" or "off command "71 23 0F A3"

i modified the flux_led.py script and then the script was working too.
But, did not test brightness and colors - if you need captures please tell me.
I have the manufacture original docs of all command - if you need this, please tell me.
"81 8A 8B 96" is a request of device status. I think in newer firmware it is a must that the device status has to be requested, before it can be switched on /off.

Could you please alter the Wifilight Adapter that it can handle controllers with newer software and the new 5 channel controllers.

by the way - with the magichome app its working all the time, so the controller hardware is ok
thank you

Copied from original issue: soef/ioBroker.wifilight#4

[jogibear9988]

From @Ilovegym66 on August 31, 2018 12:14

Hi,
here the same, with 13 controllers, and regulary updates with iobroker the wifilight adapter hangs up, btw does not recognize that a device have to switch on. ( with Command or power-on flag ).
After a restart of the wifilight adapter in iobroker it works for some time ( most 2-3 hours..) and than the same again..
I've a workaround, that I let it restart automatically all 4 hours, but this results in errors with the wifilight-adapter in iobroker, the adapter doesn't linke a restart here..

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.