Abus door lock issue after update Domoticz
Moderators: leecollings, remb0
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Abus door lock issue after update Domoticz
After version Domoticz2025.1 (build 16732), my Abus zwave doorlock works not anymore. What has changed?
For now i'm stuck to this verion..
For now i'm stuck to this verion..
- gizmocuz
- Posts: 2709
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Abus door lock issue after update Domoticz
Are you using OpenZWave or ZWaveJS-UI with MQTT?
What does not work anymore? Did you receive a new device?
Can you receive the status, or does it not lock/unlock?
What does not work anymore? Did you receive a new device?
Can you receive the status, or does it not lock/unlock?
Quality outlives Quantity!
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
I'm using ZWaveJS-UI with MQTT.
Open/close commands don't work anymore
Status is also not received
Open/close commands don't work anymore
Status is also not received
- gizmocuz
- Posts: 2709
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Abus door lock issue after update Domoticz
Please create a issue on Github following the below Guidelines:
https://wiki.domoticz.com/MQTT_AD_Report_Problems
https://wiki.domoticz.com/MQTT_AD_Report_Problems
Quality outlives Quantity!
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
mqtt-explorer: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
It don't want to run..
It don't want to run..
- jvdz
- Posts: 2441
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: Abus door lock issue after update Domoticz
On which OS are you running this, and how did you install mqtt-explorer?
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
Debian 12 and installed with apt install ./MQTT-Explorer_0.4.0-beta.6_amd64.deb
Update; i'v installed libasound2.. now i'v got this:
mqtt-explorer
14:07:14.526 › App starting...
subscribing connection/add/mqtt
subscribing connection/remove
subscribing storage/store/request
subscribing storage/load/request
subscribing storage/clear/request
[14919:0823/140714.536456:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[14919:0823/140714.536888:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
Segmentation fault
My Debian is a server...it has no display..
Update; i'v installed libasound2.. now i'v got this:
mqtt-explorer
14:07:14.526 › App starting...
subscribing connection/add/mqtt
subscribing connection/remove
subscribing storage/store/request
subscribing storage/load/request
subscribing storage/clear/request
[14919:0823/140714.536456:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[14919:0823/140714.536888:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
Segmentation fault
My Debian is a server...it has no display..
Last edited by abc1000 on Saturday 23 August 2025 14:11, edited 1 time in total.
- jvdz
- Posts: 2441
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: Abus door lock issue after update Domoticz
Do you have a Windows computer you could run on to avoid having to install addition libraries on Debian?
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
yes.. i did the install on Windows and it runs! But it disconnects.. i'm using same setting as in Domoticz..
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
Ok, it works! had to do this:
General Warning config change for v2.0 and up
From Mosquitto v2.0.x you need extra configuration, else no connection is made with Domoticz see also https://www.domoticz.com/forum/viewtopi ... 28&t=35706
To see your installed version:
mosquitto -h | grep version
To fix this edit the /etc/mosquitto/mosquitto.conf file and add:
listener 1883
allow_anonymous true
General Warning config change for v2.0 and up
From Mosquitto v2.0.x you need extra configuration, else no connection is made with Domoticz see also https://www.domoticz.com/forum/viewtopi ... 28&t=35706
To see your installed version:
mosquitto -h | grep version
To fix this edit the /etc/mosquitto/mosquitto.conf file and add:
listener 1883
allow_anonymous true
- waltervl
- Posts: 6678
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2025.1
- Location: NL
- Contact:
Re: Abus door lock issue after update Domoticz
Ok, so it was a configuration issue of Mosquito v2. Did you update Mosquito also when updating Domoticz?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
- jvdz
- Posts: 2441
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: Abus door lock issue after update Domoticz
Only for his mqtt-explorer usage from his external windows computer, but unrelated to the original issue. He now needs to provide the required mqtt message info,waltervl wrote: Saturday 23 August 2025 18:14 Ok, so it was a configuration issue of Mosquito v2. Did you update Mosquito also when updating Domoticz?
-
abc1000
- Posts: 24
- Joined: Friday 14 October 2016 20:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Abus door lock issue after update Domoticz
I did not update Mosquito
I'v created an issue on Github
I'v created an issue on Github
Who is online
Users browsing this forum: No registered users and 1 guest