I have trying to install the python modules using customstart.sh file but I get an error https://gist.github.com/varazir/d67eb6173375f3182477066f82e58e32 I have moved back to my own solution for the time being. Strange, but if you solution works, no problem. My solution is to install the modules ...

I see this if I enable debug logs is this normal? It's only device that gives my this logs. 2025-06-17 14:29:20.530 dzVents: Debug: Event triggers: 2025-06-17 14:29:20.530 dzVents: Debug: - Device: NAS (NAS_electric_kwh_value) 2025-06-17 14:29:20.608 dzVents: Debug: Dumping domoticz data to /opt ...

I have trying to install the python modules using customstart.sh file but I get an error

https://gist.github.com/varazir/d67eb61 ... 6f82e58e32

I have moved back to my own solution for the time being.

I updated the plugin First I got this pi@domoticz:~/domoticz/data/plugins/Domoticz-TinyTUYA-Plugin $ git pull remote: Enumerating objects: 114, done. remote: Counting objects: 100% (113/113), done. remote: Compressing objects: 100% (69/69), done. remote: Total 104 (delta 42), reused 94 (delta 34 ...

Hello, Version: 2025.1 (build 16724) Build Hash: a1c7883bd Compile Date: 2025-06-10 08:57:28 dzVents Version: 3.1.8 Python Version: 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0] Uptime: 1 Days, 19 Hours, 43 Minutes, 0 Seconds Raspberry pi 3 MQTT zwavejsAD ( Rpie head) Zigbee2MQTT ( USB device ...

MQTT Explorer is a GUI application Don't just copy/paste any AI generated stuff here https://mqtt-explorer.com/ The setup files from Varazir are a good start, but this is not the best way to work with docker compose 1. For each project you create a folder 2. In this folder you make a file 'docker ...

the right settings are full version in the compose file (dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_cc03fed5943aef11aca9331455516304-if00-port0:/dev/ttyUSB0) and the short version (port: /dev/ttyUSB0) in the config file. Its working now, thanks. I have the data in the remote ...

Screenshot your settings for the auto MQTT Auto Discovery settings in Domoticz..

This is mine. I hade some issue suing local host and 172.0.0.1 so I use the IP my pie get from my router.

this is my setup https://gist.github.com/varazir/65909bd ... 41aef37103

Now day's when I get an error I past it into chatgpt or Gemini and usually get good answer back.

Running in docker ?

gizmocuz wrote: ↑Sunday 08 June 2025 9:11 No, everything is in separate containers. You don't need to update some containers, or you might wish to spin up a new container for a test version etc.

Do you have any good script or way to update the containers when here are a new update there?
Have you tested https://getwud.github.io/wud/ ?

Well, one of them probably works correctly, just rename the other. You can probably google what the difference is between the two, or see it in the zigbee2mqtt web interface? Anyway, it's working It just turns the device on and off to find it. I removed all the devices that comes with the remote ...

I have setup as custom link

Well, there are much more benefits: - No system dependencies ! - Easy backup - Easy restore And yeah, DockGe is a very nice manager for that You also don't have to update if you don't miss any features or fixes Now you know how to use docker, you might check out: https://github.com/Haxxnet/Compose ...

I hade to install some extra libs to get docker running on Buster. It's a drawback using docker as you need to SSH or install a docker manager. You can't just do it from the Domoticz interface as before. Installed DockerGE, I should have started with it, now I need to redo everything, yes I can set ...

if I just keep set the _identify_ devices to unused I'm going to be fine. I think it's something new that z2m expose to MQTT/Domoticz.
It's confusing as they get named the same in domoticz. On it set to Button on device and the other a on/off device.

This is the device we have been talking about Bokhylla

Okey.... So.... the 'switch' is probably from the old Zigbee config? As this is persistent in your MQTT broker, you need to remove it manually with (for example) MQTT Explorer That means, if you can control everything, and see the correct status for the *_identify_* that is I didn't copy the MQTT ...

If I remove the devices and turn z2m hw off and on they will be auto populated again.
In this case I don't care that much of the device ID as it's easy to change the script

btw, can I make new devices not being set to used by default ?