Wired Wall Switches now reporting as if battery devices

[TimSRQ]

Recently, I've noticed a lot of wall switches reporting their state as "Unknown". They still can be controlled via Z-Wave commands, but don't update their status back to HS3. In investigating the problem, I've noticed that many problem switches are now reporting as if they are battery devices. For example, on the Z-Wave Controller Management page, I see the following message:

Error: The device Second Floor Master Bedroom Bed is not a normally listening node, and an attempt to communicate with it has failed. To use the functions on this page, please make sure the device is awake and ready to receive a command prior to selecting the function buttons below.

If I Test Connectivity to one of the problem devices, it may work or it sometimes will fail. But, eventually it will work. Also, if I Rescan the device, I tend to get an error similar to the following via the log file:

Dec-13 1:27:08 AM Z-Wave Node 4 is Z-Wave version: Lib: 3.4 App: 3.29
Dec-13 1:27:08 AM Z-Wave Warning Error getting version information for node 4, Send failed.
Dec-13 1:27:04 AM Z-Wave Node: 4 Supports Class(es): SWITCH_MULTILEVEL, SWITCH_ALL, CONFIGURATION, VERSION_V2, MANUFACTURER_SPECIFIC
Dec-13 1:27:03 AM Z-Wave Syncing Z-Wave nodes with device list...
Dec-13 1:27:03 AM Z-Wave Found 89 Z-Wave nodes
Dec-13 1:27:03 AM Z-Wave Getting Z-Wave node list for network DFxxxxxxx...

Other times, when I Rescan the device, I get a series of errors similar to:

Dec-13 1:35:59 AM Z-Wave Error Device Second Floor Master Bedroom Bed Optimization and Add Route result could not be determined.
Dec-13 1:35:53 AM Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object-> at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in :0
Dec-13 1:35:51 AM Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object-> at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in :0
Dec-13 1:35:47 AM Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object-> at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in :0

It's not consistent as to which devices tend to show up as Unknown. Some days only 1 to 4 devices have a problem. Today, I am seeing 19 with the Unknown status.

I've run a handful of "Optimizations" on the whole Z-Wave devices. This problem is mostly in the Smartstick+ Z-Wave. I have a Z-Net as well for the basement, and its Z-Wave devices seem to be generally ok.

I recently did a full system restore from a recent backup. The restore seemed to be without any problems but did not seem to resolve the core problems.

Does anyone have any suggestions of what I should be looking for to resolve?

[sparkman]

I've seen this on occasion before as well, typically after I've updated the zwave plugin. A restart has always resolved it for me. You may want to shut down HS, do a backup, rename zwave2.db in the data/zwave folder and then restart.

Cheers
Al

[TimSRQ]

Finally !!! Caution with FULLY OPTIMIZE NETWORK !!!

Ok, that did not work. But, it got me on the right path. I think I have fixed the problem now. I had plenty of backups as I am sure to create one after each substantive change in HS3 or adding devices. Here's what I had to do on my HomeTroller SEL:

0. Be sure to have a current backup of HS3 and your Z-Wave interface(s)
1. Factory Reset HomeTroller SEL
2. After HS3 restarts, factory reset the Z-Wave interface(s) (in my case, the SmartStick+ and the ZeeTroller)
3. Factory Reset HomeTroller SEL (again!)
4. Shutdown HomeSeer
5. Rename zwave2.db
6. Update Grub (see, https://forums.homeseer.com/showpost...0&postcount=17 )
7. Restore HS3 from recent backup

Most was working properly at this point!

8. I had to recreate all of the scenes for my Scene Controllers. This was fairly easy as I use events.
9. I had to delete any scene that updated/deleted codes in my ZWave door locks. These seemed to be corrupted.

Never, and I mean never, run Fully Optimize Network on the Z-Wave Interface:
NEVER: Plug-ins -> Z-Wave -> Controller Management -> <ZWave Interface - SmartStick+> Fully Optimize Network

I think the Fully Optimize network caused a lot of my devices to lose access to HomeSeer. Over a month ago, I saw the Z-Wave Networks and Options -> Z-Health checkbox option. And, being that I used to be a Vera user and that operation ran nightly, I activated the Z-Health to run nightly. It is around that time that many of my devices started to misbehave. Now, I have some Z-Wave plus devices, but mostly just Z-Wave. Many of my devices are 3+ years old. The older devices tend to fail if they can't find the interface quickly enough. And, this may be exacerbated by systems with a lot of nodes. I presently have well over 100 Z-Wave nodes and this equates to almost 500+ devices.

It's been over a week and all appears to be back to normal. Thanks again for your suggestion. It got me on the right path.