Geddy

WOW! People use some close/small zones. I found about 1000-1500 meters to be ideal for my situation. But I just used geofence for lights. I guess some use it to open garages and unlock doors (too unsecure for my liking!). It also doesn't seem to be a battery drain by having larger areas (<1% in last 24 hours in background use).

@JP the email method might not get you in the ticket system. If you get an automatic reply that a ticket has been generated then okay, but recently the email was removed as a method to generate a ticket due to site/system issues. Surprised the web is giving you issues. Do you run firewall or other web blockers that might be blocking something? Maybe try a incognito or private browser session.

@ctviggen1 make sure you’ve added the eisy to your portal account and setup the trial portal subscription for the eisy. Wiki instructions to migrate the portal: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY If you have the eisy on the portal it needs to be approved in admin console on configuration tab then portals tab.

You’re at 5.5.7 so no need to upgrade packages again (currently). You can follow the “current release” area to get notifications when new releases are posted. That’s when you would want/need to update. I usually suggest people don’t randomly hit update. Many have learned it has crashed their systems randomly hitting the upgrade packages process. It’s hard do hold off thinking you’ll get some random update, but best to wait until official releases are posted if you’re at the current level already. All your issues seem to be known issues and hopefully corrected in next release.

Interesting. Can’t help on that then. My eisy is not in an area I can connect a monitor to so just use admin console.

I imagine these are just the names of the devices. If you’re in admin console what is the first item listed in the tree for the eisy? Is it “ISY”? IoX Finder window will usually reference the “name” of the device you are connecting to. Since you restored the “ISY” backup into the eisy it is now named “ISY”. You can change the folder name to IoX and clear Java cache then reload start.jnlp and it should reference IoX again. I’ve named mine something else and it shows up in my Finder with that “name”. What is “start.win”? This is probably where you confused Michel. Not sure what app/service/device you’re talking about. Maybe a screenshot or more details. Sounds like you got everything else figured out and migrated properly. Congrats!

I think this is a known issue and being worked on and hopefully corrected in the next release. I've seen @DennisC comment about this being known. I believe the other is also part of the same issue. I had the issue once and it hasn't returned (thankfully). I'm not sure if others that got this error still get it often. (@DennisC do you still get the alert?) You can check the subscriptions by using this URL: http://eisy.ip.address.here:8080/rest/subscriptions (replace the crossed out text with your actual eisy IP). It will ask for your user/pass this should be for local login to admin console. The result is an XML file showing the subscriptions to the isy process. <Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="36" sock="7" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="no" isPortal="yes" sid="0" sock="28" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="39" sock="9" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> </Subscriptions> I would suggest you shutdown the eisy (6 button presses...wait for red light), pull the power, wait ~20 seconds, power it back up, wait ~60-90 seconds, and log into Admin Console.

@waffles rather than waiting on the heartbeats why not try with water/wet test at/near the location of the sensor? Once tested and alert received you can dry off the sensors and reset them. You said Tuesday you went back to the original programs. Have those been sending daily notifications about the heartbeat? From the post you linked to: To me the programs from the thread you said you were copying should be sending you alerts twice a day. Are there issues with the sensors in those messages? Otherwise, you're doing your own thing and seems like nobody knows what you're doing to try to help further. I believe there has also been a few posts elsewhere about how the sensors are cleared. There were apparently a few different sensor versions and firmware for each that require a different method for clearing or resetting.

@jaydrosy did you submit a ticket? What was the outcome? If they reply with "known bug" then post here to let others know. If there was something done to fix it also post here to help others attempt to fix their system. @JMcKain as suggested above, please submit a ticket to UDI support (link above in first reply). That's going to be the best way to get help and to help UDI figure out if this is a bug or expected and allow them to properly handle "fixing" it if it's indeed broke.

Seems like a lot of work to get heartbeat notifications. My question now is... Why are you wanting to monitor/track heartbeats? The whole point of the heartbeat missed notification is if your leak sensor is offline. If you look at the original theory of the programs you were copying the whole thing is to use notifications to trigger a reaction from you. It seems that you're more worried that the ISY isn't recording the heartbeat than what the heartbeat even means to the system. Now you're trying to learn how to write information to a webserver when a simple notification would do the job. My thought is now you've got so many notifications you won't really pay attention to what they're saying and you'll miss the big alert if you have an actual water issue. You've got to step back and look at the big picture. 1) What are you trying to achieve? Track heartbeat? Known when water/leak happens? 2) Do you really care when the heartbeat happens or just that the sensor is communicating with ISY? Since you said you went to the basic programs as you linked in an earlier post on Tuesday have your notifications been accurate? If so, why dig deeper for something? If you don't think they're accurate then you need to change the system so that the sensors are communicating regularly, or else replace the sensors.

@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.