Announcement

**SteveMSJ** · October 12, 2022, 04:47 AM

Originally posted by mworsnop View Post

I really dont understand this plugin but what it should do is fantastic! I have it setup and get errors all the time. Some of the ZWave devices have to be woken up manually to get the battery the best i know.a

Here is the email. Im not sure what to change. Thanks in advance! Sorry I am really slow on this one.

$Monitoring 14 devices
6 Missed: 8 OK
Last Alert: Wake-Up Missed
Battery Garage Garage Main Door Battery

Battery Downstairs Downstairs Hallway Battery
Last Wake: 10/11/2022 15:02
Last Sleep: 4 hours 36 mins
Battery Level: 99% (20)
Battery Rate: 5.2% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Downstairs Downstairs Hallway Battery
Last Wake: 10/11/2022 02:20
Last Sleep: 3 hours 13 mins
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Wake-Up Missed

Battery Downstairs Front Door Battery
Last Good Poll: 10/11/2022 15:25
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Downstairs Kitchen Window Battery
Last Wake: 10/11/2022 06:05
Last Sleep: 2 mins
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Wake-Up Missed

Battery Downstairs Living Room Motion Sensor Battery
Last Wake: 10/11/2022 12:31
Last Sleep: 12 hours 48 mins
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Downstairs Pantry Door Battery
Last Wake: 10/11/2022 04:03
Last Sleep: 1 hour 43 mins
Battery Level: 45% (20)
Battery Rate: 0.0% per day
Battery Life: 92 days (365)
Status: Wake-Up Missed

Battery Garage Garage Main Door Battery
Last Wake: 10/11/2022 11:31
Last Sleep: 4 hours 12 mins
Battery Level: 99% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Wake-Up Missed

Battery Garage Small Garage Door Battery
Last Wake: 10/11/2022 13:27
Last Sleep: 4 hours 1 min
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Upstairs Bed Blinds Battery
Last Good Poll: 10/11/2022 12:25
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Upstairs Upstairs Hallway Battery
Last Wake: 10/11/2022 15:10
Last Sleep: 11 mins
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Wake-Up Missed

Battery Utility Battery Cupboard
Last Wake: 10/11/2022 11:27
Last Sleep: 12 hours 3 mins
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Battery Utility Freezer Door Battery
Last Wake: 10/10/2022 23:06
Last Sleep: 2 mins
Battery Level: 45% (20)
Battery Rate: 0.0% per day
Battery Life: 92 days (365)
Status: Wake-Up Missed

Living Room Downstairs Battery
Last Good Poll: 10/11/2022 13:55
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Master Bathroom Upstairs Battery
Last Good Poll: 10/11/2022 10:55
Battery Level: 100% (20)
Battery Rate: 0.0% per day
Battery Life: 13 days (365)
Status: Healthy

Hi,

I'll need a bit more information about your system to be able to help. Can you post the following:

Your 'System Profile' from the help menu. The Message Board section not the Help Desk section.
A screenshot(s) of your 'SDJ-Health>Battery Devices' page, so I can see how you have the plug-in configured.
Details (manufacturer & model) of the 6 devices that are showing as 'Wake-up Missed'.

You shouldn't ever have to manually wake-up Z-Wave devices except to change configuration parameters which you would normally only do when you first install them. If you do manually wake one up then that will temporarily distort the wake-up interval and you will get a 'Wake-Up' missed alert, before the plug-in readjusts back to the normal wake-up interval for that device. For example if a device has a wake-up interval of 4 hours but you manually wake-it up 5 minutes after an automatic wake-up, the plug-in will temporarily adjust to a wake-up interval of 5 minutes. When it doesn't wake-up 5 minutes later it will alert for a missed wake-up. When it finally wakes-up automatically 4 hours later it will change back to Healthy and the plug-in will know to wait 4 hours for the next wake-up.

I can see some of yours are showing very short wake-ups, e.g. 2 minutes. Did you wake this device manually?

Steve

**mworsnop** · October 12, 2022, 05:09 AM

The device might’ve triggered, but I didn’t do anything specifically to wake it. Like opening the cover and pushing the button. The trigger would’ve happened by opening a door or motion. I don’t think that’s the same as waking it up, is i? The freezer door for example I did not open the door nor did they take it apart at 23:06

