@Brad_ST It shouldn’t be too difficult to change things on your end to reflect accurate humidity levels from Halo devices.
9:28:05 AM: debug Humidity has updated to 3400%
9:28:05 AM: debug description is humidity: 34
9:28:00 AM: debug Humidity has updated to 3400%
9:28:00 AM: debug description is humidity: 34
9:27:57 AM: debug Humidity has updated to 2600%
9:27:57 AM: debug description is humidity: 26
Level 1 support’s response was less than underwhelming (and factually inaccurate, as Halo has been compatible with SmartThings since the start). They choose to ignore long-time customers by keeping Halo’s DH top-secret while not fixing things that never worked properly. Most would argue that Halo’s software is open-source or at least abandonware at this point.
Hey there,
Thank you for contacting Samsung SmartThings Support.
As you stated that the humidity temperature is showing in thousand. I just want to let you know that the Halo devices are not compatible with SmartThings app. I request you to contact the developer of the Halo to resolve your issue.
If you experience any issue with the devices which are compatible with SmartThings app, please write back to us and we will be happy to assist you.
Thanks!
Mohd Zaki
SmartThings Support
LMAO, that made me laugh. Probably the best part was “I request you to contact the developer”. My reply would have been to tell him to email support@smartthings.com since they’re the developer and holder of the code.
@johnconstantelo My reply:
I respectfully disagree with that factually inaccurate response.
Halo devices have been compatible with SmartThings since the start. They connect and are recognized by both the classic and new apps. SmartThings has an internal device handler for these devices, and it has a long-standing problem that seems trivial to correct. You have the code, and It should be shared with those who want to fix it.
Please ask someone in level 2 support before replying with a blanket reply that is so blatantly incorrect. When in doubt, don’t – seek answers first. That’s what keeps customers like me happy.
@johnconstantelo A response:
Sorry for the delayed response. I appreciate your time and patience.
Once try to uninstall-reinstall the app and remove and re-add one Halo smoke detector to the app and check if it shows the correct humidity. If it shows the correct temperature, please remove and re-add all Halo smoke detectors to the app. If still they shows the incorrect humidity, please write back to us with the details and we will forward this issue to our support engineers.
- Mobile name and OS version
- SmartThings app version
Of course, we both know that doing all of these steps has no effect, so here’s hoping that the right support engineer takes this on.
I’ve been keeping an eye on a few of mine, and so far my humidity reports seem to come through ok:
Maybe doing that will help?
I tried over and over without any success. What version of the hub do you have? What is the firmware of your Halos?
I’m using a v2 hub.
All are at 0x26090028
Mine shows 2800% humidity. Any fix for this yet?
Not sure there is a fix to be honest. You could try removing the device and rejoining it, or try using the DTH titled “Zigbee Smoke Sensor”, wait a few minutes, and then go back to the Halo handler.
Hi everyone. I was previously the Lead Engineer on the Halo project and was a bit stunned to see recent posting on this page.
I still use my Halos today along with most of the engineering team. I’m going to read through the thread and see what I can do to help.
Originally we had hoped to release the handler, but that never happened.
If your out there still using Halo I’d love to know and I’ll do my best to see if I can help with “some” of the issues…though I cant make any promises.
~J
Awesome, and welcome!
I have 11 of the Halos, and one died last night. Won’t power up at all. I know the power is OK because another Halo works fine in that location. I ended up finding one on eBay, so I bought it. There’s a guy on Hubitat’s community selling 3 for $100 as well.
If you have any pointers for me to look at on the circuit board, or something else to check, I’d be forever thankful.
Man, I wish you guys had those devices back in the market through another manufacturer!!!
Also, if there’s any way to get the code released, please do!
I’m using mine. Non-plus version. Seems to work fine. ST had no problems finding it. Using “Halo” DH. Humidity is way off, as in most reports. 2,600%.
One of mine is reporting a problem with Ion Sensor. Should I remove & replace it, or do you believe it’s still functional, other than the Ion Sensing issue?
Mine is fully functional, except for the humidity measurement having the extra zeros. I think the measurement itself is somewhat accurate (36%) as my ecobee thermostat reports 42% in the next room over.
The hubitat DTH is public, I imagine it can be ported to smartthings really easily (in fact I think it probably is smartthings’ code)… I’ll have a look later
And if the official smartthings dth were to be released I could probably fix it, so I’d like to see that happen as well.
I found another issue which I’m wondering if any of you can confirm
If I turn on the light and leave it on, eventually it just turns itself off. No, I have no automation set to do this.
This is normal. I believe there is a 15 minute max or something like this.
Ah. Well it’s no biggie since none of my automations call for leaving it on more than a few minutes.
I have 8 Halos with 3 of them being Halo+ and they all work fine right now with no issue. Humidity reports correctly although I don’t necessarily use it very much but the weather radio in the plus works as well and alerts as it is supposed to.
Here’s an interesting couple of things.
I just replaced a dead Halo with a new one I got on eBay (never used). It joined and worked perfectly out of the box and beeped for 20 minutes warning me of the low battery. The Classic app actually showed the main tile with a red low battery warning message, while the new app was as dumb as a box of rocks with no message or warning. Great…
This one is on firmware version 0x26030027, with a target version of “Target Version: 0x26090028” AND it’s now showing humidity with a value of 4000 just like some of you guys are experiencing. Here are the values being reported since it was installed:
Let’s hope that when it finally gets to the newest firmware that this corrects itself.
@tpmanley, does the firmware update whenever it wants, or during a hub reboot, or how?