We’ll these are quite frustrating situations. As the Edge platform is still in beta it’s possible this was just an anomaly - they seem to happen less often with zigbee & zwave drivers. Personally, I see regular cases where a driver (re)install doesn’t always run to completion, thus my recommendation to reboot the hub. But why you saw such a long delay before the driver started working again, is a mystery.
I recommend to anyone using Edge drivers to have the CLI available because with it, you can force driver reinstalls and monitor progress via log output.
Anyway I’m just relieved that your devices are working again; I appreciate the huge pain it would have been to have to recreate them and their associated routines!
Yeah my man, it was hard to go to bed w/o resolving it, especially since I rely on a lot of virtual switches to run automation w/ external services. And yeah, not being able to see logs is painful, so lesson well learned.
I hope all this Edge stuff stays stable because I currently have a total of 21 various virtual devices running using this driver. Thank you!
BTW, the one thing that I was running Webcore for to flip a Virtual switch On/Off when the v2 Hub was On/Off its internal battery power stopped working after the last Hub v2 firmware upgrade. So I’ve now had to switch over to a dedicated canary smartbulb solution which only triggers when power is restored. So do you know if SmartThings exposed the v2 Hub battery power condition somewhere in this new Edge programming language where it shows when the v2 hub is on battery power and when it isn’t? If they have, then since SmartThings themselves do not support any battery condition switch on their hub device driver, maybe a Virtual device could follow the On/Off battery condition to trigger routines when there is a power outage and restoration of power.
Not that I can see. If I display capability status for the Hub using the CLI, it shows a ‘bridge’ capability but nothing else. And it shows no status for ‘bridge’. If I display health status for the hub, it shows only deviceID, state (.e.g. “ONLINE”), and last updated date.
The bridge capability is a relic like actuator and sensor.
I don’t think the hub battery status is exposed in any way that it can be subscribed to. It might be tucked away elsewhere when you view the hub through the devices or installed-hubs endpoints but I can’t remember and I just got distracted by a device type for virtual devices that is now in the API …
Where are you seeing that? They had hinted this would be coming eventually for Edge drivers. My understanding was that it would allow for drivers to be created without having to specify LAN permissions. Hopefully it would still allow for try_create_device() method.
I’ve been completely reinstalling my Location in the last two days, as I thought it was about time I got it on the EU01 shard to match my UK accounts, and I also switched the ownership away from my personal account. Yesterday I was having problems with the first hub I migrated returning a 403 error when running logcat so I thought I’d give it a factory reset today. It still returns a 403 but more surprising to me is that it installs vEdge Creator 2.3 when I do a Scan Nearby (just the once unless deleted). I find this a little odd for two reasons:
The device doesn’t give me the ‘Driver’ option in the settings, and nor do any devices created using it.
The app and the CLI tell me that it is not enrolled in @TAustin’s channel and does not have the virtual devices driver installed. It was enrolled and the driver installed before the devices and hub were removed and supposedly factory reset, but I haven’t done anything since.
Confused? You bet I am. Did I forget to do something?
That is freaky! Sounds like a glitch in the matrix for sure. And it sounds like besides the Driver option not being shown, the virtual devices are functioning normally?
You didn’t say, but to prepare for this migration, did you delete all devices and remove all drivers from the hub first? Or did you leave everything intact?
I certainly deleted the devices. If I went wrong anywhere it would be in not clearing out the drivers thoroughly. Then again I didn’t expect anything to survive a reset.
If you tap on your vEdge Battery 1 device, what happens, nothing? Instead of ‘Unknown condition’ you should see something like ‘Choose what you want this device to do’, so clearly something is wrong with that device.
I’ll just echo @DaWeav 's comments. I’m having the exact same experience, including creating a second device with the same result. Battery Level works as a condition, Power Source does not.
