Geddy

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.

Try again. @MrBill said the seller communicated quickly earlier this year. Sure, probably a little busier these days, but still should be responsive. Might have just missed the question if in with other communication. I find eBay communications like forum posts...you get more attention (and quicker answers) when you start a new message rather than adding a random question onto an existing string of communication. But looking at this item it has "Keypad Linc" as an option...so I'd say they probably do.

See the link 2 posts up...then see seller's other items.

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

Nice to hear about this service available in Canada. There's been numerous posts around here of service available through a seller on eBay that's been used by a few members on the forums. Also, there's been posts about recapping the PLM, but looks like the listing usually linked to is currently out of stock. There are options, and as you said you've hoarded a few for personal use.

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

Click the box that says “use default” and you don’t need a password. I’ve also edited to remove the post so your private info is not being shown on a public forum.

Absolutely! I never access PG3 through admin console (or the ISY Finder window). Use the IP of the Polisy and add :3000 and get directly to the interface using any web browser. On the ipad (or computer): http://<ip of polisy>:3000 (be sure to use your IP numbers in the crossed out area of the example) Boom! You're there. It's a 70/30 shot of getting there using http://polisy:3000 as some routers don't handle local addressing for Polisy correctly, but my current router does, so it's been nice to not have to remember the IP address. Although I did make a bookmark to the Polisy web interface on my browser of choice. Like @bpwwer, I just tried to log in from my iPhone (using Chrome) and it worked like a snap. It did warn me that it wasn't a secure connection, but that's normal. Just remember it will want you to log into ISY Portal account first then come back and log into PG3. I think you can skip the portal login, but it's always best to just go through the Portal login process so all the node servers can update correctly. Where are you getting stuck in this loop for login? Make sure that if you're using "admin" for the user that you use the lower case A. Often times on iOS it will capitalize the first letter of a form. The user name is case sensitive (yep...just found that out when I tested and used "Admin" it said wrong credentials changed to "admin" and zipped right in)

@sjenkins Honestly can't say I've tried this with Polisy so can't help. But just make sure do you only have one ISY in the Portal account now? In the "My Profile" on the top right is you IoP selected as the preferred ISY? Since you're getting an error if you try to remove them at this point I would think that's a support ticket waiting to happen. Sorry. Let us know what comes of the ticket.

Interesting to learn. Might look into this - https://www.reddit.com/r/homeautomation/comments/poeff3/rekeying_the_ultraloq_ubolt_pro/ Which sent me here - https://support.u-tec.com/hc/en-us/articles/360056461591 You had me interested in this lock until the support site says they're using Schlage. All my doors are currently Kwikset knobs and deadbolt. Wouldn't want to change out the whole house right now and I've had issues with Schlage in the past that I can't get my wife to be on board with trying them again. Good luck with the re-keying process.

Fantastic! Glad things are working as expected! Thanks for posting the update. Indeed you are correct in the assumption. Your standard ISY994 will continue to work just fine and the Polisy can push node server information to the ISY as long as you have it setup in the dialogue to be the target ISY. The IoP just puts everything into one device so you can retire the ISY994 equipment. You'll need the PLM and a different cable to connect the PLM to the Polisy if you have Insteon devices that you want to continue to control if/when you move over to ISY on Polisy (IoP). Read more about moving to IoP in the wiki. Just make sure that ISY994 is in your PG3 setup and all should be good. If PG3 is pushing node server data to the IoP then there's no communication between the ISY994 and IoP so you couldn't include them in any programs or scenes. Enjoy!

Sounds like going the admin.jnlp route might be working better for you. Please let us know specifically. Since you're on 4.9 and you're working fine...STAY THERE! (personal suggestion right now...especially being a mac user with an "outdated" version of macOS.) Since you're still on ISY994 and it's working for what you have currently...STAY WITH WHAT YOU HAVE. UDI has new products out that are the current and future for controllers. Save your money and get an eisy when it comes out (time still TBD, but could be by EOY). Or you could wait for a Polisy to be available. But I would not spend money to update the ISY994 at this point. It's still a workhorse, but the equipment is not getting any planned updates at the moment so Polisy or the newer eisy will be the controllers you want to look for. Do NOT update to 5.x. It's a pain at this point (IMO). As I mentioned above...you're on an outdated macOS. There are a lot of fixing steps required for most 4.x to 5.x updates so I wouldn't want you to get messed up in the middle of an update if the OS messed up something. If you have access to a windows computer then I might suggest it be done, but at this point I'm more on the side of "ain't broke, don't fix it" for your situation. So, if you're able to access admin console regularly that's great! Let's call this a win and start saving a few bucks for a new controller when they're available. Just going through the process of updating the firmware won't update the UI. You have to download a new version of admin.jnlp following each Firmware update to keep UI/FW matching. This is why the ISY Launcher process was developed. Whenever the FW changes you have to get a new admin.jnlp file from the ISY994 itself. Too many users forgot this step during the 5.x beta/update processes that UDI needed a way to develop a more streamlined (i.e. idiot proof) process. Sadly, even that has been met with ridicule...mostly from macOS users because mac is not very "friendly" at this stage of interaction (IMO). So I think you're best where you are now. As long as you're able to login directly with the admin.jnlp process.

@caknowles Are you sure that your portal license is current? When you're logged into my.isy.io go the ISY Portal Access License under "Select Tools" -> Information If should say: "License Active: Yes" If not then you need to renew the license. It's possible it's just expired and simply renewing the license will help. They're usually only good for 2 years. It's simple to forget to log back in and renew it and sometimes I'm not sure if reminder emails get overlooked or end up in spam/junk because they're infrequent. Either way...if you've got a support ticket open then I'm sure you'll get taken care of, but wanted to be sure to offer help and suggestion to look at the portal license status. Make sure to post back the solution just so it might help others if they have similar situation and find your post in a search.