The particular issue with smoke detector has already been reported by @Mariano_Colmenarejo, so apparently it is a known problem.
FYI, my ‘Checking status…’ state I was seeing earlier has now disappeared, so this is definitely a random thing.
Oddly or not my smoke now says ‘checking’ no interaction from me
Galaxy s10
Not sure why this happens so wandering if you guys can speculate
Just realised the vedge smoke when activated pops up a note on the TV saying smartthings smoke detected, tbh I noticed it a day or so ago but it just dawned on me… why ?
Nothing else pops up on screen
Kind of cool; must be a Samsung TV feature - automatic integration with SmartThings STHM. I would think there would be a way to configure that (i.e. turn on and off) within the TV menus somewhere…
Quick advertisement: I’ve just posted a new ‘Web Requestor’ driver. You will now find it listed along with vEdge in my shared channel.
Don’t know how the TV plumbs in, but certainly something (be it the mobile app itself or the backend) defaults to sending notifications when smoke sensors are activated, just as it does when leak sensors activate.
It is a samy TV but the driver has not been set up within sthm in the app, I just checked
If a device changes state within the app or an automation does something notifications don’t appear for those
Perhaps it’s a safety thing built in that non of us usually get to see ?
Leak as well ! Not tried that yet
Dagnabit, terrible driver from Tod, no vedge leak sensor 
so can’t test that one
All I need to do now is figure out how to make a dumb smoke detector smart… yup I know there’s a thread but I simply can’t be ar#ed
Yes, those are the two - smoke and leak - that @orangebucket had earlier pointed out had an automatic tie-in to STHM. I get a notification on my iphone whenever I trigger those virtual devices. Note @Paul_Oliver 's earlier post about setting off his alarms when he tapped the switch on his virtual smoke detector!
Yeah I did read that Tod, there must be a bug though as like his setup, the vedge smoke does not show as a configured device in sthm, that cannot be correct
Is that a request?!
Hahaha… no Sir 
unless it is usefull to someone else
The point is that this behaviour is entirely independent of STHM. It’s broadly the same sort of idea as having low battery or offline notifications for devices (I think we still have the battery ones, though I don’t think we have offline at the moment). Unfortunately device notifications are all or nothing at the moment.
A virtual leak sensor would be useful.
I could use it to connect the overflow float switch in the condensate pump tank for my furnace and AC unit to STHM as a leak sensor. I could connect the float switch to my Zooz Zen16 relay. And use the virtual leak sensor to connect the Zen 16 to STHM.
It would need both leak and switch capabilities. I would prefer NO on/off button on the device tile.
Consider it done.
Thank you.
All - Wanted to give everyone a heads up that I am abandoning the Settings approach to creating devices because it is just too buggy and I have no information that it is going to be fixed anytime soon. This is painful because I have other drivers experiencing similar problems. A few weeks ago @orangebucket and I traded thoughts on the obvious alternate method of creating the devices by using button commands directly on the details screen, so that’s what I’m going to do. I’ve already got it working and am testing now. Many will find it easier, but you do lose the device count that was nice to have in settings. Therefore, one of my next tasks, which had been requested early on, is to figure out a way to display a full inventory count by device type. But that’s a future enhancement.
The waterSensor will also be included in the new driver.
When I push out this driver, I’m thinking about doing it as a new driver, as opposed to an update to the existing. That way if there is anything catastrophic, it won’t affect your already-running devices. You can keep running those under the original driver, and move those devices over to the new driver at your leisure. Anyone have concerns with this plan?
I wish Samsung would move as fast as you. They lack focus, try to bite off too much and never finish anything.
Thank you again for your work.
Thanks, it sounds like a good approach. Loss of device count is not an issue for me.
Thanks again for your hard work.
sorry for my trivial question, but what is this for? I came here on the advice of a user, to be able to use virtual devices with drive edge for the location of the smartphone. As virtual I understand that the position will always be determined by the device created by my smartphone and I will be able to make a rule to align the position of the edge driver with the real one of my smartphone. But what is it actually for? and what changes compared to the old virtual devices created by the IDE. If I check I see that the old virtual device is seen locally, while the new edge is seen in the cloud. Am I missing something? I’m sure there is an explanation that I still don’t understand
