Closed Zakraket closed 8 months ago
Could you verify if your device has the light_mode capability (for instance under the devices from the developer tools) and send me a diagnostic report after triggering this card, preferably shorty after a reboot of Homey to get a clean log.
I removed that capability for the RGBW as there is no real temperature light mode. The error suggests it tries to set the light_mode anyway.
hi
Restarted Homey, waited for all devices to come online
The same for every RGWB (some are the old driver, some the new generic one), this is the only one that drives an RGBW strip (the others are on WW-strips)
Diagnostic report: "E9E496FC" (from developer tools, is that the one you need?)
btw it worked for both drivers (old and new) before the last updates
Diagnostic report: "E9E496FC" (from developer tools, is that the one you need?)
No, I need the one from the app settings in the Homey app. This one above goes to a black hole called Athom. ;-)
you ask we turn ;-)
8a64c454-0b21-42ac-9591-7ab4a771b4aa
I was already aware this issue would occur on the old RGBW2 driver but decided not to fix it anymore. After 1,5 years of deprecation these drivers arent supported anymore as I dont want to maintain the same functionality at two different places in the code. So you will have to re-pair these devices.
But are you 100% this also happens on the generic driver? The only errors in the log are from devices in the deprecated drivers.
When I have some time I will test myself but I'm a bit busy with other things atm.
I think I was confused, it works on the new driver, tnx. I'll readd the old device.
Is there a way to replace devices without braking the flows?
I havent tried it myself but you can have a look at this.
I think since the last update the "choose color" card doesn't work anymore on the Shelly RGWB
Doesn't work for "old" devices and not for new (generic)