peekay

The browser actually blocks the connection (silently) after clicking "trust anyway" on either the iPad (Safari) or Linux (firefox). Thanks for confirmation it works.

If the certificates are signed by UDI then it is not that hard to allow a FQDN (xxxxxx.isy.io or something) that resolves to a private IP address and properly uses PKI. You don't have to have a server publicly resolvable to use certbot, you just use DNS txt file authentication. It is a solved problem. Sure, it might not be for everyone, but it is a completely valid approach. Compared to the complexity of working with the admin console and all its quirks, setting up certbot really is trivial. I'm starting to feel like the complexity of managing links directly for Insteon is also worth the pain compared to design decisions that have stuck around with UDI for over a decade that still limit usability for me today.

That doesn't work with a FQDN or from a separate VLAN. As is common security practice, my IoT equipment is in a dedicated VLAN (actually a few different ones), and communications between VLANs controlled by the firewall.

That should be easy enough. Wow, that is a major design flaw! Requiring communications via an insecure communications method?!

That doesn't work because many browsers force https and fail silently or with obscure errors.

I keep coming up with errors on my iPad and Linux/Firefox desktop trying to run the Polygot_v3 dashboard that really appear to be issues with the self-signed certificate. Are there any guides or known problems with running certbot on the Polisy with DNS verification? My Polisy has a proper FQDN (only accessible via VPN). Is the certificate used the one in /etc/ssl, or are there multiple locations that need to be linked?

Something was happening between my Insteon serial PLM, my ISY994i, and my house. I've had a Polisy Pro laying around for a couple years with no practical use, so I decided to try it instead. Michele gave me the link for the updated SSD firmware and I installed it. After getting IoX loaded I tried the serial modem, but likely had screwed up the DB9-RJ45 adapter pinout. Don't know now because I broke it trying to troubleshoot. I removed the serial modem and deleted it from IoX. Now the USB PLM has arrived, and I tried to plug that in to Polisy and restore. IoX reports a DHCP error and 0.0.0.0 v0 not found when checking PLM status. I don't know if it is related, but I also cannot reach the Polygot V3 dashboard, although the admin console works fine. The login page appeared once or twice out of many attempts, but I was never able to log in. My IoT VLAN is locked down by the firewall, and IPv6 traffic is not routed. Polisy is allowed full access to the LAN and WAN. Any help on what to try next?

I have tried different cables, but I will open up the ISY and see if there is anything odd (corrosion) inside, and also see if I can hook it up to the Polisy instead-- forget if I still have the cable/adapter for it.

When I just re-restored the PLM I got this error message: The previous time I got the "no network connection" error as well, but communications were fine over the network. Not sure if it is relevant. After the restore completed the communications is still broken.

Well, back on this. I got the PLM refurbished by Insteon, and there is no change in the behavior. Not sure if they just replace the bad capacitor that used to be problematic or if they do more work. When I was updating the modem from the ISY there were no surprising errors-- just stuff that had been removed from the system, plus one exception of an active device when refreshing status. (The two adjacent Insteon devices, physically and electrically, were fine.) Then, as before the PLM stopped responding.

If it lasts me until March then I can get a new one... the problem is Insteon won't front you a refurb before you send in your unit so you are down until it is repaird. So, highest Wife Approval Factor wins...

@kclendenThank you so much for the detailed breakdown! I'll try to watch for the corrupted messages tonight and see what I can glean from the data. Unfortunately though it looks like this will end up being the nail in the coffin for my Insteon system unless the PLMs come in stock soon.

