I can see from the ean number that is clearly an Aqara Zigbee sensor. https://www.zigbee2mqtt.io/devices/DJT11LM.html#aqara-djt11lm You can update the sensitivity in the Zigbee UI. Before you update the settings, you need to wake up the device by pressing the button on it. And then change the ...

There are some known issues with some zwave usb sticks on rpi mod4.
Maybe you have one of these problematic zwave adaptors?
e.g.
https://forums.raspberrypi.com/viewtopi ... 1#p1502030

The solution is to use a powered usb hub in between.

Did you delete the zwavejs-ui discovery topics with MQTT explorer before starting before running docker-compose up -d --remove-orphans?

As most likely they are retained and will stay until you delete them with e.g. a tool like MQTT explorer

This is the way I update my zwavejs-ui go to the directory where your docker compose file is stored (in my case: cd /home/pi/zwavejs2mqtt) #update your docker compose file for zwavejs-ui if needed docker-compose pull zwave-js-ui docker-compose down # now your docker container is stopped, you can use ...

Now there is a way to disable these config devices in zwavejs-ui for people that have no need for them. (in my case there were almost more config devices than other devices.) from zwavejs-ui release 9.10.2 See https://github.com/zwave-js/zwave-js-ui/issues/3571 Just add in the docker-compose.yml ...

Hi,

I created some rooms and added them to a floor plan. In the room plan, I added the devices I want to have the updates published.
Then I set used published topic Floor/Room. In that case, I have control over which sensors/devices are published.

Could it be that your sensor is a Xiaomi GZCGQ01LM light intensity sensor? I have 3 of them, and all of them have the same behaviour. Almost every day the battery level drops to 0, causing Domoticz to report a low battery level. The battery level of these devices in zigbee2mqtt is not reliable as it ...

See FAQ from Zigbee2mqtt:
https://www.zigbee2mqtt.io/guide/faq/#w ... networkmap

To make the Zigbee plugin menu work again, you need to set the api_transport device created in the devices menu to used.

t was working with Domoticz build 13703, From build 13704 onwards the problem started. So change between 13703 and 13704 caused the control panel load problem.

Just tried in Firefox private mode and chrome incognito mode. Fails to load.

And the same behaviour with the machinon-beta theme, where in the settings menu, the theme menu does not load.

Ctrl-F5 has been tried, clear browser data, 3 different browsers...no success. The zigbee2mqtt now keep internal configuration, and if a device in domoticz is deleted, you need to delete it also from the zigbee2matt plugin configuration. Removing it in the zigbee control panel does not work as the ...

Sure, my zigbee2mqtt control panel works on my Zigbee vm, but I am referring to the custom menu of the zigbee2mqtt plugin creates in Domoticz. If a zigbee2mqtt plugin device was removed from the devices, re-creation will fail until the configuration is updated in the zigbee2mqtt plugin configuration ...

Same here. I cannot access the zigbee2mqtt control panel anymore, and this both in my test setup and Prod environment. It must have happened with the recent Domoticz betas as it was working before with the latest zigbee2mqtt plugin. It does not matter if the allow new hardware is enabled or not. The ...

Same here. It started after update of the zigbee2mqtt plugin v 3.10.
Went back to the previous version, and no more errors.

This morning I tried to upgrade from the stable version 4.10717 on a raspberry PI 3B to beta version 4.11666. Most of the powered devices were almost instantly detected and worked fine. But when I tried to switch on of my FIBARO System FGD212 Dimmer 2, Domoticz crashed. I can set the level, but ...