open zwave totally gone after reboot

[tjabas]

Hi!

I run the latest beta on a rpi3b

i have a problem when after a reboot i cant get the z-wave to start as it should, i run the Version: 1.6-1033-g3661f170

the problem is that the nodes wont show at all, if i enter the settings in openz-wave config its totally blank/gone, i have to restart domoticz 3-4 times for the z-wave to start.

any suggestions of what i can do?

if i delete the open z-wave plugin, and reinstall it, will all of my nodes disapear then?

[tjabas]

i also sometimes get an error message at boot that node 0 and node 255 is missing, but i dont have these nodes and never had, does anyone know why i get these error messages?

[tjabas]

Now im also getting this error:
Error: Domoticz(pid:541, tid:921('OZW-driver')) received fatal signal 11 (Segmentation fault)

what can be wrong?

[heggink]

Same here. Irregular signal 11's on OZW.

Sent from phone.

[tjabas]

I Wonder if it can be any problems with the usb porta, i tried to change port but the problem was still there. So i dont really know..

[tjabas]

The Zwave controllers i use is aeotech gen 5 stick, but can i buy the razberry Zwave controllers instead, mabe that one is more stable?
If so can i use the ozw node file from the gen 5 stick?

[heggink]

I have used the aeotec for years without any issues. Afaik, you cannot just move devices as they are associated to the controller. There are ways to transfer but I have never done it.

Sent from phone.

[heggink]

Did you file a bug on github? OZW based segmentation faults are not supposed to happen, no matter what.

[tjabas]

No i havent done that on github, i really dont know how to file a report.
Do i need to log in to github to file a report?

[heggink]

You indeed need (to create) a login. You can just create an issue there. Simple process.

[waaren]

Did you file a bug on github? OZW based segmentation faults are not supposed to happen, no matter what.

Just to manage expectations. The github issue list is for domoticz code bugs only.
There are numerous reasons outside the control of domoticz that can cause a fatal error in any program.
If you are the only one experience this it could well be related to something very specific to your setup or system.

Also make sure you only report an issue when you use the latest Beta or latest Stable an include all available information available including the relevant lines from the log.

[heggink]

Agreed on the beta. That said, a segmentation fault on something like OZW can hardly be triggered by anything outside the control of domoticz. Even if the 'cause' is outside domoticz, it should ideally not segfault and therefore warrant a bug report, agree?

[waaren]

Agreed on the beta. That said, a segmentation fault on something like OZW can hardly be triggered by anything outside the control of domoticz. Even if the 'cause' is outside domoticz, it should ideally not segfault and therefore warrant a bug report, agree?

I've seen a lot of reported segfaults caused by a problem in the file-system, -an incomplete updated system, -corruption in database or in xml file and by faulty hardware. In an ideal world all these external initiated problems would not lead to a segfault but I have not seen any program yet that can handle all these potential issues (even including kernels)
It' is not likely (but not impossible) that in this case the issue is caused by a bug in domoticz code as many other users (including me) use this stick in combination with a wide range of devices and recent Beta's without facing a segfault.

If you remove the stick from the hardware tab you will loose the devices in domoticz but if you made a backup of the database you can easily recover from that. The devices will still be available on the stick itself.

[tjabas]

all of it seems very strange, after a reboot of Domoticz often the z-wave wont start, and its only sometimes i get the fatal signal 11 (Segmentation fault) in the log, and if i get the z-wave to start it has always lost all of the node id´s in the settings, so it has to rebuild it all again, and when that is finished it will disappear once again after a reboot of domoticz.

can i delete all of the open zwave config files and install them again?
could that fix the issue?

[tjabas]

which file is the one that keeps the node info?
i have a couple that is almost the same:

ozwcache_0xeb3e5faf.xml
and:
zwcfg_0xeb3e5faf.xml

what should these file atrribute be set to?
as for now they are set to 640

[waaren]

ozwcache_0xeb3e5faf.xml

ozwcache
640 is OK.

If you stop domoticz and rename this file it wil be rebuild when you start domoticz.

[tjabas]

can i delete all of the open-zwave configfiles and install the again?

i have looked for a download link for openz-wave 1.6 for rpi but i havent found any.

or maybe its not that easy to install like a pyhon plugin is.

[waaren]

can i delete all of the open-zwave configfiles and install the again?

i have looked for a download link for openz-wave 1.6 for rpi but i havent found any.

or maybe its not that easy to install like a pyhon plugin is.

OpenZwave is not a separate module. It is part of the domoticz binary. No need to download something.

About the config files; make a complete backup and remove them. If something fails restore the backup and stop / start domoticz.

[tjabas]

ok, thanks, i will try that.

[tjabas]

i have now spent many hours trying to fix this issue, but today i reinstalled an older backup of domoticz, Version: 4.11674
this one works very good, open z-wave start evertyme i make a reboot of the system, the only problem left is this error of missing node: NodeID not found internally!. HomeID: 0, NodeID: 255 (0xff)

but i guess that i can live with that.

i also deleted 2 plugins that i have some suspicions about, but its just suspicions, nothing that i have seen in any log or so, but the problems started after installing them, and also upgrading to the latest beta.
the plugins where the enigma2 plugin and chromecast plugin.

another thing im thinking of is that i activated root access to Domoticz a while ago, could this cause these errors?

and i will stay of the constant upgrading to the latest beta all the time, though it will be tuff to stay of