hart2hart

Thanks.

I’ve got one that I never used beyond couple hours of testing. Will sell for what I paid. PM if interested.

Jumbo, As a follow-up. The connection to Flume has been perfect since this update. Thanks, Paul

To confirm, is this the button from within IoP which I'm not using yet and I've not been into the specific Polisy config screen since I set the box up?

Anything we can do to assist?

Should we do update as outlined in the two posts to ensure we are set for future or wait for additional details/clarifications/more straight forward upgrade.

I just moved MagicHome PG2 to PG3 Node server. It installed, found my LED strips , and I can control them. It did not install an overall node where the Node server status could be checked. Not sure if that’s by design or it needs to be added but in spirit the Node server is tagged as a beta, I’m reporting it. Thanks, this was my last PG2 Node server!

All of these options have become very unreliable in the past year with cellular company’s policy updates.

Thanks for explaining.

Using standard notification with customizations setup with the destination being UD Mobile. Eg The To: would be UD_Notifications. I’m guessing this would require IoP firmware update.

@Javi , This is wonderful. Could a special destination for regular notifications (like is done to write to a log file on ISY web server) be assigned for UD Mobile? That would enable same notification to be sent through multiple channels at same time. Thanks, Paul

It’s the plm. Lowest number links tend to stay. Replace the capacitor and you’ll likely be good for years. There is an entire thread on replacing them. Some guy sells the caps on eBay.

I’d reach out to UD and describe what has happened. They’ll know if it’s an issue and how to correct. I just didn’t want you to miss opportunity to get expert advice before the start over process begins without expert guidance considering how it failed/ was restarted in middle of PLM restore.

You were restoring a PLM and it appears you stopped it and are going to start over. Restoring a PLM writes all the links to the new PLM and IoP then goes through one device at a time and replaces the old PLM address with the new PLM address inside the device. If you stop it mid process and it wasn’t just a hang before it really got started, I’d think your individual devices have a mix of old and new PLM address. Peace out.

It appears from reading that some of your individual switches etc may have had the Insteon address of the 2412 PLM written to them. Others may still have Insteon address of your 2413 in them. Hence your network is an odd state. When you start over, not only does Polisy need to get in proper state but all devices will eventually need the address of the PLM that’s in place. I don’t have advice but I’d evaluate it. Maybe ask UD.

I’m guessing you are in an odd state. Some of your devices have the 2413s PLM address and some were updated to the 2412 PLM address.

You will need to find or make a cable that goes from RJ45 to DB9. The RJ45 connectors on Polisy are Ethernet not rs232.

So funny and not trying to pick a fight but I didn’t get any notice from Google and I don’t have time to read every post from here. The one you quoted looked to mention elk in title. I would clearly have invested 5 minutes if I’d known. With 2FA in my experience, if the IP address changes, they ask you to authenticate again. which might negate the special app passcode. Wouldn’t that be an issue in the longer term? Xfinity changes mine at least once or twice a year. I’ve been using Spark email client for about a year since texting changed. FWIW I am moving this to an outlook.com account. Maybe just kicking can down the road but…

If you turn on two factor authentication for the account, where on ISY does it ask for credentials? If your ISP gives you a new IP address will it require authentication again? I considering moving notifications smtp to an outlook.com account.

I stopped getting Email notifications from ISY a couple days ago after like 12 years. I searched and it appears that Google has disabled simple username and password access to smtp. All this protection is killing me. I should be able to mark the account as non critical. Damn! Can others confirm they have the issue. ? If so, what are you using for smtp now?

Thanks. It's installed.

I'm having the same problem. It did not update since first thing this morning. I restarted the node and it didn't update. I pushed Query from ISY AC and it updated all. grabbed a log after restart and the query that includes not activity since this AM. I didn't get any of my message saying it was not authenticated etc. I'll upload to github but how do i upload log so its not open in case I missed covering up some sensitive data?

I had to refresh store before it showed the .14 version.

Thanks! It felt like that was what was happening. Just wanted to update you and make sure.

Thanks installed it - I think. I refreshed store and then restarted the node server. While it is connecting it says version is 3.0.14 for a few seconds but I can see it revert to 3.0.13 on the screen. Its likely running new version but just displaying 3.0.13.