Geddy

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)

@Athlon are you reserving IP addresses for the KASA devices? I wonder if the devices are getting different IP addresses when the router restarts. You wouldn't notice a difference with the Kasa app and probably not with Alexa if linked to the Kasa app (rather than to IoX). But wonder if that's causing issues with the node server. I'm not sure how the node server routs the devices into IoX, but probably via IP at the time they were discovered. I wonder if your restarting the node server causes them to rediscover the devices and correct the node/links being sent to IoX. Since it's just nodes then my assumption is that programs would still work as the device didn't change name or nodes, but the IP address could have changed and the node server or IoX didn't know how to communicate to the devices anymore. I don't use that node server so @Jimbo.Automates would know best of how it is discovering devices. I know I had an Asus router many years ago. They went through a phase where rebooting was necessary because it didn't have enough memory and would drop wifi (and sometimes hard wired connections) for no reason. It's as though they don't have a good way to clear out old memory or something and rebooting is the only way to get it to "reset". It was really annoying! I've seen some Netgear devices have "reboot router schedule" in their firmware now. That doesn't bode well for future longevity of their equipment (IMO). Hopefully you get the help needed to keep things working.

@Wes Westhaver If you log into your account at Universal Devices website you can manage modules for your devices there. It might allow you to buy through the site that way. Otherwise, try sales@universal-devices.com Or you could open a support ticket via: https://www.universal-devices.com/my-tickets Be sure to include your UUID for the ISY994 you want to add the module to. Honestly though, ISY Portal is a steal for what it offers you. $23 for the first 2 years, then $20 for 2 year renewals. You get the Network Module as well as UR Mobile (for 5.x+), Alexa, Google Voice, Remote Access (no need to open ports on home network), and other options. All for less than $1/month! https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal:_Integration_with_Amazon_Echo/Google_Home/IFTTT (FYI @Techman the support email might not reach anybody (I haven't tried it lately), but it's not the suggested rout for support tickets now. Something went "wonky" sometime in the last few months.)

@deps looks like something/someone is trying to log into the IoX and failing. Error 10103 is authentication error. do you have an external device or app trying to log in that might be using an old password? See the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages 10108 isn’t listed, but given the others before it are authentication issues it could be related. If you can’t figure out what’s trying to log in you might want to open a support ticket to see if they can help somehow.

No, my eisy is showing online on the portal site and I’m able to access it from UD Mobile while away from the house. If you are local to the device can you access it? Have you approved the Portal from IoX? (Should be in Configuration tab, Portals)

@Wes Westhaver I’m not sure if you can still add the Network Module. I know it’s now included if you get the ISY Portal license. So if you already have an active portal license you should have the same network module function. But here is the info you’re asking about: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking (some info might be outdated or written for old firmware versions, but most functionality should still be there.)

Make sure you search for "pin out" information. This is one that I book marked a while back from @Brian H to help describe what connects where: There are a lot of posts. Perhaps the easiest way to find them/others is using Google Site Search since some might be archived and not showing up in the forums search function.

I have contacted Somfy several times about the ZRTSI product to see if it would work better than their MyLink and would give me a method to incorporate into the ISY. At the time I didn't have Z-Wave running on the ISY994, but would have it the shades could have been incorporated. I have 4 shades using Somfy RTS motors with a MyLink so I could automate the shades, but their process is rough. Somfy directed me to use the Tahoma product to make it more "automation friendly". It's ZIgbee and Wifi based. I got it and couldn't ever get it to connect to a network. I finally got it, but at the time didn't have any Zigbee option to make things operate any different so I have remained with the MyLink. I've never been happy with any development information from Somfy. They seem to be scattered that nobody knows what direction they are going. Now looks like even Tahoma is EOL. I don't know for certain, but last time I had a support case they said there was no current support available for Tahoma. Would be great if they had a 700 series Z-Wave controller on the horizon, but figure the 300 series might be all they produce and support until it's really dead. About the time I was trying out HomeAssistant the Somfy MyLink integration was removed. I think HA still has a Tahoma integration, but I didn't keep HA to try that route out. I was hopeful that with the ZMatter board that perhaps it would help with the Zigbee side of the Tahoma to allow me to link the RTS motors to the eisy. @BigMojo interested in if you can get the ZRTSI to work with eisy+ZMatter. Take your time testing though...I'd have to get the ZRTSI device if it were to work, and just not sure I'd be willing to spend the money on it at this point...what we have works. At the moment.

@richtimpa 3.1.18 is only for Polisy. If you're on eisy you should be on 3.1.22 (as of current release posts). If you're on eisy make sure you can log into IoX Admin Console. Then use that same user/pass to log into PG3x on eisy. If you're still having issues please power cycle the eisy by removing the power plug, waiting ~20 seconds, plug it back in, allow ~5 minutes for full boot. Then log into IoX before attempting to log into PG3x. More than likely if you ran an update and didn't allow enough time before trying to access the system it could create a conflict and UDX did not start correctly. From other posts it seems to correct itself after a power cycle and allowing it to completely boot up before attempting to log in. PS: Nice auto correct on "eisy" to "Etsy"!

I agree. Glad they were able to try to help. Hopefully when you get home it will be as simple as swapping out the cable. I tend to make a habit out of using new cables when I connect new devices. So perhaps that will be a simple fix for you. Thanks for the update

Doubtful anybody here would know about any update for Roomie Remote testing. You should contact UDI directly from their website https://www.universal-devices.com/contact-us/. We're just a bunch of users helping users support their systems. You appear to have misunderstood the previous reply (mostly based on your post on the other forum). Nope. You need to be on 5.3.4 (if you don't have Z-Wave or have Z-Wave 500 series board). There's no migration path from Z-Wave 300 Series board. And not sure if 5.0.16C will migrate. Why did you stop upgrading at 5.0.10? There's been a lot of releases since then. Seems pointless to stay on a really old build when lots of improvements were introduced in later builds.