**SteveMSJ** · October 12, 2022, 05:20 AM

Originally posted by mworsnop View Post

The device might’ve triggered, but I didn’t do anything specifically to wake it. Like opening the cover and pushing the button. The trigger would’ve happened by opening a door or motion. I don’t think that’s the same as waking it up, is i? The freezer door for example I did not open the door nor did they take it apart at 23:06

You are correct in that a device sending a message such as motion, or temperature, isn't considered as a wake-up in terms of the Z-Wave pi. At the devices wake-up interval it sends a message to the Z-Wave pi saying basically 'I have woken up do you want me to do anything'. This allows the Z-Wave pi to send commands to the device if it needs to before it goes back to sleep. You said in your first post that 'some of the ZWave devices have to be woken up manually to get the battery the best i know' which made me think you might be manually waking them up.

If you can provide the requested information I will see if I can help.

Steve

**mworsnop** · October 12, 2022, 11:16 AM

I think you are saying that the devices should send the battery info by themselves. I think I have them set to 24 hours. I did this in the ZWave tab on the device in HS. I set the 24 hours and then manually woke up the device so it could receive the information. Before your plugin I had lots of events checking the battery level. Problem i had with that is they were not updating. Maybe thats the same problem I have now.

Maybe I need to make sure the devices are all set to wake up and send the battery every 24 hours. What interval do you recommend?

**SteveMSJ** · October 12, 2022, 12:03 PM

As I said previously, if you provide more information about your system I can try and help. Otherwise it’s just guessing in the dark😀
Different devices behave in different ways, and it might require some investigation of how they are set up and operating.

Steve

**mworsnop** · October 12, 2022, 01:04 PM

This is an example. The first line says polling is disabled. But the like with the battery says 12 hours interval. Do I need to find a way to enable polling?

**mworsnop** · October 19, 2022, 11:44 AM

If I understand properly most of the devices do not send a battery info unless they are triggered. Like a open close door switch would only include battery when the door is opened. Is that correct or are they supposed send battery every X hours as in the zwave device setup.

Looks like most of my devices have not sent battery info for more than a week.

**SteveMSJ** · October 19, 2022, 01:03 PM

Originally posted by mworsnop View Post

This is an example. The first line says polling is disabled. But the like with the battery says 12 hours interval. Do I need to find a way to enable polling?

What you refer to as the first line is actually the Root, or Parent, device. You should always leave this set to disabled for battery devices. If you poll the Root device Homeseer actually polls all the child devices which is unnecessary and likely to cause timeouts and battery drain. Your example shows polling enabled for the battery child which may or may not be necessary but is not a bad thing to have it set. Most modern battery devices don't need to be polled for their battery value but they only send it when it has changed by a certain amount, e.g. 5%, so it is infrequent and could be missed, hence leave the polling set. You would need to consult the documentation for a particular device to know exactly how it behaves, there are many different types.

If you have SDJ-Health set to LogToDatabase then it will build up a history of readings for each device which can be interesting to see how they perform and report over time. Some devices tend to stay at 100% for months and then drop off rapidly over a short period of time. Some decrease evenly all the way down to 0%, some die at a high value like 70%. The behaviour is not always consistent even with identical devices and can be affected by the type of batteries and the temperature. This is why it is a good idea not to rely to heavily on battery value but have alerts for missed wake-up set to catch dead devices.

Steve

**SteveMSJ** · October 19, 2022, 01:10 PM

Originally posted by mworsnop View Post

If I understand properly most of the devices do not send a battery info unless they are triggered. Like a open close door switch would only include battery when the door is opened. Is that correct or are they supposed send battery every X hours as in the zwave device setup.

Looks like most of my devices have not sent battery info for more than a week.

That isn't my understanding, although there are lots of different devices and no universal method between manufacturers. My experience is that most modern devices send a battery report when the level has changed by some present amount, usually 5% or 10%. It is deliberately infrequent to reduce battery drain. It isn't normally related to triggering. For example, a leak sensor may never be triggered but it should still report its battery as it runs down.

Battery devices will often go weeks between sending values for the reasons noted above.

Steve

**mworsnop** · October 19, 2022, 01:59 PM

