Thanks, missed that. I enabled Health Check and I do see the status "Online" in the Current States in your driver.
However, kkossev's Health Status app can't seem to find healthStatus state in your driver for some reason, and doesn't include it in devices available to add to his app. So this probably is a question that I should ask kkossev about. I'll hit him up.
It is probably a capability I need to add. But he will know it right away.
The capability is
capability 'Health Check'
Defining this capability also adds a ping() command, which I find very useful for checking the online status of the mains-powered devices and measuring the round-trip time.
Hey Krassimir, the docs say "HealthCheck" for the capability but I see my driver already has that capability in it.
So should it be "Health Check" with the space included?
My understanding is that there is no difference. The spaces in HE capability names are removed when the code is processed.
I did not know that. I'll do a little digging because it seems it has the necessary pieces for it to be working for @danabw
I would not spend a lot of time on danabw...that guy is a constant PITA around here, and you don't want to encourage him. 
FYI I did a quick test. If I filter by capability "healthCheck"
I see all my repeaters listed which all run the Zigbee Monitor Driver.
Must be something else in @kkossev code that is preventing them from being selectable.
I have two range extenders that are both showing this error in the logs:
I am running 1.0.7 installed from HPM
I am not sure when this error started but any ideas on how to fix it?
Should be a fairly easy fix. It does not harm your routing, just hampers your information. I'm working on a little project but I'll get in touch with you sometime next week to try out a fix.
Any update?
I don't have a device that generates that error but try this line :
state?.device?.controlR != null && parsed?.totalEntries != null ? state.device.controlR.totalEntries = parsed.totalEntries : null
as a replacement for this:
state.device.controlR.totalEntries = parsed.totalEntries
If that does not work I'll put it into a try catch structure that should handle it.
That was line 968 for me. I commented it out and added the new line. Ran through the refresh process and no error on either device I have running this driver. I will check the logs again later to see if anything shows up. THANKS
No new errors overnight so I would say that looks to have fixed it. Thanks
I will put out an update tomorrow if it continues to run clean on my system.
I have not seen any new errors
Thanks, I will update the package this weekend.
Update to version 1.0.8 to handle error in this linked post
Update available via HPM.
I read through the thread and didn't see any mention of anyone using the switch capability of the driver.
Using ZMD 1.0.8 did not change any preferences (all default) but did save after initialize.
I am running into an issue and getting an error in the logs using the switch capability of the driver. I tried three different devices with all causing same issue. A Sonoff S40 Lite plug, Iris IL03-1 V3 and a MHCozy Zigbee 1Ch relay.
The issue is when I click the run button to turn on the switch. The right section changes to off and red and clicking either section does nothing and generates an error in the log
Sequence below:
Refresh browser, driver appears as below.
When I click the run button in the right/on section. The "on" section on the right side changes to red and off. See below. The switch on the device does turn on.
If I click either run button I get this error in the log, the device does not turn off
dev:912025-04-27 23:23:31.519errorgroovy.lang.MissingMethodException: No signature of method: user_driver_garyjmilne_Zigbee_Monitor_Driver_695.off() is applicable for argument types: (java.lang.String) values: [off]
If I refresh the browser, the top image is shown again and I can then click the left run to turn it off ( and the plug does turn off) but the right side changes to red and off again. Bottom image.
The plugs do respond to external control (Node-Red) and turn on/off when commanded. So it seems as this is just an interface issue. The switch status under current states updates properly also.
Thanks. I can reproduce the error. Seems to be two things going on. The first is that off() command is now being sent the value off so it causes the error because the function off() does not expect any parameters.
The second thing with the on/off interface toggling I don't really know. If I comment out the on and off commands so it only uses the inherent ones then it works O.K.
I will send out an update in the next few days using these two workarounds.
I reported this interface bug here.
Download the Hubitat app
