Geddy

@Javi @sjenkins I had the same issue on initial install and setup. It was happening if I changed the distance. It didn't seem to happen after first setup. I ended up with 3 areas. I deleted all three and setup again and did not have the same issue, but I also didn't change the distance more than once as I knew the size I was going for. What seemed odd was that when I created the geofence (even though I was inside of it) the status appeared to show me outside the area. I wasn't going out again after setting it up, but did today and it now shows correct status for inside and outside zone. I haven't attempted any further control or programs yet. Will test later today or tomorrow. Excited that this won't need Occupancy. I currently use Mobilinc with ISY Portal and eisy and haven't had any issues with geofence. I have been looking forward to having this function available in UD Mobile. Nice job!

@carealtor only iOS so far…. Wiki Instructions: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Geofencing

There's no need to edit the ISY in the PG3x setup. The eisy uses the IoX user/pass in all locations. So whatever you set to be the admin password for the Admin Console to IoX will be how you log into the eisy dashboard (as you found out). The ISY service running on eisy should load automatically. There's no need to add user/pass on the screenshot you provided. As @DennisC covers you need to sign up for Portal for the eisy. Either setup the trial (probably done during initial setup if you used UD Mobile). If you are migrating from ISY994 or Polisy the portal migration is very simple and takes almost no time to complete. A portal account is needed to be able to buy/install Node Servers to the eisy.

Best way to contact UDI is through the support ticket website - https://www.universal-devices.com/my-tickets They're really good about handling tickets so if you opened a ticket this way and it took "a week" to get a reply that's not normal. You should be able to log in and review the ticket status. It might be "waiting from customer update" (or other wording). That's the best method to work directly with UDI for support. The Forums are really more user-to-user help. And since it doesn't seem like many are using the process you are using there might not be much help here. Does Homebridge have any support you could get from their side? Since the github you linked to hasn't had any updates in several years and references ISY Firmware 5.0.16+ it's very possible that it's not working with the latest eisy IoX firmware. While I think doubtful because most underlying function appears to be the same it's still possible. You never replied to @MrBill's comment above. What is the result when you try his URL? Home Assistant connects to ISY completely different. It's also currently supported and actively updated. You can learn more about it by reading the Home Assistant area of these forums or from the HA side.

What is your desired outcome? You asked about programs now you're talking about switches controlling other switches. @gzahar suggested scenes. Do you have ONE program, or a program for each switch? Perhaps paste your program(s) to review. On the program(s) right click select "Copy to Clipboard" (last option on menu) then paste as text. If you handle all the lights as a scene you could simplify your program to be: Test Program If From Sunset - 15 minutes To 11:00:00PM (same day) Then Set 'OutsideScene' On Else Set 'OutsideScene' Off This would simplify everything. Then, if your scene does have traffic issues you can attempt the repeat that you were looking for. Note that this handles both the ON and OFF given your first post (turning lights on 15 minutes before sunset, and off at 11pm). You don't need 1 program to turn them on and 1 program to turn them off (or multiple programs for each switch).

Rather than band-aid the issue find out why the lights aren't turning off. Sounds like a noise issue. Sure, adding waits and running the command again is a way to make it work, but what happens when you have 4 or 5 repeated lines and it STILL doesn't turn off? Just add more lines? No, fix the problem! It's possible that the switch is going bad. It's possible line noise is causing a missed command. Even if you say, "but I haven't added anything to my system", there are plenty of reports that something as simple as a phone charger going (or has gone) bad adds line noise to your system. Even an appliance has been known to suddenly add noise blocking Insteon commands. FIX THE PROBLEM! Adding waits and repeating the command just masks the issue. By not finding out what's causing it could lead to other issues. Good luck.

Not sure. I haven't tried any extension. Just know some have. I wouldn't go hundreds of feet, but think most common extensions of 5-20 feet should be more than plenty to get you started. I think with the reported better signal strength of the ZMatter antenna it might not even be needed, but was mentioned as an option should you get it and continue to have some intermittent problems. Uncertain. I don't use either, and don't use much Z-wave at the moment so not sure if there's any way to have something report errors. I'm guessing there might be a heartbeat or connection node, but only an assumption. Better as a new question in the ZMatter area to see if there are programs or other ways to monitor the connection/status. Also note...there has been some troubles getting locks to work with ZMatter. I don't know the current status of that with the last update and don't know what brand locks you have. So read some of the posts in the ZMatter area about the locks for more information. And this is exactly the reason we don't have "smart locks". They're too stupid when they "don't work". I trust in my routine to lock all the doors and to double/triple check them throughout the evening before heading to bed. Security is not something I rely on automation for. It's too valuable to me and physically locking of doors and inspecting that the garage is closed are just simple measures that I don't intend to "trust" a computer to do for me. At least not while I'm physically able to do such tasks. Even if we did have "smart locks" I wouldn't feel comfortable not at least checking them on one last pass at the end of the night.

