arzoo

It's now been four days running with the IOLinc wired up as when the issue first started and no problems to report. So at this point it's unclear what resolved the problem. Maybe the fact that the IOLinc was powered down for a few days? The only other significant change was the eisy was upgraded to the latest firmware. Regardless, the system seems stable and running as expected. Thanks everyone for helping with this crazy issue - it's been a learning experience!

When I first wired this up around 15 years ago, I had confirmed that the speaker output was 5vdc. I've tested this configuration multiple times and it always works - when the alarm siren sounds, the IOLinc is triggered.

I've been running with the IOLinc active on the network but disconnected from the alarm siren (no possible trigger) and have not had any issues. Just now reconnected the alarm siren to the GND and S (as was originally configured when all the problems started) and we'll see how it goes. The only other thing that has changed is the EISY firmware was upgraded.

That's a great idea, I'll try the IOLinc with it disconnected from the alarm wiring.

I'm using the IOLinc to voltage sense when the alarm siren circuit is active. It's a very simple method to detect when my non-network capable alarm system has been tripped. Yes, I currently have one Zwave device - an LED strip for bar lighting. I do see that Zooz sells a zwave universal relay (zen17) which I think could be used to replace the IOLinc. I might give that a try. But since Insteon is currently running a sale this month, I might also purchase a new IOLinc.

The IOLinc is 70.7B.5B The original one lasted 15 years until it failed back in May. When I replaced it I went with one listed as new open box (or something like that) to save $ which may have been a mistake. Although from what you're saying I should avoid the IOLinc entirely and go with a different manufacturer - any suggestions?

It's been three days since I unplugged the IOLinc 2450 sensor and the problem has not re-occurred and there's been nothing out of the ordinary in the event viewer. Next up I'll try I'll try plugging the sensor back in, but this time to a different outlet than the PLM. I don't see how the outlet would make any difference but I figure I'll give it a try. Assuming the problem comes back then I'm pretty confident the sensor is defective and I'll order a new one.

Would love to see Eufy integration also! If I could trigger of the camera motion detection, I could do away with a bunch of other Insteon motion sensors.

I don't believe I'm running any node servers. As for my EISY version, I just now upgraded from 5.7.1 to the latest (5.8.4). Not sure why I didn't think to do this sooner. I'll keep an eye on the event log and see if those empty program events ever 30 seconds have gone away (so far I'm not seeing any). Before I open a ticket I'm trying one last debug attempt; Looking back to my last EISY backup, I had replaced a defective Insteon IOLinc 2450 sensor. The sensor is hard-wired to the siren on my home alarm system - this is how I detect when the alarm is tripped. This got me thinking, could the actual alarm system be "doing something" at 52 past the hour and that (maybe combined with another faulty sensor or device?) is the cause of the crazy shit on the EISY? Also, that sensor is plugged into the same outlet as the PLM. I know it a long shot but at this point I'll try anything. I've disconnected the sensor and we'll see what happens tonight.

Good to know, one less mystery. Thanks! I turned off my phone for a bit and still getting the "Create REST U7" events every 5 minutes, so not the UD Mobile app. Maybe this is also normal for the IoX? Someone else also posted a question about this but there was no answer.

Cool, I won't worry about this then. Thanks! Hmm, I'll have to try and figure out which program is running in a 30 second loop but I'm pretty sure I've never configured any like that. As for the REST command, that's another mystery; maybe the UD Mobile app on my phone? Update: I'm sitting here watching the event viewer indicating a program is running every 30 seconds, yet the program summary tab shows the last program to run was 15 minutes ago?

I'm using a relatively new EISY; would the SIM card still be an issue?

Looking over the log from last night when the problem occurred and I see this entry: Mon 08/12/2024 01:51:57 AM : [D2D-CMP 004B] STS [55 FF B6 8] ST Converted values Event=0 Condition=0 prec=0 Mon 08/12/2024 01:51:57 AM : [D2D-CMP 004B] STS [55 FF B6 8] ST op=1 Event(val=0 uom=100 prec=0) is Condition(val=0 uom=51 prec=0) --> true I'm assuming this indicates that program ID 004B was triggered and ran the ELSE clause (IF evaluated as true), yes? This program is in a disabled folder and the program itself is disabled and no other program calls this program, so how is this possible?

I'm confused as to why the EISY would not include info in the event viewer to indicate that a program executed? This seems like a simple feature that would be very helpful for debugging? Why just add empty timestamps?

I powered down the EISY and PLM (for 30 minutes) a few days ago and thought somehow that might have resolved the issue as nothing went crazy for two nights in a row. But then last night at 1:52 so back to the drawing board.