andrew77

Problem solved. Back up and running. I said it to Michel in the ticket and I'll say it here. Great product with great after sales service.

Thank you as always (Geddy and everyone else) I'll open a ticket.

Under Tools/Diagnostics/PLM Info/ Status it says not connected

Is my eisy corrupt? or am I having issues communicating to the PLM?

Mac Sonoma 14.5 I've cleared my java cache as above I've done this When I click it it says 5.8.4 so I'm assuming that's correct When I click on a device in the GUI I get these warnings I just upgraded to the EISY in March and bought a 2413U then.

I run a Mac. When I clicked on the update I see nothing like that. I knew the update was done because it popped up on my phone from the app, not from my computer. how do I clear the cache on the Mac?

My mistake. I got the notification it was ready to reboot (I was impatient clearly) But now I have this I'm not sure where to download that

I ran the update. I still see 5.8.0 I'm not sure where the three check boxes are or how to clear the cache

I'm on 5.8.0 Should I try to Restore PLM? I think I've done it in the past and it wasn't too laborious.

I was getting this and then I rebooted the PLM and ISY and now I get this The PLM Status says Not Connected (I apologize for the size of the screen grabs. They weren't that big on my computer)

Maybe that could be it. My issues started about 5:00 pm yesterday so maybe not. Is there a way I can test using the EISY GUI to see if it’s my gear or their gear?

This happened before and I unplugged the eisy and the and PLM (PLM first then wait, then plug in the eisy) Is AWS down? Or is it something wrong with my eisy, etc?

Thank you Paul. I actually did that and found it worked because I read lilyoyo1's post here I'm giving the credit to Paul but really thanking everybody for their help. I have to say again the ISY and now the EISY is the best, second only to this forum. If it weren't for the forum I'd be divorced and living int he dark talking to Alexa and hearing "I'm sorry but the hub that device is attached to is not responding" over and over until I shuffled off this mortal coil.

Doing more reading, should I try to restore the PLM like this fellow? Or will it have a poor outcome and I'll be sad after doing it?

Some forward motion. The PLM is showing Not Connected. I'm hoping its not a dead PLM as I just bought this 2 months ago when I upgraded to the EISY. What are the next steps?

I tried controlling a device from my Computer GUI and got this. I checked my license and I'm subscribed to the portal until 2025 so I'm not sure what this means The programs say they ran yesterday but I can say they didn't do anything. An outside lights scene didn't turn on. I looked at the troubleshooting page but nothing there seems to apply to me. I've not changed anything as far as plugging the EISY into a different location or a powerbar, etc. Should I restore the ISY or something like that?

Just checking in to see what next steps I should try.

Should I “Restore ISY”?

I have to add that when I tell Alexa to ‘turn on Apple TV upstairs’ etc she does it perfectly. If I ask her to dim the lights she either says ‘ok’ and nothing changes or she says ‘the hub that device…’ I hope that helps trigger a thought that leads to a solution.

I’m not sure what could be happening but none of my programs, timers, or voice commands are working. The mobile gui gives me this. is there some AWS failure? i believe my portal subscription is still good. Maybe not, I’m not sure how to tell will the mobile. any thoughts would be great. thank you.

Does the Eisy recognize the evo?

Thank you very much for this. My complaint is other automatic openers are wifi and don't work all the time because the garage is about 200-250 ft away from the house. This seems like a plug in direct to the power so it should be as reliable as I've always found other insteon devices, correct?

I see the IOLinc is still sold but the garage door 'wires and magnet' don't seem to come with it. Could you describe how you hooked it up to your garage opener?

Restore Device seems to have worked. I should have know to do that first. Thank you everyone that helped here

This is what the event viewer wrote Tue 03/19/2024 01:48:42 PM : [INST-TX-I1 ] 02 62 51 03 FF 0F 11 FF Tue 03/19/2024 01:48:42 PM : [INST-ACK ] 02 62 51.03.FF 0F 11 FF 06 LTONRR (FF) Tue 03/19/2024 01:48:42 PM : [INST-SRX ] 02 50 51.03.FF 70.90.75 2B 11 FF LTONRR (FF) Tue 03/19/2024 01:48:42 PM : [Std-Direct Ack] 51.03.FF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/19/2024 01:48:42 PM : [D2D EVENT ] Event [51 3 FF 1] [ST] [255] uom=100 prec=0 Tue 03/19/2024 01:48:42 PM : [51 3 FF 1 ] ST 255 (uom=100 prec=0) Tue 03/19/2024 01:48:42 PM : [D2D-CMP 0022] STS [51 3 FF 1] ST Converted values Event=100 Condition=100 prec=0 Tue 03/19/2024 01:48:42 PM : [D2D-CMP 0022] STS [51 3 FF 1] ST op=1 Event(val=255 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> true Tue 03/19/2024 01:48:52 PM : [INST-TX-I1 ] 02 62 51 03 FF 0F 13 00 Tue 03/19/2024 01:48:52 PM : [INST-ACK ] 02 62 51.03.FF 0F 13 00 06 LTOFFRR(00) Tue 03/19/2024 01:48:52 PM : [INST-SRX ] 02 50 51.03.FF 70.90.75 2B 13 00 LTOFFRR(00) Tue 03/19/2024 01:48:52 PM : [Std-Direct Ack] 51.03.FF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 03/19/2024 01:48:52 PM : [D2D EVENT ] Event [51 3 FF 1] [ST] [0] uom=100 prec=0 Tue 03/19/2024 01:48:52 PM : [51 3 FF 1 ] ST 0 (uom=100 prec=0) Tue 03/19/2024 01:48:52 PM : [D2D-CMP 0022] STS [51 3 FF 1] ST Converted values Event=0 Condition=100 prec=0 Tue 03/19/2024 01:48:52 PM : [D2D-CMP 0022] STS [51 3 FF 1] ST op=1 Event(val=0 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> false Tue 03/19/2024 01:48:55 PM : [ Time] 13:49:02 9(0) I haven't restored yet