Z-Wave PI name not consistent

[John245]

rjh
Is there a reason why the name of the latest Z-Wave PI is not consistent throughout the application. Z-wave under Plugins/Installed and Z-Wave core under Plugins/Add.


---
John

[Andrew_C]

Same question here...
I've been checking to see if I should update my Beta 3.0.4.0, (running on Windows) but I'm cautious about installing this new version, especially as the PI is not indicating "update available".

As everything appears to be working ok, then perhaps I'll wait a while. If it ain't broke...

Still, I'd like to know what the official update path is. Any info, anyone?

[randy]

The UI and core work together. The UI provides an HS4 GUI for Z-Wave, but will only work with Z-Wave core 3.0.7.0 (an HS3 plug-in).

You install core 3.0.7.0 for Z-Wave then the HS4 UI if you want it to look like an HS4 plug-in.

[Andrew_C]

Thanks Randy - but should I update my beta 3.0.4.0 if it's working ok? If so, do I simply install the 3.0.7.0 "core" as an update, or will it create a second instance?

I can't seem to find any definitive documentation.

As you can tell, I'm a bit nervous about the possibility of breaking a working system, but I do want to stay with the latest stable releases.

(PS - just noticed the time - 01:04 here now. I'm not ignoring any replies, but it's time to get some sleep. )

[randy]

Thanks Randy - but should I update my beta 3.0.4.0 if it's working ok? If so, do I simply install the 3.0.7.0 "core" as an update, or will it create a second instance?

I can't seem to find any definitive documentation.

As you can tell, I'm a bit nervous about the possibility of breaking a working system, but I do want to stay with the latest stable releases.

(PS - just noticed the time - 01:04 here now. I'm not ignoring any replies, but it's time to get some sleep. )

If it is working, you don’t “need” to update, you can stay at 3.0.4.0. I’ve seen no improvement or change going from the last production HS3 Z-Wave plug-in (even after switching to HS4). That said, I usually will run the latest versions (even betas), because I have a solid routine for rolling back if I discover any problems. If I discover any problems, I will email support. 3.0.7.0 is a production release, not a beta.

If you chose to update to 3.0.7.0 it will replace your current version, it does not create a second instance of the plug-in. I recommend disabling any plug-in before updating, just to make sure the executable is stopped. Most of the time there’s no issue, but occasionally it can be a problem.

[Andrew_C]

Thanks again, Randy - that's very helpful.

I'm with you on the roll-back preparation, I like the ease with which it can be done in HS. I agree on using production releases, too, so I think I'll probably take the plunge and move off the beta.

Despite over 20 years in HA, mostly using HS with X10 and RF devices, I'm still relatively new to Z-Wave (under 2 years). My caution arises from the potential need to restore the Z-Wave controller backup, if required.

Still - that sort of "fun" is what evenings are for!

[ServiceXp]

I updated to 3.0.7.0 a week ago, and immediately noticed some older switches status not being updated in HS. Yesterday I went to remove a device (door sensor) using the legacy mechanism, and it destroyed my entire z-wave network.

After the device was removed, the system started down this "confirmation" path that left over 25 devices without any settings. It was a complete and total loss. Nothing worked.

That is when I learned you cannot use an older z-wave back up with the new version. Long story short, I was able to get my system back to an early state (both HS and the Z-NET).

Now I'm trying to figure out how to safely revert my z-wave network back to the older version.

HS Z-Wave has always been troublesome for me, but this has been the worse failure I've experienced since 2016.

[Andrew_C]

I updated to 3.0.7.0 a week ago, and immediately noticed some older switches status not being updated in HS. Yesterday I went to remove a device (door sensor) using the legacy mechanism, and it destroyed my entire z-wave network.

Whoa! Could you specify your system a little, please? You mentioned "older switches", but all of mine are 2019 onwards, mostly Qubino, but a couple of Fibaro and Aeotec devices and the controller is an Aeotec Z-Stick Gen 5. Is that "older"?

I'm running HomeSeer 4.1.16.0 on Windows 10 Pro.

[ServiceXp]

