Make sure you set up a static IP address for the Envisalink or you’ll lose it again!
I have been loving this new version using the Edge driver but something happened today and it is not working properly with Chime enabled. If Chime is enabled, any door that is opened will show as opened but will not register when it is closed. When I turn Chime off, this behavior goes away. With Chime off, all sensors register properly when opened and closed. Any idea what could be preventing this from working properly? Also, I’m not sure why it worked well for about 2 weeks without this problem, although I need replace a battery in a motion sensor so the low bat message isn’t showing on the keypad screen constantly now.
Yours had that extra comma in the keypad display when CHIME was turned on… I may need to adjust to handle that.
I don’t think it likes the “CHIME, Rdy to Arm” message on the keypad when Chime is enabled. Not sure why. Although I did have a problem is Chime back in April of 2020 with the previous SmartApp.
New version is being pushed out dated 2022-10-02T23:04:55.538247183. This should hit your hub within the next 12 hours, or can be forced immediately through the CLI with smartthings edge:drivers:install.
- Fixes capability labels. The “Unknown” labels should be gone now, but the new labels will be duplicated (no known way to fix this yet). Let me know if any devices continue to show with “Unknown” - I haven’t checked all of the device types to be sure that they look correct now, and have only verified that things were updated on Android. @ruinertt @johnconstantelo
- Cleans up history by not displaying duplicate events where more than one capability is displaying essentially the same information
- Cleans up the automation conditions options by removing unused statuses (“Arming away”, “Disarming”, etc.)
- Handles keypad messages that contain commas @jbjohnson77
2 Likes
It’s working exactly as you described, @philh30. Thanks for the work and heads-up.
All good here too. I don’t know if this will ever get fixed, or if this is the new way custom capabilities will have to be presented. I personally thing it takes up too much space and is repetitive, as you’d found out. I had to do the same thing for my water meter.
It’s working perfectly! Thanks so much for the quick fix on my issue. How can I make a donation to support your work?
@TAustin or anyone else that can offer assistance. I previously had a device handler installed on my Smartthings hub developed by @vadimb but it stopped working with ST. I instead saw that he mentioned this Edge Driver as an alternative so started with installing this late last week. I have everything installed successfully and it worked for a few days. Now it continually shows an “offline” status of all my alarm modes even though my HW Primary Partition is showing connected and in the Ready status. I can delete the alarm modes and then have the Primary Partition add them back and they show as Ready for a little while but then eventually fall into the offline deal.
Is anyone else having this issue or can assist with how to resolve? I will attach a screenshot of my ST screen so you can see what I am referencing. Thanks for any assistance you can provide.
I defer to @philh30; his driver and I’m sure he can help you!
I was successfully able to get the Edge Driver working (migrated from my EyezOn device handler). I experienced similar issues to ones you mentioned soon after setup, but someone they resolved on their own and never came back. Maybe try to recreate the device? Might also be useful to get a log dump to try to understand what’s going on (would need the ST CLI: https://github.com/SmartThingsCommunity/smartthings-cli)
— Vadim
| Tech_East
October 24 |
- | - |
@TAustin or anyone else that can offer assistance. I previously had a device handler installed on my Smartthings hub developed by @vadimb but it stopped working with ST. I instead saw that he mentioned this Edge Driver as an alternative so started with installing this late last week. I have everything installed successfully and it worked for a few days. Now it continually shows an “offline” status of all my alarm modes even though my HW Primary Partition is showing connected and in the Ready status. I can delete the alarm modes and then have the Primary Partition add them back and they show as Ready for a little while but then eventually fall into the offline deal.
Is anyone else having this issue or can assist with how to resolve? I will attach a screenshot of my ST screen so you can see what I am referencing. Thanks for any assistance you can provide.
Thanks for the info and link to ST CLI @vadimb . Any ideas after installation what specific commands I would need to run on the CLI in order to retrieve the appropriate log / dump file to assist with someone reviewing the data? Sorry kinda a newb at this…
Any other assistance would be greatly appreciated @philh30 
I’m away from my computer and unable to do any serious troubleshooting for a few days. I’ve never seen that issue but can take a look.
None of the devices should go offline unless you’re losing connection to the Envisalink, and then they should all be consistently online of offline together.
Np thx for your reply. If you get a chance to follow up when you are back at your computer I would certainly appreciate it. Thx you sir!
Can just follow these instructions to get the logs enabled. SmartThings CLI here.
Thx…I was able to get the ST CLI installer loaded on my PC and ran via command line. I was able to run the first line successfully to verify that the Edge driver was installed along with version, etc. I am having some issues running the second command which initiates the logging:
smartthings edge:drivers:logcat --hub-address=
Not sure what information to put where…I “think” I retrieved my driverID successfully from the first command: a232e466-eb39-4f8a…and I found my local IP address for my ST Hub just not sure exactly how to format that in the second command. Excuse my ignorance but this is what I tried:
smartthings edge:drivers:logcat <a232e466-eb39-4f8a…> --192.168.1.11=
But it didn’t work…
All you need is you hub’s ip address
So I don’t need “device ID” as indicated by the command? Let’s say my hub IP is 192.168.1.11 how does the formatting look for that specific command in order to start running logs?
Thanks…
Just type in 192.168.1.11 at the prompt for you ip address.
Apologies for being an idiot…but care to share what I am actually doing wrong since after the second command I am not getting prompted for my Hub’s IP address as you can see from below:
C:\Program Files>smartthings edge:drivers:logcat --hub-address=
The syntax of the command is incorrect.