Domoticz

heggink wrote: ↑Tuesday 16 March 2021 10:34

So, this is why I am in doubt and why I started this topic in the first place. Basically: will it always be a hassle with systems like Domoticz, Home Assistant etc? Will it always be tinkering? And at the same time: does switching to a system like Atom Homey, Fibaro Homecenter, Samsung Smart Things mean it will automatically work and always work? Or perhaps the issues that I am running into are mostly caused by using either older devices or cheap Chinese devices.
I know my brother was done with Domoticz and switched to Atom Homey and every now and then he asks:"When are you done tinkering with your home automation? When do you take the plunge?"

Agree. I happen to like the messing about with technology but I realise that the current system is fully dependent on me and heaven forbid me and my car have a close encounter with a tree at speed...

heggink wrote: ↑Tuesday 16 March 2021 10:34 On your question, is OZW/ZW-node-js functional/stable enough compared to fibaro/homey/..? That's a good question. Is the hassle worth the flexibility? Comparing to zigbee, for me it is. I can make minor changes that allow me to keep it functional without major hassle.

Are some of the zwave issues solved in zw-node-js? Without the change to >255 devices in the python framework, and without a python plugin, there is time to look at the HA/zw-node-js forums and monitor people's issues reported and see how that's being experienced. I am in no rush but the moment a flexible alternative comes along, I will move.

• What causes this resetting of parameters?
• Does this also happen if you include these smoke detectors in Fibaro HC or Atom Homey?
• Do other people using Domoticz and Fibaro smoke detectors also have these issues?
• Does this also happen with Fibaro 2nd gen smoke detectors or only with the 1st gen?
• Can I easily restore these parameters rather than setting them node by node?
• Etc....

heggink wrote: ↑Tuesday 16 March 2021 11:26 Not trying to open another can of worms, the smoke detectors never worked properly for me in zwave so I just bought zigbee ones. Never any issues with then since. I just gave up on the zwave ones.

heggink wrote: ↑Tuesday 16 March 2021 11:26 Many times, zwave issues are blamed on / due to "cheap Chinese devices" (neo plugs...). Whether always valid?

heggink wrote: ↑Tuesday 16 March 2021 11:26 No idea if these issues also happen with the homey's of this world. Would be interesting to check.

Yes, I am going to check on the Homey community and perhaps some other communities like the ones from Fibaro or Samsung Smart things.

roblom wrote: ↑Saturday 20 March 2021 10:09 A few days ago I also had a deja vue because a lot of my zwave devices weren't working anymore. Most of them where indeed missing some parameters which got back after the "update device info" function. I only can't get the Fibaro smoke sensors I have working anymore. After the update device info function the get the generic type "notification sensor" and no parameter are shown.

Plantje wrote: ↑Saturday 20 March 2021 12:56 So, I hit the "refresh node info" button and....my Domoticz is stuck again. So, I have to restart the service again. Do you not have that issue?

Plantje wrote: ↑Saturday 20 March 2021 13:00 Well this is new: in the logging I see: 2021-03-20 12:49:57.931 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 71.000000 seconds ago)

RvdM wrote: ↑Sunday 21 March 2021 3:17 Oh my... Am I glad i stumbled on to this post. Since last year it is nothing but trouble with my domoticz-zwave setup.
Devices go unknown.. have to refresh the devices once every few weeks and sometimes this resolve things.. and sometimes the only thing I can do is just wait a couple of days. (not good for keeping the wife satisfied).Also today, 3 AM on a saturday i'm once again debugging and trying to solve the problem by repeatedly clicking on refresh node button.

I've never had so many issues since this last year and the most frustrating part is, the philips hue setup and my esp32 (wifi) modules are working without any maintenance. This brings me to a point that i'm really considering quiting my domotica hobby or fully switch to zigbee and migrate from domoticz to home assistant.

Good to see i'm not alone because I was thinking i'm the one being incompetent of maintaining a domotica network.

Ittiz wrote: ↑Friday 26 March 2021 3:03 Just roll back to 4.10717. Z-wave worked great back then. I rolled back a long time ago after getting frustrated with exactly the same kind of issues. The one issue is Google changed their notification system since then so the built in ones don't work when using 4.10717. But you can get the working by following the instructions in this post here: viewtopic.php?f=21&t=30341 If you look at the date on that post you'll see these issues have been going on for quite some time. The bigger z-wave network you have the bigger your issues will become.

RvdM wrote: ↑Sunday 21 March 2021 3:17 I've never had so many issues since this last year and the most frustrating part is, the philips hue setup and my esp32 (wifi) modules are working without any maintenance. This brings me to a point that i'm really considering quiting my domotica hobby or fully switch to zigbee and migrate from domoticz to home assistant.