@to_lighter glad you got this sorted out this time. Make sure you make a current backup! I like to keep my backups on a cloud drive (like OneDrive, Dropbox, Google Drive). It's possible you could have SD Card issues. How old is your device? What Firmware are you using? (Did you upgrade firmware recently?) The wiki has instructions on how to replace the SD card if you should have any new issues soon. https://wiki.universal-devices.com/index.php?title=Main_Page

@ctviggen1 remember with the eisy + ZMatter dongle you could use an USB extension cable to relocate the ZMatter board to a different area. Here is a post with some 3-D printed holder options/discussions for the ZMatter dongle. A device like that would allow you to relocate the ZMatter dongle to an area away from the eisy further extending your signal from the (center of the) basement rather than where you currently have your ISY994. Just a thought to consider other options.

Perhaps even more information for the specific fixture you're using. I have several fixtures with integrated LED that do work fine with Insteon dimmers. I don't know the brand as they were installed by my electrician and I didn't think to get a detailed list of product installed at the time. I found an interesting read from searching for ELV/Triac info. There's even a couple of old threads on these forums about the question:

It's unlikely, but possible that the password for IoX is not correct in PG3 and needs to be updated. The Polisy still needs to have the user/pass set in the web interface. I would check/confirm that is correct in IoX Configuration -> Edit current IoX Also, check the IP address being used. If you're using ISY on Polisy then I think you can just use "localhost" or 127.0.0.1. You shouldn't be using the IP for the Polisy. (Review the wiki Polisy User Guide)

I think it might depend on the brand of LED you get. Every light in my house is now LED and all my Insteon on/off and dimmers work just fine with the LEDs I have. I use the Philips dimmable LED. I have nearly full range for dimming. I don't want/need/care about anything < 10-15% brightness so I'm not a snob like some that cry when they can't get 3.1415926% brightness. I know many others here use LED on Insteon dimmers without issues. It does depend on the quality of bulb and the application. But mine ranges from can lights, recessed lights, to ceiling fans with 3 and 4 bulbs in the light kit. I use the standard paddle dimmers and 6 button keypads as dimmers (for the ceiling fan kits) and don't have any problems. *knock on wood*