Tried that much and not much remarkable during the day. I think the most I had to repeat a command was 4-5x for the farthest devices. Not quite sure how to read the balance of the events and errors Closest device Thu 01/19/2023 14:18:08 : [INST-TX-I1 ] 02 62 57 65 64 0F 11 4D Thu 01/19/2023 14:18:08 : [INST-ACK ] 02 62 57.65.64 0F 11 4D 06 LTONRR (4D) Thu 01/19/2023 14:18:08 : [INST-SRX ] 02 50 57.65.64 40.53.13 2F 11 4D LTONRR (4D) Thu 01/19/2023 14:18:08 : [Std-Direct Ack] 57.65.64-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 01/19/2023 14:18:08 : [D2D EVENT ] Event [57 65 64 1] [ST] [77] uom=100 prec=0 Thu 01/19/2023 14:18:08 : [ 57 65 64 1] ST 77 (uom=100 prec=0) Thu 01/19/2023 14:18:15 : [INST-TX-I1 ] 02 62 57 65 64 0F 13 00 Thu 01/19/2023 14:18:15 : [INST-ACK ] 02 62 57.65.64 0F 13 00 06 LTOFFRR(00) Thu 01/19/2023 14:18:16 : [INST-SRX ] 02 50 57.65.64 40.53.13 2B 13 00 LTOFFRR(00) Thu 01/19/2023 14:18:16 : [Std-Direct Ack] 57.65.64-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/19/2023 14:18:16 : [D2D EVENT ] Event [57 65 64 1] [ST] [0] uom=100 prec=0 Thu 01/19/2023 14:18:16 : [ 57 65 64 1] ST 0 (uom=100 prec=0) Least reliable Far Device Thu 01/19/2023 14:28:09 : [INST-TX-I1 ] 02 62 54 A0 07 0F 13 00 Thu 01/19/2023 14:28:09 : [INST-ACK ] 02 62 54.A0.07 0F 00 FF 06 (FF) Thu 01/19/2023 14:28:10 : [INST-SRX ] 02 50 54.A0.07 40.53.13 2B 00 FF (FF) Thu 01/19/2023 14:28:10 : [Std-Direct Ack] 54.A0.07-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/19/2023 14:28:22 : [INST-TX-I1 ] 02 62 54 A0 07 0F 13 00 Thu 01/19/2023 14:28:35 : [INST-TX-I1 ] 02 62 54 A0 07 0F 13 00 Thu 01/19/2023 14:28:35 : [INST-ACK ] 02 62 54.A0.07 0F 13 00 06 LTOFFRR(00) Thu 01/19/2023 14:28:37 : [INST-SRX ] 02 50 54.A0.07 40.53.13 2B 13 00 LTOFFRR(00) Thu 01/19/2023 14:28:37 : [Std-Direct Ack] 54.A0.07-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/19/2023 14:28:37 : [D2D EVENT ] Event [54 A0 7 1] [ST] [0] uom=100 prec=0 Thu 01/19/2023 14:28:37 : [ 54 A0 7 1] ST 0 (uom=100 prec=0) Thu 01/19/2023 14:29:09 : [INST-TX-I1 ] 02 62 54 A0 07 0F 11 FF Thu 01/19/2023 14:29:24 : [INST-TX-I1 ] 02 62 54 A0 07 0F 11 FF Thu 01/19/2023 14:29:25 : [INST-ACK ] 02 62 54.A0.07 11 FF 00 02 62 54 A0 07 0F 11 FF 06 02 50 54 A0 07 40 (00) Thu 01/19/2023 14:29:29 : [D2D EVENT ] Event [54 A0 7 1] [ERR] [1] uom=0 prec=-1 Thu 01/19/2023 14:29:29 : [ 54 A0 7 1] ERR 1 Thu 01/19/2023 14:29:37 : [INST-TX-I1 ] 02 62 54 A0 07 0F 12 00 Thu 01/19/2023 14:29:50 : [INST-TX-I1 ] 02 62 54 A0 07 0F 12 00 Thu 01/19/2023 14:29:50 : [INST-ACK ] 02 62 54.A0.07 0F 12 00 06 LTON-F (00) Thu 01/19/2023 14:29:50 : [INST-SRX ] 02 50 54.A0.07 40.53.13 2B 12 00 LTON-F (00) Thu 01/19/2023 14:29:50 : [Std-Direct Ack] 54.A0.07-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/19/2023 14:29:50 : [D2D EVENT ] Event [54 A0 7 1] [ERR] [0] uom=0 prec=-1 Thu 01/19/2023 14:29:50 : [ 54 A0 7 1] ERR 0 Thu 01/19/2023 14:29:50 : [D2D EVENT ] Event [54 A0 7 1] [ST] [255] uom=100 prec=0 Thu 01/19/2023 14:29:50 : [ 54 A0 7 1] ST 255 (uom=100 prec=0) Thu 01/19/2023 14:29:57 : [INST-TX-I1 ] 02 62 54 A0 07 0F 14 00 Thu 01/19/2023 14:29:57 : [INST-ACK ] 02 62 54.A0.07 0F 14 00 06 LTOFF-F(00) Thu 01/19/2023 14:29:58 : [INST-SRX ] 02 50 54.A0.07 40.53.13 2B 14 00 LTOFF-F(00) Thu 01/19/2023 14:29:58 : [Std-Direct Ack] 54.A0.07-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/19/2023 14:29:58 : [D2D EVENT ] Event [54 A0 7 1] [ST] [0] uom=100 prec=0 Thu 01/19/2023 14:29:58 : [ 54 A0 7 1] ST 0 (uom=100 prec=0) I'll have to wait until tonight to try to get better data and likely tomorrow before I can power cycle everything.

Just a clarification-- I call it "unreliable" in that I need to initiate the control 3-5 times for it to have an 80% chance of success.

I'm having issues with my ISY994 not being able to consistently communicate with my Insteon devices. It started when I put up Christmas decorations, which included pulling an old insteon outdoor plug from storage, and adding 7-10 new SonoffS31 wifi switches (running Tasmota and not on the ISY994). Initially it was just a couple devices and only occassionally... including the outdoor plug, but over the course of 2 months it has gotten to the point where the system is unusable. Some things go on but not off, some occassionally go on or off, but not consistently, and every night all insteon devices shut off at once. The serial powerline modem is about 4 years old, and the devices range from maybe 8-10 years old to a few months. Troubleshooting steps: Unplugged all Christmas decorations and controls. No impact on operations. Re plugged in all the SonoffS31 controls. Moved ISY and powerline modem to different outlets and circuits in the house. No impact on operations. Deleted and re-added a device via the admin console. Potentially improved operation, but still not reliable. Unplugged the second device that showed errors in error log (see 1 below). No impact on operations. Additional debugging: Reviewed log and identified patterns; log shows initial error with outdoor plug, and consistent pattern to what I was experiencing with additional error rate over time. Checked ISY insteon device communications count. Count was consistent (91 devices) over 10 tries. Random thoughts: Time of day impact seems to be significant; it is better during the day and worse at night. House is pretty big, but no two insteon devices are further than 20' away from another one. A number of the devices listed are motion sensors that aren't really used (not reliable enough), but are still active. House has a main panel and two sub panels, along with Enphase solar microinverters connected at main panel. I do not believe any neighbors use Insteon. Electrically, closest neighbor is about 120 line feet away, next-closest is about 320 line-feet away. Transformer is shared across ~25 homes. Air conditioning doesn't run during any of these issues and there are only two small motors that run (water feature pump and hot water circulator) during the day. PLM is not plugged into a surge supressor, and there are no whole-house surge suppressors. I am now at a complete loss on what to try. The PLMs are out of stock which would be my next debugging strategy. Thanks for the help!!