Passed activity scan but Invalid State

[mlevin77]

Hi, a few of my devices are showing "Passed activity scan but Invalid State" - but I don't see any error on it in the main Devices page. What does this mean?



and others say "Exceded inactivity period and failed poll" - I recently migrated my network from an Aeon stick to a ZNET device. Is there anything special to do to get these errors resolved?

[mda]

I am getting the invalid state error on all of my locks every night too (but their state looks valid in device view)

The summary is also saying 2 devices failed but the report says 3






Version: HS4 Pro Edition 4.2.0.0 (Windows)

OS: Microsoft Windows 10 Pro - Work Station 10.0.19042

SDJ-Health: 3.1.0.3

[mlevin77]

My locks always did this, but now I'm getting it on devices which aren't locks (and I'm on HS3).

[SteveMSJ]

Hi, a few of my devices are showing "Passed activity scan but Invalid State" - but I don't see any error on it in the main Devices page. What does this mean?



and others say "Exceded inactivity period and failed poll" - I recently migrated my network from an Aeon stick to a ZNET device. Is there anything special to do to get these errors resolved?

HS sets the Invalid State flag on a device when a command is sent but a suitable confirmation response is not received. If a subsequent command is successfully sent then HS will usually clear the Invalid State flag, although some times they stick and can be difficult to clear. The Invalid State flag being set is usually a sign of communication issues although they may be intermittent.

When SDJ-health does a scan it checks all the child devices of a physical device and if any have the Invalid State flag set it will note that against the Parent/Root. In your case I would suspect that at the time of the scan one of the children of the device had its invalid state flag set but it was cleared at the time you looked at the main devices page.

If you set the LogLevel to debug then, along with a lot of other log messages, the Ref of the child device that is in Invalid State will be logged.

Similarly failed polls are an indication of communication issues.

If you have recently migrated your Z-Wave network then the communication issues suggest that you have degraded performance which could be for many reasons. Resolving communication issues on a Z-Wave network can be a bit of a black art but there are lots of threads on the board, not all of which are helpful. A useful starting point is to look at the routing information using Z-Seer+ and/or 'Z-Wave>Node Information' and see if there is anything odd going on. Pay particular attention to devices that SDJ-Health flags as having issues. Sometimes problems can be caused by a rogue device flooding the network causing valid communications to be held up or lost.

Steve

[SteveMSJ]

I am getting the invalid state error on all of my locks every night too (but their state looks valid in device view)

The summary is also saying 2 devices failed but the report says 3






Version: HS4 Pro Edition 4.2.0.0 (Windows)

OS: Microsoft Windows 10 Pro - Work Station 10.0.19042

SDJ-Health: 3.1.0.3

Hi,

Locks tend to be more susceptible to communication issues which cause HS to set them to Invalid State. It might be an intermittent problem and the device might be operating ok, it just means that HS isn't always receiving a satisfactory response when it controls the device. That doesn't necessarily mean that the device didn't receive the command ok. I can't remember offhand how HS4 shows the Invalid State in Device View. Although I upgraded from HS3 to HS4 many months ago I haven't had any devices in Invalid State since HS3 days. You can always turn off reporting of Invalid State in SDJ-Health if you are happy that your network is performing satisfactorily with them.

As for the summary saying 2 devices failed but the report says 3, that's a new one on me that I have never seen! If you are consistently seeing that then I will have to dig deeper and see if I can find the bug that is causing it on your system. Perhaps it is undercounting when the errors are Invalid State, I will have a look if I can find anything.

Steve

[mda]

Locks tend to be more susceptible to communication issues which cause HS to set them to Invalid State. …

Thanks Steve. I did not have this problem on Hs3. Same locks, same z-nets, same locations of everything, same windows 10 pc

Since updating to HS4 I get this every night.

The locks all have direct routes and always test fine when I test communication to them.

I will try running debug logging and see if there is anything interesting.

If not, is there a way to disable invalid state reporting for just my lock devices?

Thanks!

[SteveMSJ]

Thanks Steve. I did not have this problem on Hs3. Same locks, same z-nets, same locations of everything, same windows 10 pc

Since updating to HS4 I get this every night.

The locks all have direct routes and always test fine when I test communication to them.

I will try running debug logging and see if there is anything interesting.

If not, is there a way to disable invalid state reporting for just my lock devices?

Thanks!

You can only disable Invalid State checking per interface so not just for locks i'm afraid.

Are any of the child/features of the locks hidden?

Try clearing all Invalid State flags, using the 'Reset' button on the 'SDJ- Health>General Devices' page and then manually trigger a scan.

If that still reports the locks as Invalid State do the same thing again with LogLevel set to Debug and capture the log for the period of the scan. You won't want to leave the LogLevel at Debug permanently.

There shouldn't be any difference between HS3 and HS4 as it is the Z-Wave pi that sets the flag, although how it is shown in device view may vary between HS3 and HS4. It might very well change between versions of the Z-Wave pi though.

Steve

[SteveMSJ]

If not, is there a way to disable invalid state reporting for just my lock devices?

As the locks are battery devices you are presumably also monitoring them in the Battery Devices section of the plug-in. I would exclude them from the General Devices section by selecting them in the 'Select devices to Exclude from checking' drop down. That way you can leave Invalid State checking on for your powered Z-Wave devices.

Steve

[mda]

Thanks Steve

Resetting did not solve the problem

They are not listed in the Exclude Devices pull down menu so I don’t have any way to exclude them

[SteveMSJ]

Thanks Steve

Resetting did not solve the problem

They are not listed in the Exclude Devices pull down menu so I don’t have any way to exclude them

It seems like there is something strange going on here. Are you saying that you used the 'Reset' button and then immediately ran a scan and they still showed as Invalid State failure?

When you click the 'Reset' button the log should show which devices it has found and reset. Perhaps set the LogLevel to Debug then click 'Reset' then click the 'Run' button for the Z-Wave interface both on the SDJ-Health General Devices page and let's see what is logged. Filter the log for SDJ-Health messages and post back here.

The exclude devices list should show all devices that failed the last scan as optional to exclude, so again something is odd. I will have to force one of my devices to Invalid State so I can do some debuging.

Steve

[mda]

It seems like there is something strange going on here...
Steve

i did the reset again, restarted HS4 and it seems to be ok now, thanks! I will keep an eye on it

[SteveMSJ]

i did the reset again, restarted HS4 and it seems to be ok now, thanks! I will keep an eye on it

Keep me posted.
Steve