Erik Baauw
Erik Baauw
> 15:31:02:955 DeviceAnnce of LightNode: 0x7CB03EAA00AFA4FE Permit Join: 0 This means the bulb's firmware has rebooted. It's probably configured to turn on on reboot; you might want to change that....
> I think we have an additional problem. I don't see any information Looks like `general.xml` is corrupt (or cannot be opened). > The SYMFONISK Sound Controller E1744 only displays...
Not sure if it makes sense to define _Drift Compensation_ and _Compensation Text_ - haven't found any device yet that supports these.
Analysing the logs, the dependency on the VNC server almost seems to work; there's only a 1-2 second mismatch between the start of the VNC server and the X server...
This is not going to work. The `isColorLoopActive()` checks only for colorloop. The special effects work very differently on Zigbee level, and are manufacturer-specific (Hue implements them differently from Mueller...
I find my workaround now fails, and causes deCONZ to crash on the first attempt. Not sure if that's due to changes to PiOS, or changes in deCONZ startup sequence....
The solution described here requires the user to create an `override.conf` file. You might consider integrating this in the `deconz-gui.service`. And while we’re at this, fix #2771 as well. I...
If I may cut in, I doubt that this is a Phoscon issue. In my experience, this is more likely an issue with the API plugin and/or the light firmware....
Brand wouldn’t be a determining factor here. Would need to know: - Whether light is exposed through DDF or legacy code; - Weather light supports attribute reporting. Unless you try...