Zwave not reliable

Tinkerer · February 28, 2020, 4:15pm

That’s a different log than the one I was directing you to, but … that can cause other issues

Delete /config/home-assistant_v2.db (or wherever it is if you didn’t use Hass.io/Docker)
Restart Home Assistant

Canedje · February 28, 2020, 4:40pm

So there is a method to update the zwave.me firmware?
where to find? or how to do?

Canedje · February 28, 2020, 4:42pm

Thanks again
I know you mentioned an other file, but I did see this happening at the log file

raymonvdm · February 28, 2020, 4:51pm

The only way to do this is installing Debian 8 on a system and installing Z-Way. I did mine using Virtualbox on Windows 10 and connecting the UZB stick to the VM

wget https://storage.z-wave.me/z-way-server/z-way-server-Debian-v3.0.0.tgz
tar xvfz z-way-server-Debian-v3.0.0.tgz
cd z-way-server
chmod 666 /dev/ttyACM0

apt-get install libcurl3
apt-get install libarchive13
apt-get install libavahi-compat-libdnssd1

LD_LIBRARY_PATH=./libs ./z-way-server

And then connect to the ip adres of you VM (might want to set networking to bridge for this VM)

http://192.168.xxx.xx:8083/

Then go to the Z-Wave node in the expert webinterface and check for firmwares, if it states that the firmware is up2date you need to use the code “all” to see the correct firmwares (also take note on the bootloaders)

http://192.168.xx.xx:8083/expert/

5.27 can give you an upgrade, 5.xx higer needs to be downgrade before you can upgrade to 5.36

Canedje · February 28, 2020, 5:11pm

Thanks again
sounds complex to me.
Is it possible to do it straigh on my Raspberyy Pi using a SSH?

raymonvdm · February 28, 2020, 5:14pm

