Halo / Halo+ Smoke and CO detectors

driver

#21

@mike.maxwell any progress on this ?


#22

yeah, This thing has a pile of manufacturer specific custom clusters, so I needed to sniff it while being paired to an Iris hub, so I have the configuration settings now, no idea what's in these clusters, next step will be to sniff it while in test mode, hopefully I'll be able to determine from that what bits get twiddled for co and smoke...
Battery, temp and humidity follow the normal zigbee schema for those clusters, but worthless without smoke and co.
There's nonsense in this thing for messing with the RGB leds, I won't be dinking with any of that.
I'm hoping to get to the alarm sniffing tomorrow, tbd...


#23

so not going to be fun ? i wish i could find the groovy files for the plus and the normal halo

I wonder if smartthings would be kind and publish it seeing Halo is gone.


#24

It was requested:


#25

Can someone confirm this device still works in ST?
I was able to get the smoke alarm, but not the CO using the self test, not sure if the self test kicks off the co or not.
Anyway the Iris integration for the device is completely off line so couldn't poke in anything via that UI.

Not going to spend anymore time on this unless the ST driver still works.


#26

Yes it works


#27

Do you need anything from the logs in the ST IDE ?


#28

I don't suppose they have the usual copious amounts of debug logging enabled do they?
If so, maybe you can log the output of the self test...


#29
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug finalResult: [type:hushalarm, value:disabled, descriptionText:Hush disabled.]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: info Known DescMap : [raw:406604FD010801003003, dni:4066, endpoint:04, cluster:FD01, size:08, attrId:0001, encoding:30, value:03, isValidForDataType:true, clusterInt:64769, attrInt:1]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug description is read attr - raw: 406604FD010801003003, dni: 4066, endpoint: 04, cluster: FD01, size: 08, attrId: 0001, encoding: 30, value: 03
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug finalResult: [type:alarm_state, value:clear, descriptionText:Alert has cleared.]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug status false
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug status 0
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: info Known DescMap : [raw:0104 FD00 04 01 0140 00 4066 01 01 1201 00 01 00, profileId:0104, clusterId:FD00, sourceEndpoint:04, destinationEndpoint:01, options:0140, messageType:00, dni:4066, isClusterSpecific:true, isManufacturerSpecific:true, manufacturerId:1201, command:00, direction:01, data:[00], clusterInt:64768, commandInt:0]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:26 PM: debug description is catchall: 0104 FD00 04 01 0140 00 4066 01 01 1201 00 01 00
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:25 PM: debug finalResult: [type:alarm_state, value:clear, descriptionText:Test Complete]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:25 PM: info Known DescMap : [raw:406604FD010800003000, dni:4066, endpoint:04, cluster:FD01, size:08, attrId:0000, encoding:30, value:00, isValidForDataType:true, clusterInt:64769, attrInt:0]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:25 PM: debug description is read attr - raw: 406604FD010800003000, dni: 4066, endpoint: 04, cluster: FD01, size: 08, attrId: 0000, encoding: 30, value: 00
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:04 PM: debug Humidity has updated to 25%
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:04 PM: debug description is humidity: 25.28%
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:01 PM: debug finalResult: [type:alarm_state, value:progress, descriptionText:Test in progress.]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:01 PM: info Known DescMap : [raw:406604FD010800003007, dni:4066, endpoint:04, cluster:FD01, size:08, attrId:0000, encoding:30, value:07, isValidForDataType:true, clusterInt:64769, attrInt:0]
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:40:01 PM: debug description is read attr - raw: 406604FD010800003007, dni: 4066, endpoint: 04, cluster: FD01, size: 08, attrId: 0000, encoding: 30, value: 07
0160db9d-38c5-445c-ba72-0bf2078ba64a  3:39:31 PM: debug Start Test

#30

yeah, I noticed that the state of the self testing was being sent over the mfr specific cluster, but I'm not seeing the output of smoke and co separately, what you captured matched what the ISA alarm cluster (not shown above) produces...
I guess I'll have to have a smoke and then put this behind the exhaust of a car...

That's all the fiddling I'm doing with this today...

This device also includes an Absolute pressure sensor (kPa), which works, but apparently ST didn't implement.


#31

kPa is nice.... could use that to detect storms or fronts. Thanks for all your help @mike.maxwell !


#32

Any progress on this @mike.maxwell ?


#33

ha, so yeah..., today's funny story from my yesterday...

Pairing this to Iris really didn't expose anything of interest in the packet capture, their interface is all but disabled, though I got some binding and configuration data, but that was it.

So, based on user reports I paired it to my ST hub, and off to the races, device is there, doing what it's supposed to do, and this is the only time that I found ST's copious logging to be of value...
We find the command to test the thing, all the hush me up nonsense, ect...

But we still don't have any of the actual smoke/co alarm bytes, I was able to confirm my suspicions that the self test doesn't actually send them, and I now know what alarm clear looks like, but not smoke and CO detected, these are the last bits I need for this thing.

So I need to actually set this thing off to get the alarm bits, firstly I want to get the smoke going, before I start up my car and hold it near the exhaust for the CO... (don't even, its not my fault that a self test doesn't actually send the alarm codes, I didn't design this thing)

My office/lab is on the second floor, it has a window that has handy access to the first floor porch roof, I reason that at least I'm in close proximity to the hub and don't have to wonder if its chatting up the hub or not whilst I set it off.
This device has a rechargeable battery in it so I don't need to drag the ghetto fab AC power connection along with it.
I also have a cat, and said cat ignores me all day long, unless this window is open.

So I have a solid plan now, start the packet capture, grab the smokes the detector and close the window far enough behind me so the cat doesn't escape...

Off we go, out and closing the sliding window, I hear a faint click when it's about 4 inches from fully closed, which I completely ignore.
We have our little smoke test, never mind the neighbors wondering what that idiot across the street is doing on his roof with a blaring white object of some sort, we shut the thing up and head back in.

And now we find the meaning of the "click"..., its a pin that slides into the bottom track of the window and locks it in place when it's 4 inches from fully closed, awesome, and it's too far for me to reach, and the wife's not home, and all the neighbors have retreated and I'm looking at a 10' jump, right...

After some consideration on taking that jump, I see a USB cable on my desk that I can reach, and after a few minutes I succeed in making that into a lasso and snagging the knob on that stupid pin, and I'm back in the office, much looking forward to the telling packet capture that exposes the secret code bits for the smoke alarm.

I sit down in front of the capture, and I got nothing, no data what-so-ever, ???, well as it turns out this thing will not send any alarm data over zigbee when it's on battery, it simply goes to sleep, flat out nothing.

So now we have a new plan, which includes canisters of smoke and co test aerosol as well as proper power connectors to ditch the current AC feed..., that lot of bits won't be here for several more days...

So there you have it, there's your update!, aren't you glad you asked now?


#34

Next time just burn an incense to test the smoke detector. smell good too..


#35

LoL that's hilarious! You would be a awesome comedy author !

But in the end did you get any usable data ?

There is a group of us that's urging ST to publish the DH since Halo is OOB. Seems they are talking to whoever is left at Halo about publishing the code.

Maybe there is hope out there ?


#36

Yeah, most everything except what I really need, the freaking smoke and alarm bytes!
So when that test spray and power connector show up it should be cake.

I'll have this complete long before ST releases anything, if they ever do...


#37

And you are correct about the test... the device sends no data for it.


#38

That is some serious dedication to your customers right there!


#39

As someone who has five of them now and still looking for number 6 I greatly appreciate it Beer Money headed your way when done


#40

on their Facebook page right after they closed up shop they hinted that they would drop their API somewhere but it looks like it's never happened