I am assuming that who ever is contacting them is letting them know that many users would like access to the handlers instead of a general email asking for publishing rights.
And what happens when ST code changes and breaks the DH ? Is ST going to fix it or just tell us we are SOL ?
@SGrayban, we’ve asked our certification team to work out and communicate the official support plan for these devices. We know many people own these devices including myself and other ST employees. Just speaking for myself here but I plan to keep it working as long as possible.
And that’s a good point… as staff you have access to the DH and can edit it or even use it for your own purpose while hundreds of us do not have that access and that is a huge issue.
What’s to stop staff from installing it on their IDE if they have to fix it to work again ? And that’s based on the plan you mention fails to keep it working or is met with resistance to even bother with it ?
This is why I said it’s abandoned code and should be 1) released into the public or 2) support should be dropped completely.
WIth the HALO app no longer working, is there a solution to run a test from the Smartthings app, or ensure I continue to get SMS notifications when it is triggered? I am new to ST but it seems that I can only control the lights for the Halo Device within the Smartthing app.
Is there any update on this? It’s been a month since the last update on this.
It has also been been removed from the SmartThings apps as a supported device
Wow that sucks but I’m sure the developers have a copy for their own use.
I guess I need to see if my Halo’s are still active in my setup still.
They still work fine in the app. They just don’t advertise them anymore as a supported device. Which I suppose makes a little sense. Hopefully they still pair properly, though.
@tpmanley, with that news does it help our case any to get that code published?
If ST no longer has it as a supported device, and the code isn’t available for those of us who still use these devices, we’re at risk of having these unmanaged devices stop performing w/no means of fixing anything, or worse yet, forced to replace them with something else.
We really need that DTH code made available.
Even more importantly, these really need local execution. All safety devices (smoke, CO, and leak sensors) should. Given the state and ambiguous nature of the code, I doubt we will ever see that happen.
Hubitat has managed to write a driver to support these, including the RGB lighting functions, so there’s always the possibility of porting that code to ST. Or porting my system to HE. 
SmartThings isn’t going to do the “right thing” here. So let’s drop it.
I have contacted the Halo people and the big boss said no. So that’s it. We have spent good money on shitty support from both sides.
I’m moving my stuff off the hub and moving to HE.
I’m not a Hubitat user (yet), so is there a way to get a hold of their code so I can give this a shot?
HE does not release any built in code.
What was the reason for not wanting to release the code?
Did Halo provide any sort of developer documentation that could be used to re-write a custom device handler?
Bummer. I would have thought they’d open that code up like ST does with (mostly) their DTH code.
All I got was NO.
yeah, surprising to hear Hubitat doesn’t put their drivers in a public GitHub.
I have a sneaky suspicion that many drivers are ripped from the ST git repo and they don’t want to get caught.
I just bought there of these. Is there any to color the RGB light settings in ST? (wife wants purple night lights) Should I even open the boxes? They sounded so good, guess I should have looked into it more before buying.
These are good devices, so I’d keep them. Yes, purple is there. Just tap on the color wheel in the lower right of the main tile.