Hi,
I’m getting this error on OZW when a Z-Wave lock is triggered.
11-04 13:29:07.330 Error: Domoticz(pid:27184, tid:27225('OZW-driver')) received fatal signal 11 (Segmentation fault)
It actually crashes Domoticz.
It was on a new install of Domoticz, but copying over the old database. I’ve deleted the hardware, then added it again (I’m using the Aeotec stick)
Is there any way to re-install the OZW software so this doesn’t happen?
Segmfault using OZW
Moderator: leecollings
-
- Posts: 221
- Joined: Thursday 23 January 2014 12:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8153
- Contact:
Re: Segmfault using OZW
OK, no answers on this, so I re-installed Domoticz again and removed, then re-inserted the Aeotec stick.
Now I have a different problem; when opening or closing a door, I get the following error:
The lock indication on the device works OK when opening or closing.
Now I have a different problem; when opening or closing a door, I get the following error:
Code: Select all
2022-11-06 14:15:54.063 Error: Z-Wave : Value_Changed: Tried adding value, not succeeded!. Node: 24 (0x18), CommandClass: DOOR LOCK, Label: Locked (Advanced), Instance: 1, Index: 1
- kiddigital
- Posts: 438
- Joined: Thursday 10 August 2017 6:52
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Segmfault using OZW
If starting out with Zwave, please switch to Zwave2mqtt and Domoticz MQTT Auto Discovery as the build-in OZW will be removed soon.
(Domoticz OZW depends on an external not maintained anymore library)
(Domoticz OZW depends on an external not maintained anymore library)
One RPi with Domoticz, RFX433e, aeon labs z-wave plus stick GEN5, ha-bridge 5.4.0 for Alexa, Philips Hue Bridge, Pimoroni Automation Hat
One RPi with Pi foundation standard touch screen to display Dashticz
One RPi with Pi foundation standard touch screen to display Dashticz
-
- Posts: 108
- Joined: Monday 04 March 2019 14:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2025.1
- Location: France
- Contact:
Re: Segmfault using OZW
Hello
Please do not remove OZW from Domoticz distribution as the latest version is working perfectly.
Instead of that let Domoticz users choose to keep OZW (event at their own risks) or switch over to Zwave2mqtt.
Many thanks
Best regards
Please do not remove OZW from Domoticz distribution as the latest version is working perfectly.
Instead of that let Domoticz users choose to keep OZW (event at their own risks) or switch over to Zwave2mqtt.
Many thanks
Best regards
meal
-
- Posts: 108
- Joined: Monday 04 March 2019 14:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2025.1
- Location: France
- Contact:
Re: Segmfault using OZW
Hi nigels0
I understand you succeeded in inserting the door sensor in you Zwave configuration and it operates correctly from a functional standpoint.
To tackle your message issue.
Have you tried to enable the creation of new devices in the Domoticz settings.
Sometimes the zwave sensor send messages which are captured by OZW and it creates new zwave devices.
BR
I understand you succeeded in inserting the door sensor in you Zwave configuration and it operates correctly from a functional standpoint.
To tackle your message issue.
Have you tried to enable the creation of new devices in the Domoticz settings.
Sometimes the zwave sensor send messages which are captured by OZW and it creates new zwave devices.
BR
meal
-
- Posts: 221
- Joined: Thursday 23 January 2014 12:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8153
- Contact:
Re: Segmfault using OZW
Hi meal,
I have new devices closed - but it seems on a bit of googling, there is an issue with the way Domoticz handles responses with (advanced) in them - I guess the error has been noted, but there doesn't seem to be a time to fix it as OZW isn't going to be supported. The general advice is just to ignore them!
I'm finding installation of the replacements for OZW problematic - otherwise I'd switch to that. I've tried installing with Snap, but it gets complicated quickly and the Wiki is (to say it politely) rather sparse.
I must admit, I need a simpler and more complete guide to install the replacement for OZW.
Regards
I have new devices closed - but it seems on a bit of googling, there is an issue with the way Domoticz handles responses with (advanced) in them - I guess the error has been noted, but there doesn't seem to be a time to fix it as OZW isn't going to be supported. The general advice is just to ignore them!
I'm finding installation of the replacements for OZW problematic - otherwise I'd switch to that. I've tried installing with Snap, but it gets complicated quickly and the Wiki is (to say it politely) rather sparse.
I must admit, I need a simpler and more complete guide to install the replacement for OZW.
Regards
-
- Posts: 221
- Joined: Thursday 23 January 2014 12:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8153
- Contact:
Re: Segmfault using OZW
One thing I’ve found out; to get past the seg fault, I woke up the door lock devices (by opening them) then starting up Domoticz. This seems to fix the issue and Domoticz keeps running.
-
- Posts: 221
- Joined: Thursday 23 January 2014 12:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8153
- Contact:
Re: Segmfault using OZW
I’ve given up on OZW - just couldn’t fix the seg faults, so moved to the new config. It wasn’t painless and had to reload some items like locks before I got to a workable state.
It really isn’t as integrated and pretty as OZW, but at least it has a development future.
It really isn’t as integrated and pretty as OZW, but at least it has a development future.
Who is online
Users browsing this forum: No registered users and 1 guest