Whoa! Could you specify your system a little, please? You mentioned "older switches", but all of mine are 2019 onwards, mostly Qubino, but a couple of Fibaro and Aeotec devices and the controller is an Aeotec Z-Stick Gen 5. Is that "older"?

I'm running HomeSeer 4.1.16.0 on Windows 10 Pro.

Most of my switches are Jasco/GE switches from 2014 - 2016. The offending Door Sensor was a 2014 Everspring Z-Wave Door/Window Sensor.

System below.

Date/time=8/10/2021 11:41:15 AM Eastern Daylight Time
Version=HS4 Pro Edition 4.1.100.0 (Windows)
License=Registered
Confguration File=C:\Program Files (x86)\HomeSeer HS3\Data\MyHomeSeerData.json
In Virtual Machine=No MFG: asustek computer inc.
Antivirus=Windows Defender
OS=Microsoft Windows 10 Pro - Work Station
OS Version=10.0.19043
Uptime=0 Days 18 Hours 6 Minutes 39 Seconds
Lan IP=192.168.1.26
Device Count=1215
Event Count=248
Processor:=Intel64 Family 6 Model 158 Stepping 10 at 3.44 GHz
Modules/Threads=133 Modules, 209 Threads
Available Threads=1023
System Load=330 Processes, 14% Load
Free/Total Memory=9.80 GBytes / 31.87 GBytes (31% free)
Free/Total Virtual Memory=7.42 GBytes / 41.39 GBytes (18% free)
HomeSeer Memory Used=176 Mbytes
Plugin Memory Used=25 EXE Plug-Ins using 1 Gbytes
Plugins Installed=AK GoogleCast 4.0.0.36,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLLock 3.0.38.0,BLSecurity 2.0.48.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.1,EasyTrigger 3.0.0.74,Honeywell WiFi Thermostat 1.4.2.2,HSBuddy 3.25.614.1,ImperiHome 3.0.0.40,mcsHubitat 4.4.4.2,mcsMQTT 5.17.3.2,MeiHarmonyHub 3.1.0.22,MySensors 1.0.5687.23871,PHLocation2 3.0.0.63,Pushover 3P 0.0.0.52,Restart 1.0.0.7,RFXCOM 30.0.0.41,rnbWeather 4.1.0.3,SDJ-Health 3.1.0.2,UltraLog3 3.0.6644.26753,Unifi 4.0.13.2,Z-Wave 3.0.7.0,Z-Wave UI 1.0.0.0

[Andrew_C]

Interesting... Hopefully my relatively recent (2019) entry in to Z-Wave might save me from such complications. My system is a lot smaller overall, with about half the number of devices. Thanks for your input - I'll post how I get on later.
Cheers.

System info:
Date/time=10/08/2021 16:57:04 GMT Summer Time
Version=HS4 Standard Edition 4.1.16.0 (Windows)
License=Registered
Confguration File=C:\Program Files (x86)\HomeSeer HS4\Data\Oasis.json
In Virtual Machine=No MFG: default string
Antivirus=Acronis Cyber Protect Windows Defender
OS=Microsoft Windows 10 Pro - Work Station
OS Version=10.0.19043
Uptime=26 Days 16 Hours 14 Minutes 0 Seconds
Lan IP=10.100.200.247 (HomeSeer)
Device Count=645
Event Count=159
Processor:=Intel64 Family 6 Model 92 Stepping 9 at 1.40 GHz
Modules/Threads=125 Modules, 114 Threads
Available Threads=1023
System Load=207 Processes, 6% Load
Free/Total Memory=901.07 MBytes / 3.83 GBytes (23% free)
Free/Total Virtual Memory=3.49 GBytes / 11.58 GBytes (30% free)
HomeSeer Memory Used=91 Mbytes
Plugin Memory Used=10 EXE Plug-Ins using 150 Mbytes
Plugins Installed=BOSESoundTouch 3.9.8.1,JowiHue 2.1.1.11,LIFX 4.0.5.0,MagicHome 1.0.0.354,Manage Voice Devices 3.0.0.0,mcsMQTT 5.17.3.2,RFXCOM 30.0.0.41,Sonos 3.1.0.57,TPLinkSmartHome4 2021.4.30.0,UltraGCIR3 3.0.6551.16959,Z-Wave 3.0.4.0