Niick_W

Another odd thing I have noticed. When a switch (or motion sensor) is turned ON (and sometimes OFF) with the paddle you get two events like this (seqnum 911 and 915): <?xml version="1.0"?><Event seqnum="911" sid="uuid:114"><control>DON</control><action>0</action><node>34 CB 62 1</node><eventInfo></eventInfo></Event> [2020-12-10 12:19:51,134][DEBUG](pyisy ) Node 34 CB 62 1 (closetLight) received EVENT NodeProperty('34 CB 62 1': control='DON', value='0', prec='0', uom='', formatted='0') <?xml version="1.0"?><Event seqnum="912" sid="uuid:114"><control>ST</control><action uom="100" prec="0">255</action><node>34 CB 62 1</node><eventInfo></eventInfo><fmtAct>100%</fmtAct></Event> <?xml version="1.0"?><Event seqnum="913" sid="uuid:114"><control>_1</control><action>3</action><node></node><eventInfo>[ 34 CB 62 1] DON 0</eventInfo></Event> <?xml version="1.0"?><Event seqnum="914" sid="uuid:114"><control>_1</control><action>3</action><node></node><eventInfo>[ 34 CB 62 1] ST 255 (uom=100 prec=0)</eventInfo></Event> <?xml version="1.0"?><Event seqnum="915" sid="uuid:114"><control>DON</control><action>0</action><node>34 CB 62 1</node><eventInfo></eventInfo></Event> [2020-12-10 12:19:55,653][DEBUG](pyisy ) Node 34 CB 62 1 (closetLight) received EVENT NodeProperty('34 CB 62 1': control='DON', value='0', prec='0', uom='', formatted='0') The DEBUG output is my program (based on PyIsy), so that you can see the timing - there is about 4.5 seconds between the two events. I don't remember this happening before (but it's possible it was happening, and I just didn't notice). The event viewer does show the extra event (this is a different switch): Thu 12/10/2020 12:37:58 PM : [ 44 F0 C6 1] DOF 0 Thu 12/10/2020 12:37:58 PM : [ 44 F0 C6 1] ST 0 (uom=100 prec=0) Thu 12/10/2020 12:38:08 PM : [ 44 F0 C6 1] DON 0 Thu 12/10/2020 12:38:08 PM : [ 44 F0 C6 1] ST 255 (uom=100 prec=0) Thu 12/10/2020 12:38:15 PM : [ 44 F0 C6 1] DON 0 It's weirdly inconsistent, sometimes you get two OFF's, mostly you get two ON's. Is this another weird Insteon thing? or is the event getting duplicated somehow? This doesn't happen if you turn the switch ON/OFF with an insteon command, just with the paddle (because you get no EVENT reporting if you do that). It doesn't cause a big problem, as the ST value is only sent once, (and I mostly trigger off that), I do have some logic that looks for Faston/off events, and they trigger twice (but again it doesn't really matter). Just thought I would point out the odd double event triggering.

I would leave it, Zwave networks sort themselves out in time. They usually run a "heal network" overnight which sorts the neighbors out.

I upgraded without any issues. I have noticed an odd thing, which may always have been there. When connected via websocket, when I receive a RR update (Ramp Rate) for a device of type RelayLampSwitch_ADV, the formatted value in the xml is incorrect. It shows the unformatted value, in this case 28, when it should be 0.5 seconds. eg: <?xml version="1.0"?><Event seqnum="225" sid="uuid:99"><control>RR</control><action uom="25" prec="0">28</action><node>33 20 55 1</node><eventInfo></eventInfo><fmtAct>28</fmtAct></Event> All other RR values (and other settings) are formatted correctly, it's just RelayLampSwitch_ADV which is wrong. It's annoying, as I'm using the `formatted` value to get the real world values for things (which works well), except for this one value that I have to put a trap in my program for (not that I use it, but it messes up my logic).

Any news on the Leak Sensors fix? I want to upgrade so that my Aeon Siren 6 works, but I don't want to loose my leak sensors. If we are talking a few days, I'll wait, but if it will be longer I'll have to bite the bullet and upgrade (from 5.0.15A so not a big upgrade) and revert to other methods for leak checking... Thanks.

OK, good to know it's not just hidden somewhere.

I'm new to ISY 944i (but I've been programming Insteon devices for years). using F/W V 5.0.15A I've added all my devices to the PLM, and just added my Open/Close sensors (2843-222 v40 and v43). All seems good. I was wondering if there is a way to edit the configuration of these sensors from within the Admin Console, like you can with other devices? The developer notes show that there are several variables that can be changed for these sensors; such as send 2 groups (ie activate the closed group), repeat ON or OFF, LED On/Off, and set LED brightness. I have changed these values in the past (via various hack methods). See page 27 of the developer notes attached. I would expect a 'config" button at the bottom of the screen, but it's not there. is this functionality just not in the Admin console? Thanks, 2843-222dev-102013-en.pdf