Geddy

@Old Surfer Dude Glad it works how you've changed it. You might consider updating ISY994 to 5.3.4. There were several fixes to z-wave control from 5.3 - 5.3.4 (specifically in 5.3.2 "Z-Wave button press control & status updates for switches"). While I can't say it would completely fix your issue (since I don't use z-wave). It's certainly something to consider that minor z-wave tweaks were done between the 3.0 release and the current release version (5.3.4).

@smileyw No...inside the UD Mobile app they're calling things widgets... More about them in the wiki here - https://wiki.universal-devices.com/index.php?title=UD_Mobile#Widgets

@jtedesco Great! Glad it worked. Hopefully it's adding them back in. I'm sure it probably isn't putting them back in the order they were so you might need to fix a lot of your programs. Good luck!

@jtedesco You need to confirm what model z-wave board you have. If it has a blue LED on the back of the ISY then you do have a 300 series. If not then you have 500 series. If you have a blue light then you should have only updated to 5.0.16c. It's probably possible to downgrade to that version by installing it and hoping things will come back to normal. I don't have z-wave so haven't attempted such a move.

That "bad" value is known a UI issue. It's fine to ignore and not causing any issues. Mine currently displays: Can you confirm your UI/FW match? Help -> About If you've rebooted/restarted lately have you also power cycled the PLM? Make sure you plug the PLM in first and allow some time before you booth the Polisy.

What you you mean you "STILL" cannot login to PG3? Have you posted somewhere that you weren't able to? You should have probably fixed that before going through an update process that required you to reboot PG3. Sadly, the "reset credentials" part of the multi function button on the Polisy does NOT reset PG3 credentials. (only SSH, IoP, and PG2) You should start a support ticket to see how to reset the PG3 password. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@bpwwer Yeah, they're the same. I wasn't worried about it. Just surprised it didn't update. Perhaps your right...cache ...might have just needed to refresh the page. Worked the second time though.

@bpwwer Great work! Just ran the update. Went without issues (for the most part). The only issue I can mention is that as soon as I hit the "Restart Polyglot 3" option it took me immediately to the ISY Portal login. I let it sit there a while...what felt like long enough for PG3 to reboot (3-5 minutes). Logged into the portal, like it normally requires, then logged into PG3. It still said it needed to be rebooted. Went through the process again, but this time backed out of the ISY Portal login and was in the PG3 window with the yellow window. Waited for the yellow message box to go away and was then able to proceed with the log-in process (ISY Portal and PG3), PG3 is up and running fine. Nice work and thanks for the simple update process.

@geobark If the mission critical is only one item (or just a few) then using network resources and UD Mobile notifications would be your best bet. You can setup notifications to push to UD Mobile for your devices. Setup is fairly easy and doesn't require additional apps or accounts. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Notifications_Tab

Look at the group section in the wiki - https://wiki.universal-devices.com/index.php?title=UD_Mobile#Group_Setup If you still have issues/questions maybe @Javi can help with something specific. I haven't attempted this, but seems like what you're looking for.

9 months later! I bet some of them were welcoming little Valentine's day bundles of joy around the time the text came in!

Come on @MrBill nobody pays any attention to this "warning" when they're dead set on getting perfectly formatted text messages. I mean, it's all in the formatting. Who cares when the messages arrive? It's not like there aren't any other alternatives. And it's been documented in several (dozen?) other posts here that text messages are notorious for arriving late. Sure, they might start out instantly, but when it's something truly mission critical it will be that ONE message that comes in hours (or days) later and it's too late to do anything about it. @geobark glad you found a "solution" to your issue. But know it's only the solution to the question you asked. The REAL "solution" would be to avoid using email to text gateway and consider other alternatives. You can learn more about Pushover on their site - https://pushover.net/. You can then learn more about how to set it up with the ISY by looking at other posts on the forum or by reading the ISY Cookbook found in the Wiki. There are also some basic steps (might be old) for Pushover found on the wiki site. Ultimately, the suggestion above by @MrBill to run Spark is a solid suggestion. And @asbril had the solid suggestion for Pushover. Both are probably more reliable than email to SMS/MMS gateway alerts. At least over time. 👍

I think you've hit the nail on the head with this statement. But as @lilyoyo1 points out it's probably best to figure your setup in the Hue app first then add everything to the Node Server to feed to ISY/IoP. Another comment (warning) I have is to make sure you put an IP reservation in your router for the Hue Hub. There's a note about it in the readme of the Node Server, but often overlooked. "Poly assumes that Bridge IP address never change, so it is recommended that you create an IP address reservation for the Hue Bridge on your router." I think the biggest thing is it depends what you're trying to achieve with the ISY involved with controlling the Hue lights. Need to plan that out first then it seems fairly simple on/off and levels are simple. Colors get complicated. I like setting up scenes in the hue app then being able to trigger them from the ISY. This is more or less find out on your own. As @lilyoyo1 points out the current node server is based on the old API so things are limited to a degree. The Hue app allows only so much setup and its own automation that I've found that to work well enough for me not to have it integrated with ISY at all. But that's just how I use Hue in the places I have the bulbs currently.

@4wealn if you're plugging in the ISY994 first then it's not seeing the PLM and would boot into safe mode (if you went to the Admin Console). I think it keeps trying to look for a PLM and corrects itself eventually, but might not. It's always better to plug the PLM first then the ISY994 as @Techman suggests. Here's the PLM service others have talked about in the past: https://www.ebay.com/sch/nilachidatasystems/m.html I think a few have used this service with good results. If you have the skills to try to replace parts yourself the same seller has a listing for a Capacitor Replacement Kit that you might give a shot. When you have the issue next time try logging into the Admin Console and open Event Viewer. Set it to level 3 and try controlling the trouble devices. Read more about event viewer here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer A successful "on/off" cycle using the Admin Console should look similar to this: Mon 09/12/2022 04:56:23 PM : [INST-TX-I1 ] 02 62 41 F8 2F 0F 11 FF Mon 09/12/2022 04:56:23 PM : [INST-ACK ] 02 62 41.F8.2F 0F 11 FF 06 LTONRR (FF) Mon 09/12/2022 04:56:23 PM : [INST-SRX ] 02 50 41.F8.2F 44.D1.80 2B 11 FF LTONRR (FF) Mon 09/12/2022 04:56:23 PM : [Std-Direct Ack] 41.F8.2F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 09/12/2022 04:56:23 PM : [D2D EVENT ] Event [41 F8 2F 1] [ST] [255] uom=100 prec=0 Mon 09/12/2022 04:56:23 PM : [ 41 F8 2F 1] ST 255 (uom=100 prec=0) Mon 09/12/2022 04:56:25 PM : [INST-TX-I1 ] 02 62 41 F8 2F 0F 13 00 Mon 09/12/2022 04:56:25 PM : [INST-ACK ] 02 62 41.F8.2F 0F 13 00 06 LTOFFRR(00) Mon 09/12/2022 04:56:25 PM : [INST-SRX ] 02 50 41.F8.2F 44.D1.80 2B 13 00 LTOFFRR(00) Mon 09/12/2022 04:56:25 PM : [Std-Direct Ack] 41.F8.2F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 09/12/2022 04:56:25 PM : [D2D EVENT ] Event [41 F8 2F 1] [ST] [0] uom=100 prec=0 Mon 09/12/2022 04:56:25 PM : [ 41 F8 2F 1] ST 0 (uom=100 prec=0) If the PLM is failing it would not send an ACK event and the hops might be an issue. If you pull the log file read about some errors you're looking for in the wiki for "Viewing the Log file".

@rssorensen That sounds like an interesting electrical problem to trip that outlet each day. Or is it only randomly? You can do like the OP and disable the program for a few nights to confirm that it doesn't trip if the program doesn't run. It depends on how large your system is and if there are a lot of battery devices or older devices. I think the "query all" was something used specifically to the older ISY devices that got carried over into ISY994. It is not included in initial setup for Polisy, but some have manually added it. I don't know exactly what it did, but seems to be that it just synced all the device status with the ISY so things would be correct. It ran at 3am because it was likely not to interfere with other traffic.

ISY994 latest release is 5.3.4 (not taking into account the z-wave comments above). @rswyman As the posts above outline where to find the updates and what to know before going to the update I will caution you...READ all the update instructions. If you're not a frequent user of the ISY994 admin console you might stumble into a few issues with the update process. Keys to keep in mind: z-wave board version (if you have z-wave enabled ISY994) Make note of any programs that have "Adjust scene" Make note of DISABLED programs (there have been several notes that in the upgrade process all programs become enabled) Make sure you're using the ISY Launcher method to access Admin Console Good luck! Post back if you run into any issues with the update.

@jkosharek That's nuts. Easy fix though. Not sure how active the developer is so not sure if the instructions will get updated. Thanks for posting the solution!

This might be something you need to open a support ticket for. I get the same error as you. Honeywell probably changed something and the UDI link is sending to a page that doesn't exist. I know I set it up in the past, but this time it did go to a bad URL as you say. I don't currently use this node server so not sure if it's working from my previous setup or not. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com FYI - @dbarentine or @bpwwer the link on the node server store doesn't point to the "read me" correctly for this node server. It's using the Polisy root address then "UniversalDevicesInc-PG3/udi-honeywellhome-poly". Different issue that can hopefully be easily fixed.

Not together. As @MrBill points out if you have to reset you must reinstall the firmware (simple process). Then restore the backup to get all your "user settings" (I assume you mean devices, scenes, programs, etc.). Process for resetting the ISY994 is found in the wiki - https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY You would need to buy a new MicroSD card (for the ISY994). Then you would need to go through the process outlined in the wiki - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card You should take some time to read the wiki. Really lots of information in there for all your questions above. Including power supply requirements.

@Ross I moved your post to the Notifications Node Server forum. I think the question is better asked of the developer @JimboAutomates. Or learning more about the node server from the Read Me linked from the NS store. It's been said many times that the "old" process of using email to text has become very unreliable, and not the suggested method. Using Notification Node Server as developed works with other apps to send push alerts to your mobile devices. Because it is not relying on email servers and your provider to support email to text it's usually more efficient once setup correctly. You just have to judge for yourself your ability to learn the new process and set it up how you best want to receive notifications. Or, if you're able to stay with the system that has been shown to have issues (at times) and just live with it as you might have it currently setup.

The reason this worked after update was it was a fix made between 5.3 and 5.3.4. It was a small fix, but widely talked about at the time since apparently a lot of people use the default settings.

Did you do this recently? If so you've probably got some corrupt files. There were issues (as @lilyoyo1 mentioned) with going the SSH route to update Polisy so UDI issued an alert to only update through IoP on configuration tab and "Upgrade Packages". If you've recently run any SSH commands to bring ALL packages up to date then you need to start a support ticket to get the corrupt files repaired.

Interesting issue, and great to know the process to correct. Thank you for posting the solution provided by @Michel Kohanim.

@Rich okay, good to know. Glad you got it sorted out for your situation. One question I would have is what happens when the underlying source code updates….do you think it would change the file you edited and cause the errors again? Glad it works now though.

What sort of errors were you getting? Haven’t heard of any NTP issues on the Polisy.