HM-LGW and "triggering" smoke detectors

sathya · October 2, 2016, 5:17pm

Hey,

that’s really cool ! Actually I’ve probably never tested it, because you have to set the HM-CFG-LAN address in the init sequence. That’s why I probably assumed the sender address is fixed (or maybe I did test it - I can’t really remember). Could you send me the log excerpt of triggering the smoke detector? If it looks ok, I will change the source code .

Cheers,

Sathya

Wirrkopf · October 2, 2016, 5:17pm

Test using HM-CFG-LAN as Interface:

01/16/15 11:40:14.166 RPC Server (Port 2001): Info: Connection from 192.168.1.116:49191 accepted. Client number: 64 01/16/15 11:40:14.171 RPC Server (Port 2001): Info: Client number 64 is calling RPC method: setValue Parameters: (String) *IEQ0084244:1 (String) INSTALL_TEST (Boolean) 1 01/16/15 11:40:14.183 RPC Server (Port 2001): Info: Connection to client number 64 closed (3). 01/16/15 11:40:14.184 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B539440160B33FD09F7003F 01/16/15 11:40:14.599 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B539440160B33FD09F7003F 01/16/15 11:40:14.784 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B549440160B33FD09F7003F 01/16/15 11:40:15.219 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B549440160B33FD09F7003F 01/16/15 11:40:15.384 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B559440160B33FD09F7003F 01/16/15 11:40:15.838 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B559440160B33FD09F7003F 01/16/15 11:40:15.984 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B569440160B33FD09F7003F 01/16/15 11:40:16.459 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B569440160B33FD09F7003F 01/16/15 11:40:16.585 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B579440160B33FD09F7003F 01/16/15 11:40:17.078 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B579440160B33FD09F7003F 01/16/15 11:40:17.186 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HMK": Info: Sending (HMK): 0B589440160B33FD09F7003F 01/16/15 11:40:17.698 HomeMatic BidCoS packet received (LGW, RSSI: 0x4B): 0B589440160B33FD09F7003F

Test using HM-LGW as interface:

01/16/15 11:48:32.864 RPC Server (Port 2001): Info: Connection from 192.168.1.116:49340 accepted. Client number: 15 01/16/15 11:48:32.876 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: setValue Parameters: (String) *IEQ0084244:1 (String) INSTALL_TEST (Boolean) 1 01/16/15 11:48:32.882 RPC Server (Port 2001): Info: Connection to client number 15 closed (3). 01/16/15 11:48:32.883 Module HomeMatic BidCoS: HM-LGW "LGW": Info: Sending (LGW): 0B5A9440160B33FD09F70040 01/16/15 11:48:33.297 HomeMatic BidCoS packet received (HMK, RSSI: 0x4B): 0B5A9440160B33FD09F70040 01/16/15 11:48:33.301 HomeMatic BidCoS packet received (HMD, RSSI: 0x5B): 0B5A9440160B33FD09F70040 01/16/15 11:48:33.484 Module HomeMatic BidCoS: HM-LGW "LGW": Info: Sending (LGW): 0B5B9440160B33FD09F70040 01/16/15 11:48:33.896 HomeMatic BidCoS packet received (HMD, RSSI: 0x61): 0B5B9440160B33FD09F70040 01/16/15 11:48:33.898 HomeMatic BidCoS packet received (HMK, RSSI: 0x4B): 0B5B9440160B33FD09F70040 01/16/15 11:48:34.083 Module HomeMatic BidCoS: HM-LGW "LGW": Info: Sending (LGW): 0B5C9440160B33FD09F70040 01/16/15 11:48:34.495 HomeMatic BidCoS packet received (HMD, RSSI: 0x61): 0B5C9440160B33FD09F70040 01/16/15 11:48:34.506 HomeMatic BidCoS packet received (HMK, RSSI: 0x4E): 0B5C9440160B33FD09F70040 01/16/15 11:48:34.684 Module HomeMatic BidCoS: HM-LGW "LGW": Info: Sending (LGW): 0B5D9440160B33FD09F70040 01/16/15 11:48:35.097 HomeMatic BidCoS packet received (HMK, RSSI: 0x4C): 0B5D9440160B33FD09F70040 01/16/15 11:48:35.285 Module HomeMatic BidCoS: HM-LGW "LGW": Info: Sending (LGW): 0B5E9440160B33FD09F70040 01/16/15 11:48:35.698 HomeMatic BidCoS packet received (HMK, RSSI: 0x4A): 0B5E9440160B33FD09F70040 01/16/15 11:48:35.701 HomeMatic BidCoS packet received (HMD, RSSI: 0x5A): 0B5E9440160B33FD09F70040

Do you need more lines of the log or is this sufficient?

sathya · October 2, 2016, 5:17pm

