Aeotec Gen-7 Zwave stick, new firmware 7.21.3, still jammed controller and dead devices

I don’t see anything strange in the logs. Only that the coordinator is jammed and then is ready again. My devices are almost all the same as before. Compared to that I have some battery powered devices added, that are a sleep most of the time.

The Gen5 stick never jammed or had problem. The network was a lot more stable. So it does not make that much sense that it’s so unstable after switching coordinator.

I did one change this afternoon and disabled LR. The coordinator has not jammed since then. I had to disconnect and re-connect the coordinator because the whole network went down a hour after the change. Not sure that that fixes the problem.

What firmware version do you use?

I am on the same firmware version.

Also I am not the only person with the problem. :smiley: Read a lot of comments online, about people having the same issue.

I have seen some people with probs with 700 series, but hadn’t seen any 800 issues. What a shame as I find the 800 series range and performance so much better. I have been slowly moving from plus v1 to plus v2 for most things that I can.

So one thing.

I have no problem at all. But the first two weeks after moving back to the 500 sucked.

The culprit was yes partly the 700 stick but mostly:
Devices that are S0 joined when the don’t need to be
Devices spamming the network (chattty energy meter, dying fan controller)

Each incident by itself was able to crater my install like the 700 stalling issue but it was. Purely traffic. When I moved to the 500 stick I still had to fix THAT. Once I did it became stable as a rock.

So just moving to the 500 isn’t enough. Move AND Fix bad stuff on the network.

2 Likes

Thanks for the tip! Will have better look at it as soon as I get my new stick.

Is there a best practice to see what device is spamming the network?

Look at the RX stats for each device, write them down, then start working down the list from the chattiest one.

Or use this script

2 Likes

Nathan, are you planning to move to an 800, or happy to stay on the 500? I’ve had a 500 for years with 0 problems. Still eyeing to upgrade, but not sure if its worth the trouble.

I’ll move if I ever need LR. But I don’t expect to. Second thing that would make me move is end of support on the 500

1 Like

Thanks. Will inspect that and have a look.

After turning off LR, the network is more stable. Stick did not get jammed after that.

Still going to try the 500 when I get it.

How do I run this script on HA OS? I can’t seem to figure it out. Nor can I find the log files from zwavejsui you mention in the script post.

Figured it out. In the last 10k lines (from 7:10 am to 9:40 am) I get this:
740 038 49-0-Power
497 043 49-0-Power
435 087 49-0-Power
428 054 49-0-Power
377 025 49-0-Power
368 053 49-0-Power
221 005 49-0-Power
208 034 49-0-Power
203 050 49-0-Power
144 049 49-0-Power
121 047 49-0-Power
89 076 49-0-Power
46 033 49-0-Power
35 052 49-0-Power
35 038 37-0-currentValue
32 007 49-0-Power
31 035 49-0-Power
25 035 37-0-currentValue
19 038 37-0-targetValue
16 044 49-0-Power
14 021 50-1-value-66049
13 095 37-0-targetValue
13 095 37-0-currentValue
13 058 49-1-Power
13 035 37-0-targetValue
8 036 49-1-Power
8 021 37-1-currentValue
8 019 38-1-currentValue
7 058 38-1-currentValue
7 036 38-1-currentValue
5 083 50-0-value-65537
5 006 49-0-Power
4 087 37-0-currentValue
4 086 49-0-Power
4 051 49-0-Power
4 041 49-0-Power
4 024 37-1-currentValue
4 021 37-2-currentValue
4 021 37-1-targetValue
4 019 38-1-targetValue
3 081 49-0-Power
3 075 50-0-value-65537
3 040 49-1-Power
3 040 38-1-currentValue
3 034 37-0-currentValue
3 024 50-1-value-66049
2 093 49-1-Power
2 088 49-0-Power
2 086 50-0-value-65537
2 082 50-0-value-65537
2 082 49-0-Power
2 075 49-0-Power
2 072 49-0-Humidity
2 072 49-0-Dew point
2 072 49-0-Air temperature
2 071 49-0-Humidity
2 071 49-0-Dew point
2 071 49-0-Air temperature
2 068 49-0-Humidity
2 068 49-0-Dew point
2 068 49-0-Air temperature
2 060 49-0-Humidity
2 060 49-0-Dew point
2 060 49-0-Air temperature
2 059 49-0-Humidity
2 059 49-0-Dew point
2 059 49-0-Air temperature
2 057 49-0-Humidity
2 057 49-0-Dew point
2 057 49-0-Air temperature
2 055 49-0-Power
2 054 50-0-value-65537
2 046 50-0-value-65537
2 046 49-0-Power
2 045 50-0-value-65537
2 045 49-0-Power
2 042 49-0-Power
2 041 50-0-value-65537
2 037 50-0-value-65537
2 035 50-0-value-65537
2 033 50-0-value-65537
2 033 37-0-currentValue
2 032 49-0-Power
2 025 50-0-value-65537
2 024 50-1-value-65537
2 024 37-1-targetValue
2 023 50-1-value-65537
2 023 49-1-Power
2 022 50-0-value-65537
2 021 50-2-value-66049
2 021 50-2-value-65537
2 021 50-1-value-65537
2 021 37-2-targetValue
2 011 49-1-Power
2 010 50-0-value-65537
2 010 49-0-Power
2 008 50-1-value-66049
2 006 50-0-value-65537
2 005 50-0-value-65537
1 093 50-1-value-65537
1 088 50-0-value-65537
1 087 50-0-value-65537
1 087 37-0-targetValue
1 085 50-0-value-65537
1 085 49-0-Power
1 083 49-0-Power
1 081 50-0-value-65537
1 076 50-0-value-65537
1 070 49-0-Humidity
1 070 49-0-Dew point
1 070 49-0-Air temperature
1 067 49-0-Humidity
1 067 49-0-Dew point
1 067 49-0-Air temperature
1 064 49-0-Humidity
1 064 49-0-Dew point
1 064 49-0-Air temperature
1 063 49-0-Humidity
1 063 49-0-Dew point
1 063 49-0-Air temperature
1 058 50-1-value-65537
1 056 50-0-value-65537
1 056 49-0-Power
1 055 50-0-value-65537
1 053 50-0-value-65537
1 052 50-0-value-65537
1 051 50-0-value-65537
1 050 50-0-value-65537
1 049 50-0-value-65537
1 047 50-0-value-65537
1 044 50-0-value-65537
1 043 50-0-value-65537
1 042 50-0-value-65537
1 040 50-1-value-65537
1 040 38-1-targetValue
1 038 50-0-value-65537
1 037 49-0-Power
1 036 50-1-value-65537
1 036 38-1-targetValue
1 034 50-0-value-65537
1 034 37-0-targetValue
1 033 37-0-targetValue
1 032 50-0-value-65537
1 022 49-0-Power
1 019 49-1-Power
1 018 50-1-value-65537
1 018 49-1-Power
1 014 49-0-Humidity
1 014 49-0-Dew point
1 014 49-0-Air temperature
1 013 49-0-Illuminance
1 013 49-0-Air temperature
1 011 50-1-value-65537
1 009 50-0-value-65537
1 009 49-0-Power
1 008 50-2-value-66049
1 008 50-2-value-65537
1 008 50-1-value-65537
1 007 50-0-value-65537
1 004 50-0-value-65537
1 004 49-0-Power

