Domoticz

Yet again with the 2 last updates my devices keep timing out... I'm now on 4.9766

No one here willing to help or explain why one day it's working one another.
Some times it just works with restarting the raspberry pi and works 1 day then it's back again.
Or delete and add it again. But it's starting to bugging me out

Agreed, it's really weird

Have you tried the Heal network under Node Management, this fixed a lot of the timeouts I was getting.

Currently on my main machine every web browser under two accounts stop functioning using the latest version

mark.sellwood wrote: ↑Tuesday 17 July 2018 22:59 Have you tried the Heal network under Node Management, this fixed a lot of the timeouts I was getting.

I have never had any luck with using that. Feels like nothing happens.
Only thing that sometimes work is rebooting.

Why do I get presume dead like it's don't try again, I wish I could reset that value.

Varazir wrote: ↑Wednesday 18 July 2018 9:19

mark.sellwood wrote: ↑Tuesday 17 July 2018 22:59 Have you tried the Heal network under Node Management, this fixed a lot of the timeouts I was getting.

I have never had any luck with using that. Feels like nothing happens.
Only thing that sometimes work is rebooting.

Why do I get presume dead like it's don't try again, I wish I could reset that value.

Same here... For this I do a planned restore health every night.

Plantje wrote: ↑Wednesday 18 July 2018 9:28

Varazir wrote: ↑Wednesday 18 July 2018 9:19

mark.sellwood wrote: ↑Tuesday 17 July 2018 22:59 Have you tried the Heal network under Node Management, this fixed a lot of the timeouts I was getting.

I have never had any luck with using that. Feels like nothing happens.
Only thing that sometimes work is rebooting.

Why do I get presume dead like it's don't try again, I wish I could reset that value.

Same here... For this I do a planned restore health every night.

How do you do that ?

Varazir wrote: ↑Wednesday 18 July 2018 9:37

Plantje wrote: ↑Wednesday 18 July 2018 9:28

Varazir wrote: ↑Wednesday 18 July 2018 9:19

I have never had any luck with using that. Feels like nothing happens.
Only thing that sometimes work is rebooting.

Why do I get presume dead like it's don't try again, I wish I could reset that value.

Same here... For this I do a planned restore health every night.

How do you do that ?

Sorry, I was kinda busy...
You can do that here:

Plantje wrote: ↑Monday 06 August 2018 13:36

Varazir wrote: ↑Wednesday 18 July 2018 9:37

Plantje wrote: ↑Wednesday 18 July 2018 9:28
Same here... For this I do a planned restore health every night.

How do you do that ?

Sorry, I was kinda busy...
You can do that here:
Capture.JPG

No problem, I found the setting, I thought first it was going to be on each node.

Just want to say that for some parts of my network that "often do not function as expected"

Eg, I'll walk into the bathroom and it could take 10 seconds for the light to turn on which is unacceptable, I've applied predictive logic to try and overcome the problem.

Eg, If I walk into the hallway, THAT motion sensor will turn on the bathroom after 3 seconds AND the bathroom motion sensor will turn on the lights immediately (if working as expected).

It's unfortunate but I've not been able to get 100% functioning as expected with my Z-Wave network, I've tried Z-Stick ZME-USB Razberry and playing with just about every setting in OpenZWave etc.. and I've got about 6 Aeotec repeaters (because I thought strengthening the mesh would help).

Reliability issues are not unique to my Z-Wave setup either, eg I've got one Hue lightstrip that sometimes doesn't turn off on the first signal so I've got it in the Lua logic to send the signal a couple of times after waiting a bit. The visible effect is that it's working correctly (and I'm happy).

Then my Somfy RTS blinds and curtain being controlled by RFXCOM, I was having a reliability problem if not waiting 1 second between controlling each blind / curtain (so again I coded around the problem) waiting 1 second before sending commands).

My suggestion is don't expect 100% reliability from any system, you can work around a lot of problems by using Lua scripting logic.

Agreed, although I heard of someone who switched to Fibaro and had no issues anymore whatsoever.

I think I'm going to solder a antenna onto my razberry.

The node I have most problem with is one that is placed normally behind my computer in the room next to my controller.
Keeping that node in the same room as the controller it works fine.

Varazir wrote: ↑Monday 06 August 2018 23:12 I think I'm going to solder a antenna onto my razberry.

The node I have most problem with is one that is placed normally behind my computer in the room next to my controller.
Keeping that node in the same room as the controller it works fine.

Forgot to mention, I tried that as well (soldering an antenna to my Razberry), I didn't see any noticeable benefit.

