You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iobroker 7.0.6
js-controller 7.0.6
npm 9.8.0
node 20.5.1
Conbee II USB Stick
After updating the deconz adapter from 1.4.1 to 1.6.4 the light components are not working any longer.
The deconz.0 light objects in iobroker seems to have no connection to the phoscon web gui (aka zigbee) which is working well.
Curiously the deconz.0 sensor objects are still working.
Even deleting a light in phoscon and in the deconz.0 object direktory. Restarting the adapter (and PC) and connect the light again to zigbee can't solve the problem for this light. Seems that there is really no connection zigbee - deconz Adapter for the lights any longer.
After downgrading to 1.4.1 everything is working again.
The text was updated successfully, but these errors were encountered:
More or less same issue for me. After upgrade to deconz adapter 1.6.4 components could not be controlled any more via JS. Object values were available and read out correctly, but setting/updating values was not possible - they were shown in the objects overview, but not acknowledged. I downgraded to version 1.5.0 and everything worked fine for me again.
My system:
iobroker 7.0.6
js-controller 7.0.6
npm 9.8.0
node 20.5.1
Conbee II USB Stick
After updating the deconz adapter from 1.4.1 to 1.6.4 the light components are not working any longer.
The deconz.0 light objects in iobroker seems to have no connection to the phoscon web gui (aka zigbee) which is working well.
Curiously the deconz.0 sensor objects are still working.
Even deleting a light in phoscon and in the deconz.0 object direktory. Restarting the adapter (and PC) and connect the light again to zigbee can't solve the problem for this light. Seems that there is really no connection zigbee - deconz Adapter for the lights any longer.
After downgrading to 1.4.1 everything is working again.
The text was updated successfully, but these errors were encountered: