Phil G

The root problem causing eisy to crash was that it was in AP mode. I should have been able to diagnose that myself. I have other PG3 licensing problems, probably also caused by me during migration, but PG3 and eisy are now stable. I can't say enough good things about UDI's technical support. I have never experienced such a high level of responsiveness and capability. Michel gave me his time for free but I chose to run a charge through for an hour of programming and support. I suggest that anyone who can afford to do so, please consider paying for support when your issue is clearly not a bug.

I think I did change the user/pwd on Eisy after the migration. Not positive. I don't think I can reach PG3 anymore at all to try out your suggestion. I have a remote session scheduled with UDI support.

I submitted a ticket and hope to have it resolved in a day or two. I'll post the resolution here in case it can help someone else.

Here's a clean problem description: I have an Eisy on 5.5.9, and PG3x on 3.1.24. This is a migration from Polisy/PG3. For completeness, I'll note that I had a Zooz 700 Z-wave stick on the Polisy and have a UDI Zmatter dongle on Eisy. Eisy seems to be functioning normally. Insteon and most of the Z-wave nodes are behaving. The problem is with PG3. I can launch the browser window but, when I log in, it crashes IoX after about 5-10 seconds: the UD Mobile app shows 'ERROR: 503", the PG3 browser window pops up a red banner, and the UDI portal shows Eisy offline. This behavior seems to be consistent regardless of how I get to the PG3 browser window. I've tried the AC, Launcher, and directly http:// in a browser. I remembered as I was writing this post, that I probably incorrectly restored the PG3 backup to Eisy. I believe that I might have selected "Restore Backup" first, then used the "Migrate from PG3 Backup" after referring to the instructions again. I'm an idiot. Any suggestions other than 'get a new hobby' (too much invested) would be greatly appreciated before I write my confessional support ticket.

Excellent advice, all, thank you.

This works now! No idea why, but I'll take the win. Here's a screenshot of my Configuration tab. Looks normal to me. No internal firewalls set up. Turned off the malware protection. Will see if this clears anything up. Eisy is on 5.5.9 (firmware and UI) Instead of trying to access PG3 from the AC (which has been crashing Eisy), I exited the AC and opened PG3 via the Launcher. Here's the screenshot. The red banner popped up about 10-15 seconds later. It was running at first. Hard to read, sorry. It shows version is 3.1.24 and IoX at 5.5.9. The uptime was over 1 day before the crash. Hello Sir, I will try this after rebooting. Good idea, I hadn't thought of it. I did look at the Eisy log before the most recent crash. I don't see an "error log" option in the pull down, but I did look at the 3 logs available at saw nothing obviously wrong. However, unless it says 'error' or 'warning', I probably wouldn't be able to pick out a problem. The activity that I do understand a little bit is when some node servers are sending data and this activity was occurring and looked normal. Once again, I'm grateful for this forum community. Thank you both for giving this some thought. I'm going to try Trion's page refresh idea next. I hate to submit a ticket for a problem that I'm sure that I caused. I'm thinking of just plugging my PLM back into the Polisy and doing a factory reset on Eisy. Thoughts on that?

That all worked as you described. I got a security warning from Chrome (as always), but connected anyway. Here's the url: PG3 window opened and I used my Eisy credentials to log in and then Eisy froze (UD mobile started throwing the error/closed messages). Yes, I've tried this multiple times and I always get the "not found" message. I'll try that again a little later after another reboot. I'll also go back in to the AC and follow your other lead regarding the https login to Eisy. I believe I can get in to PG3 via Launcher and will verify later. Not sure what i can do to troubleshoot from there.

Thanks Dennis. I clicked the power button 6 times for shutdown, waited for the red light, unplugged for 30 minutes, then plugged it back in and waited another 30 minutes. Launched the AC, ignored the Update Packages notice, and everything is normal with IoX, Insteon nodes, and most Z-wave nodes. I opened the event viewer to use as an IoX heartbeat. Tried opening PG3 using the AC Node Servers menu. The PG3 login screen popped up, I entered my credentials, hit the login button. The event viewer halted when I hit the button. After a few minutes the AC gave me a java timeout error. So, that's where I'm at right now. This behavior has been going on for a few days. Before that I was able to open PG3 from the AC but nothing was stable. FWIW, the launcher can't find Eisy using https and port 8443. It can only reach Eisy with http and port 8080. Not sure why that is or if that is indicative of a configuration problem. Also, my node servers didn't port over from PG3 to PG3x. The names were in there, but no licenses. I was able to reinstall a few free NS's, but I need to put in a ticket to have my licenses moved over from Polisy. Gonna do the takes-forever reboot method again. THANK YOU for the help so far.

I managed to mess up my migration from Polisy to Eisy. Looking for some ideas on how to fix this before I submit a ticket. Not sure what I did wrong, but here is my current status: 1) Eisy is on 5.5.9; PG3x is on 3.1.24 2) On reboot, I get note to upgrade packages and the System Busy pops up for 15-30 minutes with multiple 0 -> 100% completion cycles. I let those finish and then upgrade packages; done this several times. 3) Insteon nodes work, most Z-wave nodes work. Some Z-wave nodes display as placeholders. 4) my 'Query All' program had become corrupted / failed and showed an error message in the 'Then' program section; I edited per forum suggestions and it runs now and when I made this change is when I started getting the System Busy notices on reboots. 5) Cannot connect to PG3x from AC without crashing Eisy. Can reach PG3x from IoX Launcher. My paid node servers have not carried over to the Eisy. I'd appreciate any ideas for troubleshooting.

After reading past the included setup instructions (follow the UD Mobile app instructions) I found that manually entering Eisy wifi password will not allow the setup to succeed. I'll close up this post and keep researching. BTW, yes, I am on 1.0.6. Thanks for the help Javi.

I was just about to be blown away by the exceptionally easy Eisy setup (see what I did there?), but it's hanging up on the wifi configuration. I'm using an Eero mesh wifi and usually don't have any problem adding new devices to the network. I see that the Eisy briefly shows as my connected network for the iPhone, but then iOS displays an error 'cannot connect to internet' and then disconnects. I'd like to just log in to eisy's wifi manually. What is the password?

Thank you for the tip. Just saw this but too late to try it. I let the Policy run in circles overnight continuously giving me the System Busy message. When I came back to it the next day, I pulled the power and it booted up just fine. Seems to be all good now. This is becoming my go-to solution for mysterious Polisy behaviors. Ignore it, be patient, come back later. Just joking, but in all seriousness my system seems to be more fragile now than with the ISY994. I guess it is much more complex now with a dozen node servers and zwave added.

I was working on some programs this afternoon when I noticed that I couldn't control any Insteon devices from the AC. I then noticed that the PLM was showing a red light, so I did an ISY backup and then pulled the PLM. I plugged it back in and then rebooted Polisy the from the AC. The Polisy came back up with the left light solid but the 2nd and 3rd lights blinking quickly. That was 1 1/2 hours ago and I've been getting a System Busy message that repeats every time it gets to 100%. Any ideas on what to try next? I hate to pull the Polisy power because the System message says 'do not unplug ...'

The solution seems to be to wait 19 days. The Ecobee NS now connects to my account and both thermostats are online. I have no idea why.

Hello @Jimbo.Automates, I keep getting this error while trying to link the PG3 NS to my Ecobee account: 2022-11-28 10:42:12,981 Thread-21 udi_interface ERROR Controller:_getTokens: _getTokens: authorization_pending :: Waiting for user to authorize application. 2022-11-28 10:43:12,912 Thread-22 udi_interface ERROR pgSession:response: Unauthorized: https://api.ecobee.com/token?grant_type=ecobeePin&client_id=2aFymqxQsvp6z7MHQFPqT89NQwC0Bu4K&code=trnEV8UoD5FIJST_TB1ZN_ht: text: { "error": "authorization_pending", "error_description": "Waiting for user to authorize application.", "error_uri": "https://tools.ietf.org/html/rfc6749#section-5.2" I have been running the NS for months with no problems, but I had to change my Ecobee account email. Ecobee requires deleting the account and creating a new one in order to use a new email. The new account is now linked to my 2 thermostats. I then deleted the Ecobee NS and reinstalled it so it would issue a PIN. I enter the PIN into the Ecobee portal which indicates a successful link. The NS, however, fails to recognize the authorization and throws out the above error. It eventually times out and reissues a new PIN. Tried it 3 or 4 times. NS gives me a new PIN each time, and Ecobee portal accepts that new PIN but the NS fails to connect. Any ideas?

You couldn't get the bridge firmware back to 2.22.6? Or, once you did that you still have problems? The developer is having issues getting his dev environment back up after moving.

I've never looked too hard into using HRV systems. Air exchange is not a problem, my house leaks like a sieve. I guess the HRV would act as a dehumidifier in the winter since it's chilling the indoor air before exhausting it. It would be interesting to put eyes on the drip line to see how much water you're removing. The solution to my problem was to add a few programs to change the dehumidification set point to 55% and set a state variable whenever the humidity hit 60%. This forced the whole-home dehumidifier to start running, and the changed state variable triggers an Alexa routine (which was my goal all along).

@larryllix, I see setpoints but not humid/dehumid device status.

Does anyone know if the humidifier and dehumidifier status are revealed as nodes in the NS? I don't see them. My downstairs Ecobee controls humidification, and upstairs controls dehumidification.

Yes, there are issues. Don’t update your Bond beyond 2.22.6. If you have, then you can always reset the Bond to its original firmware, but you don’t want the hassle. I lost all Bond devices in the Bond app when I wiped the firmware back to factory. I never had the NS working with it prior to that start over point because I had immediately updated the Bond as soon as I unboxed it, then added devices, then installed the NS and found it didn’t work.

Did you update the Bond bridge s/w? Some people are reporting (me included) that the current NS doesn't work with the latest version and they fixed the problem by reinstalling v2.22.6.

@ISY4Me, thanks for the factory reset tip. My firmware is now back at 2.22.6 and the NS is working perfectly as far as I can tell. I'm new to this, so perhaps it's missing some functionality that I'm not aware of. I'm only controlling a single device, and the discovery function in the PG3 NS dashboard successfully found it after the bridge showed up on the admin console.

CPeterson, what is your Mac OS version? what is your Java version? Regarding start.jnlp, you download that (after clearing your java cached applications and applets) and only run it once to put the "ISY Launcher" alias on your desktop. You then delete start.jnlp and use the "ISY Launcher" every time you need to get into the Admin Console. Of course ISY Launcher is sort of misnamed because it actually opens the ISY Finder. You then use the ISY Finder to launch the Admin Console on whatever UDI box is on your LAN (994 or Polisy, no difference). I'm sure that the following is not technically correct but, FWIW, I think about this process being like downloading an app installer (start.jnlp) and then running this installer which is what installs the app you want (ISY Launcher). Having the ISY Launcher (the app) sitting on your desktop is the end goal in this process. You always delete the installer. Delete your "start.jnlp"s. Clear the java cache (delete your java cached apps): Java Control Panel > General > Settings... > (accept defaults) Delete Files... > (accept defaults) > OK > OK > OK

Mac OS default is to disallow installs from anywhere except signed apps the Mac App Store. As Bumbershoot says, go to System Preferences > Privacy & Security > General. At the bottom of that window you will see 'Allow apps downloaded from:' and a note something along the lines that Java was blocked from loading (because it's not signed and from the App Store). Click on the padlock to allow changes to this setting. Enter your login info, and then you'll be able to override and install. My Java version is up to date at Java 8 Update 341. My only gripe with ISY console is the need to use Java. Have you cleared your Java cache before downloading the .jnlp again?

@lilyoyo, what was the original post if not the first post, above yours? I’m honestly confused by your comment. Please explain.