gdntx

Yep - glad things are back up. Working in IT I get what it takes to have a major outage anytime, let alone a holiday. But, tongue in cheek, let's just say - AUTOEXTEND.

I saw a RATDGO forum over at Home Assistant. You might find more help there.

What "Span" size did you use to get 3 wide? I can't seem to get 3 icons to one row.

Does BSD have a cron tab? Set up a weekly reboot from the OS.

I believe the way the Portal and all components work you don't ever truly have to worry about this - you can use DHCP. The portal knows your Eisy by Mac address and how to find your home network. There is magic that allows the portal to connect. I'll call it magic, because I don't fully know what protocols are used and how it allows the traffic into your home network. Maybe someone will clarify that for me too. What I can note and help with is how to get a static IP address for the Eisy if you prefer the static. I used to do that by hardcoding the IP in my ISY and turning off DHCP, but I've learned is that a "Reservation" in the router seems to be preferred these days. So I've switched to the reservation when I upgraded to Eisy. If you pull up the console for the router, look for Advanced Config, then LAN you'll find the IP reservation section. You'll see all connected devices and will show the Mac address of each including your Eisy. Find the Eisy, select it and add the reservation - choose the static IP address you want and assign it, save it. Then reboot your Eisy. It will always get that same IP address now when rebooted.

Ford Pass was down this afternoon too for a while - did AWS or which ever provider have a bigger outage?

Glad that worked - I just learned that this week myself in another thread. I wish they would add something to the console to point this out - it is not intuitive at all - @Michel Kohanim

I'm not sure I followed all of the problem, but I had problems setting the On Level for a switch and just found it has changed in the SW. If you are trying to set the local On Level for a switch, set the number to what you want in the console and then click the "On Level" button, not the "Write" button. You may already be trying that, but it isn't intuitive. I don't know when that changed, but maybe help for changing the settings of the switch.

I've got a Honeywell TH9320WF5003. I don't know if this is the same as the T9 you have and speak of. The Wifi works well (the app seems to lose connectivity every other time I open it - I just force close the iOS app and restart and connection is good) and I also control through Alexa which is reliable. 98% of what I need is just handled with the internal schedule. I don't get deep into the protocols, but would either the Eisy or HA have an interface to the Alexa skill that you could include in your programming?

Thank you @Techman and @Geddy for the follow up and solution. I guess I could have looked through some documentation. My system has been in for 10 to 12 years and I don't mess with it much. I just recall the button used to say "OK" or something and whatever change you made on the screen were written to the switch. I'm sure this is likely updated in the documentation. I'll note staring at that screen I don't think for a hundred years I would have thought to click the "On Level".

Interesting follow up - I forgot about the new UD Mobile app because I typically use Mobilinc from the phone. I opened the app, selected the switch, changed the On Level to 13%. It wrote the switch and that is now what I get when using the switch locally. So maybe a bug from the desktop ISY GUI?

I had this problem previously with a 994, but for current HW I just migrated to a new Eisy and upgraded the SW to 5.8.0. I used a new PLM. All of the migration has gone well: restore from the backup, Restoring the PLM, etc. Portal license migration, Spokens for Alexa. I had 3 or 4 switches that didn't update and I've done a restore device for those switches. I don't show any communication errors. I now have a switch that I want to update the "On" level for. Simple update to 13% from the 100% currently set. The console shows activity on the network and I've captured the detailed log, but nothing I do after clicking "Write Changes" will truly update the switch. I can remotely and locally control the switch, it all seems good, except the update for the "On" value Any insight would be appreciated. Screen shot of the switch and a log of the write is attached. ISY-Events-Log.v5.8.0__Wed 2024.01.10 01.28.46 PM.txt

Thanks for posting - I also ran into the same thing. I had just asked her to forget devices and she acted like she did, but did not. A quick Google took me to the above web page and that worked just fine.

I just replaced two switches last week, once you get them worked out in ISY you'll also have to go into the Portal and add them and remove the old ones, then have the Echo discover devices.

I was out on my ISY portal updating a couple of switches I replaced in my Echo. There is a button I don't recall "Live Update" it says that when it is enabled and using the V3 skill the device status will be sent in real-time to your echo app. I can't find any reference to a skill with that name - not linked to ISY anyway. Thanks.