i am not looking to use it. it appeared in my linked services this week
It is not in my linked services.
I am having trouble movin gmy last z-wave and zigbee devices using DTHs to Edge.
In particular:
- Fibaro Motion sensor, keeps picking up the DTH when re-paired
Fibaro contact sensor, same as above - Aqara button (I have 2 already using drivers), same as above
Should I wait for them to be automatically moved to a driver? Does it work even if the driver is not a stock driver (the Aqara, while the Fibaros should work with stock Z-wave sensor driver) ?
Hi @sulisenator
Unfortunately despite the fingerprint being in the Smartthings official driver it never picks up the device, and installing the ST beta driver will see it picked up as a Zwave switch or generic sensor with no way to swap driver.
However, @Mariano_Colmenarejo excellent Z-Wave Sensor And Child Thermostat MC driver will allow it to pair correctly. You will need to uninstall the DTH device first which will exclude it from the Zwave mesh.
I found that after pairing i needed to put the device into pairing and send a setting (I disable the LED) to get all sensor readings. One of my devices then required a battery pull for motion events to work, not sure why this was.
Also, pair the devices near the hub or sometimes the device will be recognised as a zwace switch and youll need to delete and repair again
PS should have mentioned this is for a Fibaro motion sensor
I had the same issues with my Fibaro Motion. I had to remove the device, delete the Groovy DTH then add the device back in. FRI the driver for the Motion sensor sucks
Everybody’s under pressure, everybody’s annoyed when things that they count on stop working, and nobody knows what the impact will be on other people.
So…let’s help each other where we can, be understanding where we can’t, wish each other well whatever path we’re on. It’s a long road ahead.
Anyone come up with a solution for there Nest Thermostats?
With MyNextManager dead, I have been trying to move to Home Assistant for humidity automation, but that has been a bust as there “unofficial” integration is not maintained at all and there “official” integration does not have access to set humidity.
For such a specific question, I suggest starting a new topic under automation ideas with a ? At the end of the title and you’ll probably get more responses.
Sorry, is this the end of groovy that’s shutting down my smartapps?
if I try to reactivate them, the lever disappears and when the Smartthings app is opened again, the levers are down. If I try to enter each one and save, it gives me a network error… none of the routines connected to the devices of these smartapps obviously work anymore. I’m not complaining, I’m trying to contain my frustrations, I just want to understand
It is part of it. This part …
Groovy SmartApp Shutdown - Announcements - SmartThings Community
If you have a Samsung Galaxy device the life360 automations can be triggered by notifications on the phone using Bixby and then a Smartthings automation
no, Pixel and Oneplus. My pixel work fine with the ST geolog Oneplus not all time unfortunately
Sorry, is this the end of groovy that’s shutting down my smartapps?
if I try to reactivate them, the lever disappears and when the Smartthings app is opened again, the levers are down. If I try to enter each one and save, it gives me a network error…
Yes, the SmartThings cloud is no longer available for custom SmartApps (ones that you added yourself through the old IDE).
New community FAQ:
Why Did My Integration/SmartApp Stop Working in January 2023?
You can make one based on the humidity, but you cannot set the target humidity.
That was only available in the unofficial API.
Can you explain setting this up please?
Smartthings would be alot more powerful if we could enrol the Bixby options into ST as native ST triggers
And mine felt relieved when she learned that her credit card won’t be affected.