Good to see i'm not alone because I was thinking i'm the one being incompetent of maintaining a domotica network.

heggink wrote: ↑Tuesday 16 March 2021 17:48 @Plantje

Yes, I am going to check on the Homey community and perhaps some other communities like the ones from Fibaro or Samsung Smart things.

I did a little snooping around on the homey community/forum pages. After a while, I started to get this "Deja Vue" feeling with posts like:
https://community.athom.com/t/heiman-sm ... ector/2344
https://community.athom.com/t/ikea-dimmer-problem/44074
https://community.athom.com/t/fixing-di ... lows/37896
and so on/forth. Looks like it's not such a walk in the park as well. Then again, maybe not surprising as one could wonder whether a relatively small company (aren't all home automation companies small?) can even compete with an open source community from a bug fixing perspective... 10 devs owning all problems vs 20.000 end user type hackers (like myself being an old C programmer who engages in python hacking these days) and a few capable devs having multiple interests . The judges are probably still out on that one .

Anyways, still no answer for your "why do all the parameters get reset" question.

H

rrozema wrote: ↑Sunday 28 March 2021 19:59 Did you verify that it is indeed the parameters in the device that got reset? For example I've got some in wall touch switches that normally have a blue ring lit when the switch is in the off position. I've switched the blue ring off by setting one of the options in the device's settings. I've never had that accidently the ring went blue again. In other words, the device settings in the device itself were never reset to their default values, it was just Domiticz that didn't know the options values anymore.

rrozema wrote: ↑Sunday 28 March 2021 19:59 Many of the issues reported here and with ozw 1.6 in general can be traced back to the ozwcache xml file getting corrupted. The device settings are also stored in this xml file and read from there upon each start of Domiticz: if the settings seem 'lost', try re-reading them from the device using the button in the bottom of the options list.

rrozema wrote: ↑Sunday 28 March 2021 18:26 Ozw 1.4 doesn't support a lot of more modern devices. Many of the issues complained about in here are in fact user errors. Don't understand me wrong, there are a lot of issues in 1.6, but going back to 1.4 is not a solution.

Plantje wrote: ↑Friday 26 February 2021 22:52 Let me quickly get back to my own topic. I love seeing the responses here! This is exactly the discussion I wanted to get going!

I read through all of the comments, but didn't (and am not going to) reply to all of them. That would be pointless.

However, I think I can draw some preliminary conclusions.

• First of all, it seems that the issues that I had a few years ago where mostly caused by my limited understanding of Z-Wave, the nodes and devices. That has improved in the meantime, but most likely I will still make some mistakes.

rrozema wrote: ↑Sunday 28 March 2021 19:59 Did you verify that it is indeed the parameters in the device that got reset?

commandArray = {}

intLicht = 50
strDimLevel = '65'
strBewegingsSensor = 'Multi Overloop Beweging'
strLamp = 'Lamp Overloop'
strLichtSensor = 'Multi Overloop Licht'
strDuurLichtAan = ' FOR 1'

--print('Status ' .. strLamp .. ' ' .. otherdevices[strLamp])
--print('Status ' .. strLichtSensor .. ' ' .. otherdevices_svalues[strLichtSensor])
--print('Status ' .. strBewegingsSensor .. ' ' .. otherdevices[strBewegingsSensor])
--print('Test commando: ' .. 'Set Level ' .. strDimLevel .. strDuurLichtAan)

if (otherdevices[strBewegingsSensor] == 'On' and (tonumber(otherdevices_svalues[strLichtSensor]) < intLicht) and otherdevices[strLamp] == 'Off') then
    print('Nieuwe logica '.. strLamp .. ' aan')
    commandArray[strLamp]= ('Set Level ' .. strDimLevel .. strDuurLichtAan)
end

return commandArray

What the F? I cannot add pictures anymore.... the board's attachments quota has been reached...?!?

dmtcaz wrote: ↑Wednesday 23 December 2020 18:32 This is what helped solve my problem - and hopefully future ones as well though it's more a kinda workaround:
I modified options.xml (/domoticz/Config) by setting

<Option name="ReloadAfterUpdate" value="NEVER" />

which prevents a new z-wave devices config file to automatically modify existing nodes. You could also prevent the new file from downloading by setting

<Option name="AutoUpdateConfigFile" value="false" />

However you might miss device info in the future when you install new devices with this last setting.

Although manual says not to, after that I modified the ozwcache_[id].xml file (/domoticz/Config) specifically for the recalcitrate device. Under Commandclass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" I simply deleted some lines that contained bs imho (yep, first made a backup ). Depending on your situation you may have to experiment a little. My temperature readings were restored. After that I had to manually delete the duplicate and false devices from the devices panel in Domoticz. Domoticz keeps these stored in a separate db I presume.