about half of my devices are reporting wake up missed. I’m not sure what I need to change after reading what you just said. Do you have any ideas?

**SteveMSJ** · October 19, 2022, 03:07 PM

Originally posted by mworsnop View Post

about half of my devices are reporting wake up missed. I’m not sure what I need to change after reading what you just said. Do you have any ideas?

Start at message No 2 in this thread and I will try and help.

**mworsnop** · October 19, 2022, 05:28 PM

Date/time=10/19/2022 15:27:29 Pacific Daylight Time
Version=HS4 Pro Edition 4.2.16.0 (Windows)
License=Registered
Confguration File=C:\HomeSeer HS4\Data\HomeSeerData.json
In Virtual Machine=No MFG: minix
Antivirus=Windows Defender
OS=Microsoft Windows 10 Home - Work Station
OS Version=10.0.16299
Uptime=12 Days 1 Hour 33 Minutes 29 Seconds
Lan IP=10.215.81.4 (House)
Device Count=667
Event Count=192
Processor:=Intel64 Family 6 Model 76 Stepping 4 at 1.34 GHz
Modules/Threads=134 Modules, 100 Threads
Available Threads=1023
System Load=89 Processes, 2% Load
Free/Total Memory=1.12 GBytes / 2.00 GBytes (56% free)
Free/Total Virtual Memory=2.17 GBytes / 4.00 GBytes (54% free)
HomeSeer Memory Used=39 Mbytes
Plugin Memory Used=10 EXE Plug-Ins using 54 Mbytes
Plugins Installed=EasyTrigger 3.0.0.74,JowiHue 4.0.7.10,MNS Insteon 4.0.4.0,MyQ 1.2020.705.1301,Pushover 4.0.8.2,SDJ-Health 3.1.0.9,SmartThings 4.0.17.0,Sonos 3.1.0.57,Tesla Vehicles 1.9.0.1,UltraWeatherWU3 3.0.7806.23606,Z-Wave 3.0.10.0

**mworsnop** · October 19, 2022, 05:37 PM

Devices config and four of sensors that are saying missed

Attached Files

**SteveMSJ** · October 20, 2022, 03:47 AM

Originally posted by mworsnop View Post

Devices config and four of sensors that are saying missed

Hi,

Thanks for the additional information.

Firstly, probably unrelated to your issue, your Z-Wave info extract shows you have polling set in the Z-Wave plug-in for the root device of Node 6. I would recommend disabling that as it is not necessary and only likely to cause problems during the devices short wake-up.

I can see you are running the last release of the version 3 Z-Wave plug-in and have resisted any temptation to upgrade to the version 4 plug-in. That is a good decision for now as the version 4 plug-in still has some limitations on configuring polling and is anyways still HS3 legacy code behind the HS4 front end. You might want to consider the 3.0.11.0 Beta as I personally had issues with 3.0.10.0 which were fixed in 3.0.11.0, although that related to including certain devices. Probably best to leave it as it is for now though.

Usually this all works without issue but, if not, it can be difficult to pin down as there are lots of things going on. The best thing to do is to pick one device that is showing the issue and try and focus on that. If we can figure out what is causing the problem then it will likely apply to the others as well. Let's pick Node 5 the Downstairs Kitchen Window.

To see what is going on with wake-ups can you filter your Homeseer log using the following phrase:

Wake-Up Notification Received for Node 5

I can see your screenshot is showing a nice long uptime of 12 days. However, if you have restarted HS4 since that screenshot you might need to set the Start Date of the log so it is spanning at least a week. If you get nothing in the filtered log then try a search phrase of just:

Node 5

Post back what your log shows.
Post a screenshot of the status text of the SDJ-Health monitoring child for the Kitchen Window. It will look something like:
Also please post a screenshot of the SDJ-Health tab for the monitoring child for the Kitchen Window. Find the monitoring child/feature in list view, click on the device, then select the SDJ-Health tab, then click the 'Manage' button. This gives information about how the device is set up and being monitored as well as any local overrides of the SDJ-health options. It will look something like below:

I'm out for the rest of the day but will be back this evening.

Steve

Attached Files

Announcement

Getting errors - not sure what to change?

Getting errors - not sure what to change?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment