Just finished installing my Insteon Smoke Bridge and Onelink CO2 and smoke detector. It’s 9pm and can’t test it anymore until tomorrow morning but it looks like it’s configured properly from my Vera lite. I’ll let you guys know if it works.
What do you use to give to vera insteon capability ?
PLM 2413u
It sees the smoke bridge as a motion sensor. Pressing the test button on the smoke detector doesn’t trigger an alert so I’ll try using “smoke in a can” tomorrow to test it.
It doesn’t look like the smoke bridge works with Vera. I can get it to work with the 2413U connected to my laptop though. I guess I’ll be using HouseLinc on my laptop for now.
I was able to get the smoke bridge working on my Vera. I’m running a pretty recent nightly build of Altsteon, but much like with the built-in MCV Insteon support it shows up as a motion sensor but doesn’t trip when you press the test button on the bridge. I’m still pretty new at all this, so this probably isn’t the “right” way to get it working, but it works well enough for me so I thought I’d share the settings I found that worked. After I added it to Altsteon as a motion sensor with device category 16, subcat 10 (found using altsteon_cli), I’m pretty sure all I had to do was specify “I_InsteonTriggerSensor.xml” as the “impl_file” in the Advanced tab of the device.
After you modify the device and restart luup, check the smoke bridge’s device icon - if it’s showing up as tripped (red icon instead of green), go back into the Advanced tab, set “Tripped” to 0, and restart luup. The icon should be green now. Go over to your smoke bridge and press the button on the side once - the LED should change from green to red. Consequently, the smoke bridge’s icon on your Vera should have changed from green to red, showing that it has tripped.
One thing to be aware of - every time the sensor gets tripped you’ll have to manually reset it by going into the Advanced tab and setting “Tripped” back to 0. I’m sure there’s a way to fix that (something to do with the smoke bridge only sending data when it’s tripped, not when the alarm clears), but if your smoke alarms are going off on a regular basis you probably have bigger issues.
[quote=“joshw, post:5, topic:175035”]I was able to get the smoke bridge working on my Vera. I’m running a pretty recent nightly build of Altsteon, but much like with the built-in MCV Insteon support it shows up as a motion sensor but doesn’t trip when you press the test button on the bridge. I’m still pretty new at all this, so this probably isn’t the “right” way to get it working, but it works well enough for me so I thought I’d share the settings I found that worked. After I added it to Altsteon as a motion sensor with device category 16, subcat 10 (found using altsteon_cli), I’m pretty sure all I had to do was specify “I_InsteonTriggerSensor.xml” as the “impl_file” in the Advanced tab of the device.
After you modify the device and restart luup, check the smoke bridge’s device icon - if it’s showing up as tripped (red icon instead of green), go back into the Advanced tab, set “Tripped” to 0, and restart luup. The icon should be green now. Go over to your smoke bridge and press the button on the side once - the LED should change from green to red. Consequently, the smoke bridge’s icon on your Vera should have changed from green to red, showing that it has tripped.
One thing to be aware of - every time the sensor gets tripped you’ll have to manually reset it by going into the Advanced tab and setting “Tripped” back to 0. I’m sure there’s a way to fix that (something to do with the smoke bridge only sending data when it’s tripped, not when the alarm clears), but if your smoke alarms are going off on a regular basis you probably have bigger issues.[/quote]
Thanks, this worked for me. Specifically, in the device add ui I used “10,A” which is the hex version of “16,10” and it shows up. I haven’t gotten around to testing it though.
If there were some skilled person who wanted to shore up support, I have an extra smoke bridge and one link smoke/co alarm I’d be willing to donate to a serious developer.