Quelltextzeilen sind raus . Echt cool, dass du das herausgefunden hast!!!

Nachtrag: https://github.com/Homegear/Homegear/issues/165

Mythos · October 2, 2016, 5:19pm

If we are talking about “triggering” the smoke detector, does that mean that the siren can be enabled on demand?

Personally I am looking for an indoor siren that should be used in case an alarm was triggered (e.g. by a window contact). Thus it would be awesome if the smoke detectors can be used as indoor siren without any hardware modifications…

Wirrkopf · October 2, 2016, 5:19pm

Yes, you can enable the siren on demand.

Mythos · October 2, 2016, 5:19pm

That’s pretty useful. I really hope that the successor (the HM-SEC-SD-2) will be able to enable the siren on demand as well. Since I’ve read a lot about various issues with the current version I am still waiting for the release date of the successor model.

Wirrkopf · October 2, 2016, 5:19pm

I have 8 HM-SEC-SDs and haven’t had any real issue yet. I press the “calibrate” (or whatever) button every few months and I had only very few fake alarms.

Same with the issues some are having with the LAN gateway. I only had ~2 “hangs” in around 1,5 year of operation and I have played around with it quite a bit.

Mythos · October 2, 2016, 5:19pm

How many devices do you have in your configuration? As far as I’ve read in different forums the problems (hanging HM-LGW) mainly occur with complex configurations using ~100 devices or more.

Wirrkopf · October 2, 2016, 5:19pm

~ 70

Mythos · October 2, 2016, 5:20pm

Since the new HM-SEC-SD-2 has been released a few weeks ago I wondering, if the siren can be enabled on demand as it was possible with the predecessor?

Wirrkopf, have you already had the chance of testing the new version?

We are going to buy about 10 devices for our house but the on-demand triggering of the siren is a mandatory feature for us. Thus I would really appreciate to get any feedback about the “inofficial” feature capabilities of the new HM-SEC-SD-2.

Thanks in advance for any help!

sathya · October 2, 2016, 5:20pm

Hey,

it should work. I didn’t test it though. If it really doesn’t work, it’s easily implemented - I just would need two or three devices to test.

Cheers,

Sathya

HomaticWalker · October 2, 2016, 5:20pm

Hey! Could someone please tell me how to send the siren alarm using a HM-SEC-SD?

I have 6 of them installed and linked in one group. I am using openHab like:
Contact Smoke_Living “Living” (Smokes, Living) {homematic=“address=LEQ0017899, channel=1, parameter=STATE”}

and would like to use the siren like:
Switch Alarm_Signal_Indoor "Alarm - Indoor " (Alarm) {homematic=“address=LEQxxxxxxxxx, channel=x, parameter=xxxxx”}

how do I address the group? I my device list I have:
ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach
0x40000013 │ │ 25DF5B │ *LEQ0033668 │ 0042 │ │ ? │ No │ No
0x40000017 │ │ 25E1E8 │ *LEQ0034457 │ 0042 │ │ ? │ No │ No

Thanks a lot!

sathya · October 2, 2016, 5:20pm

Hey,

from the command line run:

or

Of course you can call “setValue” over RPC, too.

Cheers,

Sathya

Mythos · October 26, 2016, 10:36am

This would be so great.

I’m still looking for a combined siren (indoor alarm) and smoke detector. Thus I’m wondering, if the siren of the new HM-SEC-SD-2 can be enabled on demand or not.

@Wirrkopf, @sathya: Have you had any success in triggering the siren of this device?

sathya · October 26, 2016, 2:47pm

Hi @Mythos,

I still don’t have any devices to test. If someone would send them to me, I will implement it ;-).

Cheers,

Sathya

Mythos · October 27, 2016, 9:28am

I could buy some HM-SEC-SD-2 and send them to you.

Do you think that EQ-3 may completely prevented the siren triggering by firmware?

sathya · October 27, 2016, 12:33pm

That would be really great!

I don’t know, but I don’t think so. The detectors have to communicate with each other so the external triggering should be possible.

Cheers,

Sathya

cokefridge · June 22, 2017, 8:57pm

Hello everyone,

seems like I’ll have to dig this up
any success/news on the issue yet?

Best regards

sathya · June 23, 2017, 7:50pm

Hello @cokefridge,

the HM-SEC-SD-2 can be triggered by Homegear.

Cheers,

Sathya

cokefridge · June 25, 2017, 11:33am

Hello @sathya,

thanks for the info. I was a bit confused about the setValue part you mentioned earlier in the thread, so I asked the question in the OpenHab board. As I am still a newbie (coming from an annoying UI in the generally limiting rwe/innogy smarthome solution) triggering the alarm in openhab might be useful to someone finding this thread here (like i did)