Yes, that’s the one.
I’ll give it a go. One of the switches is currently just 12-15 feet from the ST hub but I can move it closer.
Just as data point, I have other devices in the same rooms as these that are not having trouble.
I’ll report back.
Okay, I think I have a bigger issue. No matter where my devices are they will still show OFF from time to time even when they are physically ON and reporting up to date power information. And if I’m seeing the power reporting okay I can’t see how the devices have fringe connections … I could be wrong.
I am seeing this not only on the Aeons but on my just installed Zooz power switches.
The common factor between the two is these are my only Z-Wave Plus devices.
I am going to report to Support.
EDIT: Reported. If I get any info I’ll share.
So, this is what I got back from Support:
"Thanks for your detailed reply. I had a couple of peers in office and had a specialist look at your account to see if we could pinpoint the particular trouble with the devices reporting their wrong state in the app. Since these devices are using custom device handlers and also not certified and tested to work with SmartThings we do not have a way to determine where the specific fault in the reporting. Especially since this could be related to the device handler or it is possible that because of the amount of reporting some of the device handlers you are using in conjunction with each other that it is overloading your Z-Wave module or the device itself is failing to report its status to SmartThings.
I recommend reaching out to the SmartThings Community page for those specific device handlers and posting a message directed towards the developer who wrote the custom device handler. They will have a better idea of what could be happening as they wrote the code and would likely be able to help to see where the lapse in reporting is coming from."
I’ll reiterate that I am only getting this false ON/OFF state reporting on this device and the ZEN15 Power Switch. The devices will show ON for a period of time then suddenly show OFF when they have not been turned off (and are confirmed as physically still on and reporting other data). I wonder if it is an issue with the volume of reporting they are doing. Again, they are reporting power info just fine so it does not seem to be a signal issue.
I may try going back to the stock handlers for a while and seeing if that has the same issue because as of right now ST can’t help further.
So frustrating.
@jbisson, any luck with getting the github integration working?
@nezmo yup, this is their generic answer, as soon as you ping them with issues, if it’s a custom device handler, they won’t offert any support. I’ve been there, even If it had anything related the device handler…LOL Did you try with the stock device handler if you were experiencing the same issues? I got a faulty one that I needed to return so it could be possible that it is defective.
@stroh I made the change, I do believe it did the trick, thank you soo much.
Can anyone verify if it works now?
I have tried with the stock handler and the same issues exist. Supports wants me to remove and reinclude the device next. I have not done that yet.
Working here. I installed from the github integration, switched over to that version in devices, and then deleted the cut and paste version. All seems to be working, retained settings and last reset date of 14 days ago.
I don’t see this at all. In order to help me, could you provide the full detail under “my device” section?
should look similar to this:
https://drive.google.com/file/d/0BwpIB0iAJmxEczVfcjJ1cnVpSmM/view?usp=sharing
https://drive.google.com/file/d/0BwpIB0iAJmxEcEd4MzlOM0JnVDA/view?usp=sharing
Also, can you turn on “Enable Debug Loggin?” in the bottom screen of preference screen and send me the full set of logs? I want to see if it’s something that is causing this…
thanks,
Sent via PM.
@nezmo thanks, something looks very weird based on the logs, I forgot to ask to enable trace logging as well. Can you enable trace and provide the set of logs again?
Will do. I’ll report back.
Hi @jbisson,
It looks like SmartThings is detecting my Aeon Smart Switch 6 using your device handler as a light bulb instead of a switch. So when asking Google Home to turn on the lights, it also turns on this switch.
Is there anything I can to make SmartThings detect it as a switch?
I have no clue what could go wrong, seems like an issue with the google home and smartthing integration. I don’t have google home so I would not be able to tell.
There are no bulb or light capabability within the Aeon Smart Switch 6 handler, it must take the switch capability as a light? not sure sorry
I have been digging a bit further and I noticed that when I use this device handler, it looks like SmartThings also thinks it’s a light or a dimmer.
When I go to Automation > Add a SmartApp > Lights & Switches > Gentle Wake Up > Dimmers
If the switch is configured with this device handler it shows up, but when it is configured with the “Z-Wave Metering Switch” device handler, it doesn’t.
So I think Google Home is getting it’s info from the same place as SmartThings SmartApps.
The handler has the dimming and color adjustment capability for the LED light on the switch. It seems Google Home and Alexa take this capability and assume it’s a bulb. Not sure that can be resolved from the handler without removing the ability to configure the LED.
The stock handler has not implemented any configuration capability for the LED thus it shows up differently.
I’ve noticed this too, with Google Home. I had to go into the ST app, Automation/SmartApps, and open the Google smart app–and turn OFF the option of “Allow Google Assistant to access all devices and Routines”. Before I did that, someone could say “turn on the lights” and all my Aeon smart switches would turn on! Not really a safe option.
I am getting an error on configuration, specifically when setting minimumChangePercent to 10, I’m getting the following:
org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '10' with class 'java.lang.String' to class 'java.math.BigInteger'
Any idea?