But I still don't get the need to have the "AND" in the line. I didn't read the later replies in the thread you originally referenced, but thought if the original programs worked as posted then modification shouldn't be needed. Unless there's a specific reason. To me..."missing heartbeat" isn't a reason to modify the program, but a reason to find the cause of missed heartbeat. Folder conditions are tricky, but they're an easy method to make all programs in that folder not run. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Folder_Conditions You already have them in a folder for "Leak Sensor - 49 hrs". In that folder make a condition that will NEVER be true. (i.e. if a variable = 1 then set the variable to 9999). It will act as though the programs in that folder do not exist and will not fire. Now...there is an issue (and I haven't personally proven it), but there might be a way that if a program calls on the "THEN" of a program in a false folder it might trigger, but I cannot confirm.

@bwade913 if you go to "Purchases" you should have the option to (Re)Install from that page. It should handle the upgrade. Possible that one or two older node servers might not work properly based on some other comments around the forums. I think @bpwwer would be better able to answer, but thinking that just the "reinstall" on the "Purchases" page should get you what you need without having to uninstall and reinstall. However, if you do uninstall a node server I would suggest having admin console closed during the process and not running admin console again until you have the node server reinstalled and configured so it doesn't mess up the nodes and programs in admin console. Again, this is based on how things worked in the past...not sure if as critical or applicable now, but just a method to try to avoid additional work by not having the admin console open when changing/adding/updating node servers.

It's possible your DB9 jack wasn't wired correctly. Did you follow the pinout picture from the UD site or other comments in the forums about how to handle the wiring of the Serial signals? Pinout description: https://forum.universal-devices.com/topic/34283-polisy-plm-will-it-work-with-serial-usb-or-both-types/?do=findComment&comment=324912 The only way to connect the PLM to the Polisy is through DB9 (serial) or USB. There's no RJ45 jack on the Polisy to accept the serial cable that most used to connect the Serial PLM to the ISY994. All the RJ45 ports on the Polisy are Network ports and could cause damage to the PLM if tested. So, be extra careful! Hopefully you haven't damaged a working PLM! There are repair services available (by the new Insteon and by a forum user on ebay). There was a RJ45 to DB9 cable in the original packaging for serial PLM. Though most might have thrown it away when it wasn't needed to connect to the ISY994. If you still have the original box it's tucked away in the inner packaging. Yes, they will need a PLM with the eisy to communicate with Insteon. If you are able to test the PLM via computer there are methods to do that. I've never attempted them, but have seen @Brian H mention them. Try to get the PLM issue sorted out first. Then can address the time zone issue. That was a known bug in early IoX versions, but you said you are on 5.5.7 so shouldn't have that issue. One thing at a time though. Get a usable system. Then can worry about the time.

@CandC, @FloridaGary and @glarsen see if fixed this morning. Appears that a server might have lost a connection. It was fixed this morning from another post. Wondered if it impacted what you were seeing for favorites not showing status.

@waffles Forgive me for chiming in with this, but just for clarification for my own sake and to review what you're doing... Why do all your programs that appear to update the heartbeat have an "AND" with a status of "Wet" of either on or off? That seems counterproductive. It's as though you combined two programs from the link you provided. They should be mutually exclusive based on reading the early parts of the thread you posted to. I don't run any Insteon leak sensors (I didn't find them reliable enough at the time I tested them in my system), but looking at your programs compared to the link you originally posted that you attempted to coy from to me you messed yourself up by having an "AND" in the heartbeat 25 hour program. I think that's why you were "missing" heartbeats. Because you were not just basing the program on that instant. You've got so many programs and so many edits or variations of them that it's possible something is messing up any changes you make at this point. My suggestion would be to put all existing programs in a folder and make the folder conditions false so they don't run. Start over with the simple programs from the link you provided and try it for a day (or two) and see if you get a correct heartbeat and/or progression of the new programs. There's something about your initial thought that you are "missing heartbeats" you just randomly changed the program to 49 hours. Heartbeats were hardcoded by Insteon to happen about every 24 hours. If you have a missed heartbeat it's because of other reasons and should be reviewed rather than just kicking the program out 49 hours. (IMO)

@DennisC Worked logging into eisy. Can you log into portal site and see if your error or event logs will load?

Very strange. I have no such issues. AWS isn't showing any issues in North America (was wondering if it was perhaps a regional issue).

@DennisC or @jwagner010 iOS or Android? Working fine for me on iOS v1.0.21. At least able to get connection and control devices while remote. Other Android users are reporting issues with Favorites not loading. Portal also available/working for me and reports eisy IoX online since last Friday.

Yeah, it's a note to not leave logs in "debug" mode. Why put them all in that stage and leave them that way? That's usually only meant to debug a specific error. Leaving them in "info" or "error" mode, whichever is default, should be fine for day-to-day operations. The few that I run are in "info" mode as I don't worry about errors until I start having them. Then figure error or debug is what I would use to try to learn what's happening. Glad Michel got you sorted out.

From the wiki: [NOTE: The ISY994i takes a MicroSD card. The max size is 32GB. Please look for a card with the newer A1 rating (A2 also works, but will fallback to A1 because the ISY994 does not provide hardware support required for A2). All other process steps below remain the same.] The wiki also outlines the process for proper replacement and reinstalling firmware.

Perhaps the easiest way would be to enter a support ticket to get help getting to where the logs are and delete bloated logs and hopefully get you running again. https://www.universal-devices.com/my-tickets Additionally they would confirm that it was your log issue that was causing problems.

I don't remember how it works (as I don't use HA), but remember seeing other posts about the "ignore me" function being a way to keep some ISY devices out of the HA side. I think others that use HA currently would be better able to tell you how to incorporate that. But that way it isn't imported into HA. I think the default was {ignore me}, but suggestions were made to change it to a simple symbol or shorter text. Perhaps that way you wouldn't have to delete them from the ISY/Node Server, but they also don't import into HA if you ever ran an update again that somehow imports items. More info: https://www.home-assistant.io/integrations/isy994/

@Athlon guess a swing and a miss then. Oh well. Oh, and just went to look at the additional info for the Kasa node server and saw this: (Source: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md)