Sorry, forgot you`re using a Pi. Yes it is possible but not on all version of Raspbian

https://z-wave.me/z-way/download-z-way/

Canedje · February 28, 2020, 8:45pm

The network is not responding again now.
No special message at the OZW_Log.txt.No sent-failed or so.
The traffic self is also not to much in my opnion

I recognize a pattern.
It looks like it is happening from 21:00 hour.
Im start running at that time an transition in 15 minutes for a RGBW dimmer in steps of a 1%.
I do use a node called lullaby.
I do have the feeling that this node is using to much system or so that stops the Zwave mesh to work.

I tried to switch by hand at the lovelace overview several switches. Nothing happening.
Suddenly after about 5 minutes or so the lights are switching on and off the ones i switched by hand.
Zwave is keeping in mind what I asked for, but is only able to execute after 5 minutes or so?

I realy don’t understand what is happening.

Tinkerer · February 29, 2020, 8:26am

It sounds like that “node” (I’m guessing Node Red) is overloading the capabilities of your Pi.

One thing to do is look at the light transition setting since with many integrations you can set a transition of many minutes.

Canedje · February 29, 2020, 8:56am

Thanks again. I did have an transition of 15 minutes.
I stopt that que as experiment
and do put a simple switch on and off que instead

Any ideas how to make a less intensive transition que?

Tinkerer · February 29, 2020, 3:03pm

Within Node Red? No idea, don’t use it. You’d want to open a new thread in the right sub-section here.

Canedje · February 29, 2020, 6:57pm

Thanks.

It is not the solution. Zwave still not reliable.
Special in the evening when light is on.
I do see a lot of traffic on one node. (node 2)
It is a neo coolcam wallplug doing nothing but be on.
I show a part of the OZW file:

2020-02-29 19:53:00.749 Detail, 
2020-02-29 19:53:00.749 Detail, Node002, Refreshed Value: old value=false, new value=false, type=bool
2020-02-29 19:53:00.749 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:00.749 Info, Node002, Received Meter report from node 2: Power=15.97W
2020-02-29 19:53:00.749 Detail, Node002, Refreshed Value: old value=15.98, new value=15.97, type=decimal
2020-02-29 19:53:00.749 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:00.749 Info, Node002,     Previous value was 15.98W, received 7 seconds ago.
2020-02-29 19:53:00.749 Detail, Node002, Refreshed Value: old value=15.96, new value=15.98, type=decimal
2020-02-29 19:53:00.749 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:00.749 Detail, Node002, Refreshed Value: old value=13, new value=7, type=int
2020-02-29 19:53:00.749 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:00.749 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:00.774 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:00.794 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:00.811 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:01.810 Detail, Node002,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x32, 0x02, 0xa1, 0x42, 0x59, 0x40, 0x00, 0x07, 0x59, 0x4a, 0xbf, 0x00, 0x80
2020-02-29 19:53:01.811 Detail, 
2020-02-29 19:53:01.811 Detail, Node002, Refreshed Value: old value=false, new value=false, type=bool
2020-02-29 19:53:01.811 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:01.811 Info, Node002, Received Meter report from node 2: Voltage=228.48V
2020-02-29 19:53:01.811 Detail, Node002, Refreshed Value: old value=228.58, new value=228.48, type=decimal
2020-02-29 19:53:01.811 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:01.811 Info, Node002,     Previous value was 228.58V, received 7 seconds ago.
2020-02-29 19:53:01.811 Detail, Node002, Refreshed Value: old value=228.49, new value=228.58, type=decimal
2020-02-29 19:53:01.812 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:01.812 Detail, Node002, Refreshed Value: old value=13, new value=7, type=int
2020-02-29 19:53:01.812 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:01.812 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:01.830 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:01.847 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:01.864 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:02.747 Detail, Node002,   Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x32, 0x02, 0xa1, 0x4a, 0x00, 0x06, 0x00, 0x07, 0x00, 0x07, 0xbe, 0x00, 0x82
2020-02-29 19:53:02.747 Detail, 
2020-02-29 19:53:02.748 Detail, Node002, Refreshed Value: old value=false, new value=false, type=bool
2020-02-29 19:53:02.748 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:02.748 Info, Node002, Received Meter report from node 2: Current=0.06A
2020-02-29 19:53:02.748 Detail, Node002, Refreshed Value: old value=0.07, new value=0.06, type=decimal
2020-02-29 19:53:02.748 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:02.748 Info, Node002,     Previous value was 0.07A, received 7 seconds ago.
2020-02-29 19:53:02.748 Detail, Node002, Refreshed Value: old value=0.06, new value=0.07, type=decimal
2020-02-29 19:53:02.748 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:02.748 Detail, Node002, Refreshed Value: old value=13, new value=7, type=int
2020-02-29 19:53:02.748 Detail, Node002, Changes to this value are not verified
2020-02-29 19:53:02.748 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:02.771 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:02.787 Detail, Node002, Notification: ValueChanged
2020-02-29 19:53:02.803 Detail, Node002, Notification: ValueChanged

This is going on for a long time.
Do you recognize something strange?
Why is there this amount of communiaction?

If I do a heal network. Everything reacting oke again for a (short) while
In day time I do not see this delays

Do you know how to check how busy my RPI is somehow?

Tinkerer · February 29, 2020, 8:34pm

Don’t do Heal network you’re breaking things.

However, that log shows that something is sending notifications over the mesh every second. Z-Wave is low bandwidth, having something that chatty may be causing you issues.

Canedje · February 29, 2020, 8:50pm

how to find this “chatty” device?

I do have an unknown node.
I am not able to remove that node somehow, not knowing where it comes from.
Can dat cause the problem?

Tinkerer · February 29, 2020, 9:05pm

Node002 - just look at the log you posted Look in Developer tools → States at your zwave. entities, and find the one that has an attribute of node_id: 2

Canedje · February 29, 2020, 9:06pm

I know the one
I will reset it and add it again

Canedje · March 1, 2020, 11:06am

A pitty. No succes again.
It looks like HA is not usable for me this way.
Zigbee and Zwave are the most important part of my domotica.
Very strange this happens. In Homey zwave worked fine. I had exactly the same setup in devices and flows
In day time everything is working oke.
In the evening there is some overload caused by something I don’t know and can’t find.

Maybe I give it a try to switch from Zwave dongle (AEONLABS).
and start all over again.
Is there a way to reset the zwave dongle?

I realy don’t know what the best is to do.
Any advice?

by the way: thanks for al effort you gave so far

Fishwaldo · March 1, 2020, 2:38pm

Replacing dongles etc won’t help. Node 2 is flooding your network. Check config options of node 2 about reporting frequency or percent change etc you need to stop it getting so chatty.

Canedje · March 1, 2020, 3:14pm

Thanks for the answer.
Yesterday I did unpair the node, resetted it and paired it again.
After that it was not chatty anymore.
But the network was still very slow and not reliable.
I will “tail” the messages of the controller for a while

In the mean time I did change all wallplugs the report by value change from 30% to 80%
and changed report time from 300 to 900 seconds
For the rest I don’t see interval consuming settings

At this moment the reports are coming in very slow.
Sometimes 10 sec. or there must be a PIR detection or so.
So at this moment the amount of traffic looks fine.
Every thing is reacting also as expected.

I will check again at night

Just a question:
I do have about 30 zwave devices. about half are router types (220V).
Is this much or just normal average amount of devices?

EDIT:
It is night and the most off my lights are running or activated by a PIR (Neo Coolcam).
The amount of traffic is still not realy high (I think it is about 1 message every 2 seconds or so)
Can it be something by the priority handling of the PIR’s?
Because the problem is that the lights are not switching on, on activating a PIR
And how to change that?
I do see this at the node settings at entity:

Do I need to change that setting?

EDIT 2:
I did change setting of all neo coolcam plugs to power change% 100% and update sequence to 1800sec. (I do have 10 Neo Coolcam wallplugs)
There is some improvement.
Sometimes the light is triggered within a second after PIR detection (1 out of 6 times or so) the other times it take up to 10 seconds to fire the light after trigger.
The improvement is that almost all actions are handled and non are lost.
The most device to trigger are Fibaro FGS223 switches (about 6) all are triggered by a Neo Coolcam PIR
The traffic is not that heavy in OZW-log. Sometimes every second a fire, sometimes 10 seconds nothing
I’m still not there but closer i feel
It still is not giving the same results as with Homey.

Canedje · March 2, 2020, 5:48pm

The result is still not acceptable.
I just added the last device.
I do have 31 zwave devices now. It is to much for the zwave USB in combination with HA.
Starting after reboot takes about 25 minutes get all devices up and running.

I just ordered an Vera Edge.
I will use it as a Zwave hub and control it by HA.

I hope this will be te solution.
To be continued

Canedje · March 4, 2020, 8:29pm

I using now a VeraEdge as an extra Zwave Hub, beside my Zwave.me USB.
I did bring over 12 of the devices to Vera (out of 30).
I tried to keep 2 goed networkmeshes beside each other.
At this moment the Zwave is reliable and working fine.
I’m happy
I will do more experiences in the near future, to find out if I can understand why the unreliability is happening.
Now the situation is stable enough to go on