I see a lot of timeouts in my system and what is strange to me is that there shouldn't be a signal problem. I live in a 2 bedroom apartment and there are as I said about 6 Aeotec repeaters and lots of Z-Wave devices everywhere. Why I am seeing timeouts to me does not make sense (thus I ended up coding around problematic situations as best I can, eg the delay problem with my bathroom).

I've tried Z-Stick, ZME-USB and Razberry (v1 and 2) (that makes 4 controllers total).

Yet my experience mentioned in the post above still applies.

ben53252642 wrote: ↑Monday 06 August 2018 23:18

Varazir wrote: ↑Monday 06 August 2018 23:12 I think I'm going to solder a antenna onto my razberry.

The node I have most problem with is one that is placed normally behind my computer in the room next to my controller.
Keeping that node in the same room as the controller it works fine.

Forgot to mention, I tried that as well (soldering an antenna to my Razberry), I didn't see any noticeable benefit.

I see a lot of timeouts in my system and what is strange to me is that there shouldn't be a signal problem. I live in a 2 bedroom apartment and there are as I said about 6 Aeotec repeaters and lots of Z-Wave devices everywhere. Why I am seeing timeouts to me does not make sense (thus I ended up coding around problematic situations as best I can, eg the delay problem with my bathroom).

I've tried Z-Stick, ZME-USB and Razberry (v1 and 2) (that makes 4 controllers total).

Yet my experience mentioned in the post above still applies.

Okay thanks for the info. Something isn't right...

To put it in Dutch:"Joh?"

since two days or so I am experiencing slow zwave response.
shutdown my raspberry, restart, al problems are gone.
today same issue. restart, all is well. after an hour again slow response.
I realized, two days ago I updated to 4.9992 .I really don't know if I had issues before updating. but I cant remember.
I also found a lot of timeouts in my log.
I just healed my network, and now it looks ok.. no more timeouts.

fingers crossed.

EDIT:
wow, 5 minutes later. the timeouts are back. very very strange.

EDIT:
I found out, I had 1 faulty z-wave device. A removed it, and now I have almost no timeouts and all is responding as normal again.

qwerk wrote: ↑Monday 10 September 2018 20:38 EDIT:
I found out, I had 1 faulty z-wave device. A removed it, and now I have almost no timeouts and all is responding as normal again.

How did you determine the Z-Wave device was faulty?

Plantje wrote: ↑Thursday 13 September 2018 22:28

qwerk wrote: ↑Monday 10 September 2018 20:38 EDIT:
I found out, I had 1 faulty z-wave device. A removed it, and now I have almost no timeouts and all is responding as normal again.

How did you determine the Z-Wave device was faulty?

after a while, this was the one with the most timeouts. responded the slowest.
and I guess a little luck

Ok, started analysing my situation for a little.
I have a few Z-Wave devices:

• Fibaro smoke sensors
• Greenwave power nodes
• Greenwave power strip
• Aeotec power node
• Aeotec multi sensors
• Danfoss Popp Radiator Thermostats

I get the timeout in the logs of only the three Aeon multi sensors I have. I have placed the multi sensors throughout my house; some even close to other Z-Wave devices that don't report time outs.
The Greenwave power nodes and power strip do blink green occasionally… as I understood that means they cannot report to the main station either. But they don't report time outs in the Domoticz log.
I will do more investigating, but at first glance it looks like a multi sensor is only reporting a time out as soon as it notices movement. So, a while ago, my wife and I were both in the attic an the multi sensor there reported time outs. Now my wife went back to the living room and I see time outs from the multi sensor in the living room coming in as well.
Seems logical that devices that have polling disabled don't present time outs.

I just did a "Heal node" for the three multi sensors. The one in the attic immediately started reporting timeouts again; the other two don't do that yet.
Next test: I disabled the motion detection of the sensor in the attic and healed the note again. A few more time outs came in and then they stopped coming in.
Meanwhile the two other multi sensors still don't return any timeouts since I healed the nodes.
Ah... now time outs from the living room sensor come in as well. Good to know that my wife is still moving.

For testing purposes I disabled motion detection on all three multi sensors and healed the nodes associated...The setting of motion detection enabled vs disabled is automatically reset. It seems less timeouts return, but they do still occur.

Again: for testing purposes, disabled polling on all three of them. The timeouts stop and obviously I get no motion detected signal as well. So, what's the use of a multi sensor if you're not polling it?

Edit: as I was typing this I saw a time out from the Aeotec power node as well...so much for my analysis... But that happens very rarely compared to the three multi sensors.