That’s interesting. Appreciate the info and clarification! I’ll be sure to keep that in mind.
This was in regards to the other issue I had. I have an automation using a door contact sensor that would send me a notification if it opened. This stopped working - I assumed it may have been related to the motion sensor issue but clearly it wasn’t. I went in to the automation, made an update, then changed it back so the ‘Save’ button was not grayed out so that could re-save the automation. This was probably something with SmartThings based on your previous and recent comments about some of the new issues that have popped up.
In this post above, I warned that I would have to be releasing a new driver to fix broken buttons. However after having looked into this a bit further, from what I can tell the buttons are still functional, but just don’t look right (on iOS, they are always highlighted and blue-colored as if they are always in the ‘on’ state).
Because releasing a whole new driver would require everyone to have to re-create all their devices and routines, I’ve decided against doing that for now. But please report here any problems you may be having - particularly with the panel or zone device switches. It is entirely possible that there are unique issues between iOS and Android mobile apps.
That said, there are a couple updates I want to get out, so I am pushing out an update to the current driver. The new Envisalink 2.1 driver version is 2022-06-16T21:27:36.587540491. No action is required; this will be installed automatically to your hub.
I have the new driver installed. I’m using iOS and had/still have the always highlighted and blue-colored buttons as well as the “no cloud” icon under: Tap for additional partition commands.
This was the same as before the driver version 2022-06-16T21:27:36.587540491
All of the zones and the panel still appear to be functioning correctly.
Thanks for the report. I’m surprised about the cloud you’re getting for the additional partition commands field; that should not be happening. I’ll have to look at that further.
Todd,
I am trying to set a routine when the DSC is armed-away and the garage door is open, it will close the garage door. I tried the partition status and security mode as a trigger but, they are not responding. Nothing happens. When I look at the status on the properties of the panel, it shows when it changes from off to on. Any ideas? I tried the same routine but, just text. Same, nothing. I have other routines that work the same way but, not using the DSC panel.
@TAustin, wonder if you’ve seen this before - I want to upgrade to Driver version 2.1, so I removed all devices and the panels. Uninstalled the driver from the hub and installed version 2.1. I created the two partitions and zones, but for some reason, the primary partition would not create a device for one of the zones. I tried disabling and re-enabling the device under settings, but the partition would not create the missing zone. So I removed all zones on both partitions again, removed the partitions and the driver from the hub. I re-installed the driver to the hub. Using the CLI, the driver shows as installed on the hub.
This time around, the system refuses to create the first panel. I restarted the hub, removed the driver and re-installed it again, without any luck.
I made sure that there are no panels or zones (devices) left from the previous installation in the Samsung IDE.
Is it possible to force the system to create the first panel?
Thank you.
Hello! It sounds like you are having quite a frustrating experience, and I’m sorry for that! I don’t recall, do you have the CLI? I’m not sure what it could be. Perhaps you have another version of the driver still on your hub? I know you and I had earlier worked together and might have used an alternate channel for installing and testing interim drivers.
If you have the CLI, run this command to get a list of drivers running on your hub:
smartthings edge:drivers:installed
Run this command to get a list of all devices, just to make sure something isn’t showing up on the IDE:
Hi Tom. When the device would not create after the first install, I checked with the CLI that the original driver was uninstalled properly. I also checked that the new driver was uninstalled before trying the installation again.
Anyway, something went wrong with Smartthings of my hub during this process. The hub became extremely slow, and webCore routines either failed to run or only ran after a very long delay. Rebooting the hub did not help.
I left it overnight, and it appears to have recovered, although the system is still slow turning on some devices.
The Panels showed up as well as the zones/devices, apart from one or two. I got the system to create these zones by changing the troublesome zones as “unused” in settings, waiting for 15 minutes and then marking them as “motion detector” again.
Thanks for your response.
I’ve heard of some very flakey things like you described happening with people’s hubs.
You did the right thing in setting problem zones to unused and then back again. I’m glad that worked OK for you.
Let me know if you have any other problems. I’ll warn you that due to a change in the platform, the switches on the panel devices for arming away or stay, are always showing highlighted blue, but they are still functional. Normally they should go grey when switched off. The next driver update I do I will try to correct it; the challenge is to fix it without causing disruption or the need to delete and re-create devices!
The other platform issue at the moment affects iOS users: the field labels are not showing correctly on the device Controls screens. This has already been reported to SmartThings, so hopefully a fix will be made sooner rather than later…
Sorry Todd, my apologies.
I’m primarily an Android user, but noticed the missing labels on my iPad.
I’ve had further issues and in the end, I was unable to Arm/Disarm the alarm from the app. When arming the alarm manually, the app showed the alarm status correctly, but the commands from the app to the alarm had no effect. In the end, I removed all zones and panels again, but without uninstalling the driver this time. I added the primary panel without any zones and only once the primary was working fine, I added the second panel. The panels are working perfectly now and I’m able to arm/disarm/send notifications using the Sharptools Rules Engine.
I’ll run the setup without the devices for a few days before adding the devices a few at a time. I don’t know if adding all the zones at once could be overpowering the hub? (I have the Version 2 hub; 16 motion zones on the DSC panel.) I remember having a similar experience when I initially using AlarmServer - it was as if the hub could not deal with all the messages coming from all the motion sensors and it slowed the whole system down - after a few days, things seemed to return to normal again.)
You might want to take it slow when you configure each zone setting: just waiting a second or two between each one you save. I’m just guessing but maybe it is true that trying to create too many too fast could be causing problems.
I finally found this in an earlier post…
“The other platform issue at the moment affects iOS users: the field labels are not showing correctly on the device Controls screens. This has already been reported to SmartThings, so hopefully a fix will be made sooner rather than later…”
