Also rename to dryer notification or something. For washer, people can use built-in ssmartthings lighting/power allowance and a smartthings branded outlet.
But in the US for electric dryers, many are 220 volts and are much harder to setup with power monitoring.
Also, dryer vibrations are probably going to be more reliable over more dryer models than washing machines, as many washing machines are very silent.
The link above does show the replacement app. It is the alternative column. On top of that if you still like the existing SmartApp, many include the code source so you can install it yourself. Most of the non-duplicate ones can likely be simulated with CoRE or WebCoRE.
I tried the same solution (placing a multi-sensor on the dryer) and could not get it to reliably work. I believe itâs due to my dryer being new and doesnât really vibrate much while running. Iâve tried everything from placing the sensor on the bottom of the dryer (where the drum should vibrate the most) to placing it on the door. It never went into âactiveâ for more than a few seconds at a time.
While I fully understand the deprecating of apps which continually break (such as the Netatmo integration) what I donât get is why ST is deprecating apps such as âLaundry Monitorâ and âMail has arrivedâ which they published, & donâ't rely on kludges nor third party devices to work.
JD, thanks for your quick reply.
I see I am behind the times in this area.
After some research, I find that the Alexa app now integrates with
RoutinesâŚbut not routines related to Smart Home Monitor. (they are
disabled). This is precisely what I was using Virtual Switches and the
SmartApp to accomplish (shame on me). I would however like the user to
have the ability to override this protection feature.
So it looks like I cannot continue to activate lighting, modify Modes,
and control SHM ⌠BY VOICE when leaving and arriving. Is this correct?
Any ideas?
You can use the feature that JD mentioned. Itâs actually a bit nicer than using a separate SmartApp. Or you can get the code from the list and create your own app based on that.
What you are describing is a different feature than the one that I mentioned.
It is true that if you set up a routine, then there is a chance that echo will be able to run it just from the routine name. But as you pointed out you canât have security features in the routine.
Thatâs different than what I mentioned. If you read my post again, youâll see that at the very end of setting up a routine there is an option to âperform automatically whenâŚâ And you can have the trigger for that be the exact same virtual switch that you are using now.
So your virtual switch comes on, and your routine runs as long as youâve Filled in the âautomatically whenâŚâ fields inside the routine itself.
Everything is the same as using âswitch activates home phraseâ except that you donât have to use that smartapp. Instead, the routine itself will look for the switch coming on.
Iâm sorry I canât give you a screenshot, as I mentioned, the current version of the mobile app is not navigable by voice. I suggest you contact support and they can walk you through it. Or maybe someone else can post a screenshot for you.
Itâs really simple to use once you find it, itâs just that the feature is a little difficult to find.
@slagle The support of ST was the only reason that I purchased the Netatmo. I understand if a company stops support devices or abandons and API that ST would discontinue it, but because you guys canât find a way to support it it just seems to be going backwards stop supporting devices. Iâm pretty disappointed.
No reason NOT to integrate Netatmo with Smartthings. @cscheiene did an excellent work on Netatmo handlers and his ongoing support is great. Been using his handlers with no issues for my 5 Netatmo weather devices⌠@thrash99er guve these a try, they work very wellâŚ
There a numerous flavors of laundry monitoring apps developed by community that work better than the one that is being retired. Just search laundry monitor and you will find plenty alternatives, or⌠you could always use webCoRE for any automation needs you haveâŚ
This is a great example of why a SmartApp was deprecated. Support would get tickets saying this used to work and now it doesnât, but really, it was an external factor that was resource intensive to pinpoint (and provided an all around poor customer experience).
1 Like
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
41
Thatâs exactly what the âMarketplaceâ is already!
i.e., a place for reviewed and vetted SmartApps to be published.