Does not look to chatty to me. But perhaps I see it wrong.

Stick was also jammed again this morning for over a minute. Had to turn of a light and power plug. That’s all. :frowning: Really don’t get it.

Looking at the logs live, I don’t see anything spamming constantly. New logs arrive between 1 tot 4 seconds.

Doing the rough math, you have about 3200 updates (just counting the top ones) over the course of 150 minutes. That’s 21 updates per minute or one every 3 seconds. That is too much traffic. Start with the worst power meter at node 38 and reconfigure it to report much less frequently and only the data you are actually using, and work down the list from there. You are about 10x over where my network is.

2 Likes

Same… Granted I did it by pulling ALL my power meters off of ZWave. But when I had mine 15 seconds on a few plugs was the max I could allow before things got weird. But really do you need 15 second resolution on your power metering?

I get it if you’re using power meter to trigger something and want to know exactly when something happens. But most power triggered events I’ve run across no matter media need some kind of smoothing anyhow so you’re not getting real time anyway…

1 Like

Ok, thanks. I thought it was quite good. :smiley: Guess not. I will update them to once a minute. Should be just fine I guess.

1 Like

Completely understand. Thanks for the tips. Going to update the interval. :slight_smile:

If you are using it to trigger, most good power sensors have a threshold for a change before reporting. I’d recommend doing this as it will eliminate a lot of data. For example, my humidifier draws 60 watts when it is on, I have the change threshold set to 30 watts. If you have 20 power sensors each going off once a minute that’s still too much.

Thought process:
a) what am I using the sensor for? If not using eliminate. E.g. do you really need voltage, current, watts and watt-hours? Disable on the device and in HA.
b) what’s the maximum reporting interval or change that I can use? If it’s just power reporting then every 10 minutes should be fine. If it’s triggering, what does it trigger to, what’s a reasonable change threshold.

2 Likes

I mainly use it to check how much power it is using and to see if I need an automation to enable/disable it to prevent devices using power when they are standby, etc.

Just disabling it would be enough, to prevent it from sending data?

1 Like

The zwave device configuration should be updated to not send it or send it at a lower frequency / higher change threshold. If you disable sending voltage, for example, then I would also disable the voltage sensor in HA since it won’t have data. But disabling voltage in HA, will not prevent the device from sending it on the zwave network.

You may want to start by being fairly aggressive, because the first goal is to see if the zwave network can be stable. What are the devices you have?

1 Like

Hmmm ok. I want to keep track of the kWh to see how much everything uses my energy dashboard. I am ok with not reporting any power data every few minutes or at all. I only want the kWh to work and show the total usage.

I have the following in my network:

39 Fibaro power plugs
8 Fibaro dimmer 2
1 Fibaro motion sensor
10 Aeotec temperature sensor
1 Fibaro single switch
1 Fibaro double switch

1 Like

The energy dashboard updates stats once per hour as long as you have one power report during the hour it will get it.

If you do what Pete says you can absolutely drop that traffic by an order of magnitude… And then as to timers use how many reports doI want in an hour. (4- 15min, 2-30, etc.)

1 Like