slimypizza

I don’t think you need the separate Dog Lights program. You could just put that logic in the Dog Lights Away program. But that’s not the problem. I think it’s the IF statement. The Mon-Fri section has no calendar entry and may be halting the program from running. If you meant to trigger on Mon-Fri all the time then check the “Daily” box when programming that part of the schedule.

No help here just confirming I see the same issue on my EISY/HA system. At least the Blink app still works. I have the arm/disarm schedule setup there.

Thank you. Sounds like I should keep it installed though I dont use UD mobile. Looking forward to future updates to add functionality to eisy-ui.

Is there a way to uninstall eisy-ui?

I guess this is just another quirk of Alexa but I’ve had the voice command “It’s movie time” in our house for a few years now. It correctly turns off all lights in and around the family room for watching TV. Maybe it’s because I don’t have any other commands beginning with “It’s” so there is no potential conflict.

I have the IOlinc garage door kit and I key on the garage door sensor to determine the status of the door (ie open or closed - ON/OFF). It updates on its own, without needing to query. You should have two devices that show up in your AC: garage door relay and garage door sensor.

Thank you. I skipped right over the mention of beta in the official release post. Looking forward to further additions to eisy-ui.

I guess I misunderstood the purpose of eisy-ui. I thought I read it was to get rid of the java based AC. I finally got eisy-ui working after following the instructions of bmercier including sudo service eisyui start. However, I don’t see this as any replacement for the java UI. There’s nothing dealing with programming or variables, etc. Did I miss something or is that part still in the works?

Try adding your port number. Ex https://192.168.0.172:8443/desc

Yes, exactly. Once the EISY was powered down the switches were snappy and functional unlike their behavior with the EISY on.

Thank you all for your suggestions. I believe its all sorted out now. Strange as it was, things seem to be working again. I ended up verifying the switches worked if my EISY was powered down. All switches responded as expected. Then I reset and restored every switch since the malfunctions seemed to be random. That took a bit of time. Then I resaved every program on my EISY. Extensive testing now indicates the system is working without issue once again. Don’t know how this started but glad it’s over and appreciative of all the help. I’ve got a medium sized automation network and can now resume my project to expand.

There are too many switches affected to think they individually all failed at once. Also, I mentioned some programs are not performing as they should. I suspect the EISY at this point and not necessarily the PLM (since HA and Alexa appear to work). Perhaps there is a programming or config glitch I can’t get rid of unless I start from scratch or go to a previous backup. As I outlined above I will disconnect my EISY from the network and see how the switches behave. After that I may need to go to a previous backup but I only have backups from older SW versions. As I said earlier, this problem was first noticed after installing two new 2477S switches. My only backup prior to the new switch installation was the one created when I advanced to 5.9.1. Again – Can I use older backups from previous OS versions in an updated system? Thanks all.

No power event at all and I did pull the tab on the bottom of a few switches, wait, and push back in. Unfortunately, no change. Thanks. I'm very open to further suggestions. Thanks all. Can I use older backups from previous OS versions in an updated system?

Although it seems random, about half of my switches seem to be unresponsive (and the LED light does not go to the top) but if I activate them through HA, they may become responsive again for a while. I admit this is very strange. Sometimes when I turn the switch on via HA, the switch may not be able to turn off. Some programs with timers (eg, landscape lights, fans, porch lights) may or may not work and the devices have to be turned on/off with HA. These programs worked perfectly in the past and have not been altered. A couple of things I am going to try: I should have thought of this before: Turn off my EISY and see if the 2477S switches work. They should operate as a standard switch. I have my old ISY994i and PLM. I will substitute it into the network temporarily in place of my EISY and see how it performs. Question: I have older backups from previous OS versions from my old ISY994 (I’m running 5.9.1 now on the EISY). Can older backups from previous OS’s (eg, 5.8.x) be used on my current system? Thanks for all your help.

Guy – Sounded impossible to me as well but yes, pushing the physical switch does not work on many switches but Alexa and Home Assistant work fine. I also noticed today that a programmed timer (for a bathroom fan switch) did not work. It was supposed to turn off after a few minutes and worked fine in the past but today it kept going for over an hour until I saw it through HA and turned it off. Brian – I’ll try power cycling a few switches and see if that makes a difference. Note: I first began seeing this behavior after installing new 2477S switches in a bedroom. I named them Bedroom 2 Light and Bedroom 2 Fan. I already had switches in other rooms named Bedroom Light/Fan and Bedroom 1 Light/Fan. Would the similarities in names cause confusion in the EISY and problems that would extend to the whole network? I did remove the new switches, checked wiring for poor connections, and reinstalled. I also flipped the circuit breaker for Bedroom 2 which would have removed any noise or interference caused by those switches if that was a problem but neither troubleshooting effort changed the outcome. I still don’t see how physically pushing the switch paddle could result in no on/off status change.