I too am now considering Hubitat. The only reason I am considering Hubitat , is because I cannot handle spending 5 dollars every week for a new 2450 battery.
Multiplied by 5, which is the number of ST sensors that continue to kill by battery life after the firmware update. Some of those sensors are on their second battery in a week
1 Like
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
290
My advice on the ST branded sensors⊠throw them away and use the money to buy Iris Sensors⊠Theyâve never been anything but a problem.
Wait, itâs not a glitch??? You mean the update drains the batteries on any sensor that gets updated? I was hoping they werenât really dead, dam theyâre expensive
Thank God I found Hubitat, Iâm slowly moving over and DONE waiting for âmore local controlâ and putting up with forced updates
Totally agree on that point of buying Iris sensors. Esp if you are wanting or am picky about zigbee vrs zwave. Only times I buy ST sensors now is when the âfancyâ sensors go dirt cheap. The multipurpose is nice for its tilting and if it goes on dirt cheap sale Iâll buy another. Same with the water sensor. Just because Iâve not tried any others. But the open/close and motion sensors are great, and usually can be had on the cheap during sales. Another great reason to go to Iris for open/close and motion, both take cr2 batteries. Not that they are cheaper or last longerâŠat least they take the same battery. ST sensors are all over the place with cr2450 or AAAA or whatever else. My battery storage spot is rife with like 5 âuniqueâ batteries now which suck.
As for the comment about is this normal that ST goes quiet. YupâŠrelease an âupdateâ and maybe reply once or twice then go radio silent for easily weeks. Dont know if its âmaybe they will go awayââŠor if its âlets go heads down and fixââŠor what. But its very common. At this point, Iâve given up on the batteries. Until the device quits working all together Iâm just going to let the batteries complain. Iâve got two cr2450âs sitting here on my desk at 2.95 volts that ST said was 1%. So just going to wait for things to go belly up.
I agree about needed different kinds of batteries is annoying. I never knew that there were âAAAAâ and how many different coin batteries there are.
I purchase batteries and just blindly replace when they get low.
There is a solution for this, you can run all of your devices and automations on Hubitat and use an app called Other Hub to do a 2-way sync to virtual devices on ST hub. Those virtual devices can be controlled by Google Assistant. Your ST hub does need to stay on, but itâs just to act as a link to GA until the official HE/GA integrations gets approved.
Good luck! If you have a lot of automations using webCoRE or other smartapps in ST, you can replace the physical devices in the apps with the virtual devices created by Other Hub and leave your automations running on ST while you work on moving them over as well. I did this, and my migration was pretty seamless.
My process looked like this:
Reset device (this leaves the device listed in ST, but resets the physical device so it can be paired to a different hub)
Pair device to HE
Add device to Other Hub app (which replicated a virtual device to ST)
Replace physical device with virtual device in all ST smartapps and automations
Force delete physical device from ST
Later on, re-created automations from ST on HE hub, then removed ST smartapps
Perhaps we are victims of a business decision to stop testing and supporting updates for certain older devices, DTHs, or use cases with many devices. They ainât making money off us and will ignore the rants until we go away. Itâs common Samsung practice to encourage upgrades to newer products or cut off older services to cut their losses for failed programs like SmartThings.
In fact, just today Samsung was fined $5M for degrading mobile phone performance to force customers to buy new phones (link
Iâve been having what can best be described as scene weirdness since last Friday⊠Donât know if it is related to firmware but the timing is sure coincidental.