Environment: V.2 hub, no battery. Large mesh for both Zigbee and Zwave sides. ~185 devces total.
Short version - my ZWave mesh was acting crazy yesterday around the time the FW came in.
Less short version:
I had done some recent ZWave repair procedures to recover from a bad (GE 14xxx) switch and possibly a ghost device. It was pretty bad before - I’ve an entire 1/4 of the house dropping on and off since last Sunday though I had managed to make it livable until I could chase it over the weekend. About the time the FW hit last night the whole thing took a nosedive and nothing on the ZWave side of my system was working correctly.
I don’t know if the performance was due to the mesh issues or the firmware, but in either case nothing was working correctly so it forced me to try to fix it last night. I forced a deletion of an ID I suspected was still in my system as a ghost (Created generic ZWave in IDE, gave it the suspect ID, deleted in newapp) then ran through a few repairs. After my last repair, I shutdown the hub until the IDE logs reported my hub offline (about 20 min - why not force a Zigbee heal while I’m at it…) then brought everything back up.
It seems really responsive and snappy this morning. Sorry I couldn’t tell you more about what action seems to be the repair, but figured you may have more info than I can see. PM me for the account / hub info if it would be important to the beta and you care to review the logs.
Thanks @nathancu for the feedback. I asked a colleague to look into your issues. I will say that in my personal opinion, network repair is not something that I am a fan of based on the experience or results we have seen over the years. A lot of the process relies on the devices and their stack to help heal and repair.
And while the repair is active, the process can be lengthy in time (waiting to hear back from the device and the mesh), anyway, that could explain if things did not complete in time.
As to how to fix the sluggishness of communication with certain devices? Honestly, I start with the route (as shown in the IDE) and go from there. I’d be happy to have our team to look into such issues if they come up again.
LOL, Hi @Kianoosh_Karami! All is well for me, but as you know, I’m almost all Zigbee now, with just a few Zwave devices left in my environment.
So far so good for me.
The only issue I’ve seen, which is more than likely not a hub/firmware issue, is that the mobile app is missing some of my devices within a particular Room, but they are there in the IDE and in the old Classic app.
Running 34.7 for 3 days now. No issues. Seems like the app and devices are more responsive. Loading the app seems faster. Seems like it is on the right track.
I was really frustrated with the lack of app and device responsiveness and seeming to go offline quite often. This beta release could be saving me from leaving ST
Had to restart hub after update (v2) Did not get back online after the update, but a simple restart fixed that. Now everything is working perfect. Using Fibaro z-wave switches and ST and Xiaomi Aqara zigbee sensor.
I was hoping this firmware update would fix an issue that started with the local health check… I have a number of Aeotec contact sensors that are always reported as OFFLINE while they are actually perfectly fine. As soon as you change their contact status they pop back up ONLINE just to drop off at some point.
I suspected it was a DTH related issue however I am using the generic ST one and not all of the sensors are having this issue. I excluded and included them to see if that would fix the issue, and ended up having to repeat the operation multiple times as part of the raw description was all zeros (library, fw version, not the product model etc.). I must say that the include/exclude, albeit it failed to complete properly many times, was much better than in the recent past.
I am also curious to see if this firmware update fixes a super annoying issue where many of my Homeseer dimmers and switches just completely look up (no zwave, no paddle response). I have to power cycle them to get things back up and running. It appears that this is not exclusively an ST issue as I’ve seen other reports from Homeseer users (no ST hub) but this issue went from once in a blue moon to multiple times a week especially when there are lots of people in the house (traffic related?? not that again!!)
Last, in the past few days, several of my automations that react to something (generally zwave) being turned on, or on a motion sensor (ST zigbee) to trun something on (generally zwave) are failing. I have no idea whether it is fw related (suspect not) but mention it in case others are seeing the same.
Firmware team - I’ve spent the last three days recovering my ZWave network, and now I’ve lost the entire Zigbee side of my install. Everything is showing offline. I have no control in the app, and attempting to rejoin a device does nothing. Can someone ping me in PM to take a look. I just uploaded the hub logs and I’m capturing app logs now. I rebooted the hub about 20 minutes ago to force a Zigbee heal and nothing is coming back unfortunately. I’m kinda stuck.
@Kianoosh_Karami: any chance additional firmware can be added to this beta to test this feature further? I would think the Inovelli switches/dimmers are more popular.
We are looking to do that. We are in active communication with many prominent Z-Wave vendors to attain their support and obviously firmware update files so that we can provide those in the upcoming releases. I fully realize that having support for 1 device is not all that useful or flashy per se, but our intent was to inform our users and vendors we have finally go around to provide the Firmware update support for Z-Wave devices so that in future we can increase that support device list to much more.
@Kianoosh_Karami, my IKEA Tradfri Repeaters have gone offline again. These devices are just repeaters. They don’t have any other functionality. Plugged in and that’s all. I noticed it today, that both of them went offline. I did see one of them yesterday being offline so unplugged and plugged it back, but the other is still offline. Do you guys want to give a try again and look what is pushing them offline, as it happened last at the previous firmware update?
I just had another zwave meltdown and after powering cycling the entire house due to many locked up devices, I ran a network repair trying to get rid of unknown devices in the routing of devices with issues.
The part that was unusual as I had never seen it before for zwave was a relatively large number of devices stating they were rejoining…
Is this new to this firmware? It implies that the devices were kicked off the network but I was unaware that was possible with zwave. When does that happen?
[2020-12-10 12:11:22.000 PM CST moments ago ] HUB zwStatus include search Z-Wave include search started
[2020-12-10 12:11:12.000 PM CST moments ago ] HUB desc 76 Powder Room Entry Light rejoined
[2020-12-10 12:11:12.000 PM CST moments ago ] HUB zwStatus device setup Z-Wave device setup started
[2020-12-10 12:11:12.000 PM CST moments ago ] HUB zwStatus device inclusion Z-Wave device inclusion started
That should be your Zigbee device, correct? I think it just happens to be timing related where your Zigbee device rejoined the network during a Z-Wave network repair.
please!)
