Jump to content

eisy setup issues


bigDvette

Recommended Posts

Posted (edited)

1). I can not set the time in eisy.  You click change location, you can pick a location and then it adjusts the time but incorrectly. If you close the admin console and re-open is has lost the setting.

 

2).  I can not get the pg3 to discover the isy.  I can add the isy manually and it simply will not connect. 

Can't continue testing until these work.  The eisy is on 5.5.0.

Edited by bigDvette
Posted
14 hours ago, bigDvette said:

The eisy is on 5.5.0.

I think you mean your ISY firmware is 5.5.0. 

14 hours ago, bigDvette said:

I can not set the time in eisy.

I have not had this issue with setting the time or the location. Sounds like it might be UI issue. I'd suggest clearing Java Cache and reloading IoX Launcher (fresh download of start.jnlp). 

What computer OS are you using? Win, Mac, other?

14 hours ago, bigDvette said:

 I can not get the pg3 to discover the isy.

PG3x on eisy should auto discover the ISY running on the same system. It should appear in the ISYs tab with a checkmark next to an active ISY UUID.  If try to add manually and you can't get it to load with "localhost" then use the ip 127.0.0.1. You shouldn't need to add user/pass in this step. Though I haven't attempted this to confirm. Mine just worked right away. 

 

eisy/PG3x has moved all the password settings into IoX so if you change the password for the system through the admin console it will update everywhere (this is a huge change from Polisy process). 

Make sure you check out the eisy user guide in the UD Wiki for additional setup steps or troubleshooting. 

 

Posted
42 minutes ago, Geddy said:

I have not had this issue with setting the time or the location

No problem for me either. Time is on time :-) 

Posted

Well, it isn't working.  I cleared java cache, downloaded start.jnlp again and re-installed.  Upon launch the Polisy and my 994 are in the list, no eisy.  I can add it manually and it finds it and loads the model and isy version.  I open the admin console and go to configuration page.  You can see no timezone is selected. The clock is off by 2 hours (to pacific from central).  I select dallas and click ok.  Come back, still nothing selected.  At top of screen the time has adjusted 5 hours backwards to 7:04 am, it is really 3:04 pm.  If I ssh in to eisy the time there is still set as pacific time.  

 

On the PG3 front, sometimes I can't even log in.  currently I can not. It redirects me to portal for login, and then local login to webpage just won't even login.  I tried localhost, 127.0.0.1, the actual IP and nothing works.   

 

Any way to start over?  I also couldn't get wifi setup to work, ended up plugging in to the wired connection.  happy to allow some debugging on this box.  I did do a restore from my polisy backup so I have nodes.  I know zwave has migration issues, but can't I move the insteon PLM. I only have 7 zwave devices and was considering re-doing the zwave piece.

 

Screenshot 2022-12-29 at 3.02.43 PM.png

Screenshot 2022-12-29 at 3.03.08 PM.png

Screenshot 2022-12-29 at 3.03.16 PM.png

Screenshot 2022-12-29 at 3.03.54 PM.png

Screenshot 2022-12-29 at 3.04.09 PM.png

Screenshot 2022-12-29 at 3.04.17 PM.png

Screenshot 2022-12-29 at 3.04.28 PM.png

Screenshot 2022-12-29 at 3.04.53 PM.png

Posted

I'm not sure what's causing the problem with logging in.  Is it reporting that authentication failed or just not doing anything at all?

If it is showing an authentication error then the username/password isn't correct (or UDX isn't running). PG3x uses UDX to authenticate using the local IoX credentials.

For the initial problem where it doesn't show the local IoX connected, that's likely because the browser has cached authentication information that is no longer correct and the UI isn't actually connected to PG3.  Logging out and logging back in will refresh the login info and allow the UI to connect to PG3.  So assuming you can get logged in again, it should connect and show the local IoX as connected.

I'm currently trying to find a way for the UI to detect this case and let you know that you need to re-login.

Posted

Look, something is definitely wonk.

sometimes I can’t log in, sometimes I get an auth error.  If I reboot eisy, I can get back in.

 

however it will never detect ISY in pg3 logged in or not.

 

the time setting issue is also weird.  
 

it isn’t a cache issue.  I’ve moved between machines that have never logged in and same problem.  All are macs.

I’ll fire up my gaming rig later and see if same issues in windows.

Posted (edited)

mine says 5.5.0 in AC and launcher.
 

Forgot I had boot camp on my Mac.  Booted to windows, Java wasn’t even installed.  Installed the launcher.  Eisy didn’t show up in list.  Added manually, got in and tried to change time.  Same exact issues documented above.  Pg3 page does not show connected to ISY and there is no list of isys.

can we maybe move on from its a cache issue.  Tried on 3 macs and 1 windows machine.  Any other troubleshooting?  I did restart with the 10 button presses earlier and it did reset and wipe out the restore and reset password back.

 

also, I did register on portal and activated portal from the AC.  

Edited by bigDvette
Posted

One thing I noticed when I did get logged in and somehow got PG3 to see the IoX there were two mac addresses and neither was the Polisy that is still active. One was the eisy and I am suspecting that the other my be the WIFI mac address of the eisy which I don't use.

Posted

Since I can't see what you're actually seeing, I have to make assumptions about what is really happening.  I thought I'd start fresh and see what happens.

I reset PG3x to factory settings and opened the UI using a browser I don't normally use.  This is what I get.

image.thumb.png.cd9d86cc5d02ba8b75da279eadc62c3d.png

Clicking the login takes me to the portal login screen.

image.thumb.png.065e3f18f4c5e41f3c22d90034a5f23a.png

Logging into the portal brings me to the PG3x login screen.  I enter the default credentials.

image.thumb.png.75a0a7db4cdf4b034e1ec0a88ea16331.png

 

That logs me in.  The local IoX is connected (yes, it's still 5.4.5).  Ignore the red status message, that's me trying and failing to detect when it hasn't actually connected, my current code displays that all the time regardless of the actual connection status.  If I drop the the ISYs menu I'll see my local IoX configured and selected.

image.thumb.png.c5e3760b89db7713bffa023903a7524f.png

If I reset PG3x again and restart it, this specific browser window will not change, but if I reload the page it will then show the the IoX as disconnected and no IoX will show up under the ISYs menu.  However, it will show the status as Connected (which is wrong (sort of)). This is because the UI is still trying to connect to PG3x using the authentication info from the previous login which fails.  To correct this, I need to logout and then login again to update the authentication info.  This case sounds like what you initially described.

 

 

Posted (edited)

@Michel Kohanimprobably too busy fixing things to write on here -- there was a bug that blew up certs after a restore, been online with him most of the afternoon. We went from 5.5.0 to 5.5.1 to 5.5.2 since noon :)

I completely understand what folks have said about how great the support is !!! 

Edited by MJsan
  • Like 2
Posted
4 minutes ago, bigDvette said:

Upgraded to 5.5.2.  Finder finds the eisy.  I can change the time.  PG3 finds the eisy and is connected.  Seems like 5.5.2 was the fix.

Thanks @bpwwer

Thanks for the update. Maybe it was 5.5.0 that was the problem. My eisy is still on 5.4.5 as I haven't taken the time to update it, too busy trying resolve all the PG3x issues.

Posted
8 minutes ago, bigDvette said:

On to next issue.  CAn't install / purchase any node servers. Clicking install button seems to do nothing.

Yup... cannot launch PG3. Just sits at Login :( tried clearing cache, Safari, Chrome, and Edge.

image.thumb.png.2fd2c651e119e18c0273bf2612ec7288.png

Posted

There are a few bugs related to installing node servers.  It may be possible to work around them, but it's a bit complicated.

I am currently only able to test installation with my own node servers as my eisy has a bad hardware ID and can't be registered with the Portal (should be getting a new one soon).

These are the bugs I'm aware of:

 

1) First installation will leave some of the node server files with the wrong owner/permissions.  This causes the node server to fail to start.  Using the re-install option should correct this.

2) When it tries to start the node server after doing the installation it will fail.  It actually tries to start the node server before the installation is finished.  After installation, stopping and then starting the node server may get the node server working.

3)??? Since I can only test with my own node servers which don't use the Portal or a license, it's possible there are bugs here that I won't see.  Based on some of the forums posts I suspect there is in which case, it may not be possible to install any node servers.

4) backup doesn't work.  Well it actually does work but it hits the same bug as #2 and PG3 is told the backup is done before it's even started.  The backup does happen (it's sitting in /tmp on the eisy) but PG3 doesn't see it and send it on through the browser.

5) Migration is just not possible yet.  There are three (four actually) things that need to happen to migrate node servers

    - First, PG3x needs to be able to read a PG3 backup.  The backup file formats are different between the two.  I have this bit already coded up.

    - Second PG3x needs to convert a PG3 node server to PG3x.  How the node server is stored and controlled has changed.  Again, this is coded.

    - Third, PG3x needs to move the node server to the local IoX.  Restoring the PG3 backup in step 1 will keep the existing setup. So if the node server was installed to a Polisy IoP, then after the restore it will add the Polisy IoP to the database and expect the node server to be installed on that IoX device.  I still have to write code.

   - Fourth the license needs to be migrated from Polisy to the eisy.  This happens via the Portal and not something I control.

Posted

So given all this, should the wiki really talk about backup and restore of pg3 like it is a doable thing?  
 

for a while all questions were answered eith a please refer to the wiki but the wiki gives a whole migration procedure that seems to not be remotely possible to perform right now:  

Posted

After delegating a couple of node servers from Polisy they show up in node server purchases. It looks like I can reinstall into the eisy from there. Will that also take care of the license issue?

Thanks

Posted

so, while looking at why I can't get any node servers. I went to portal and it said I needed to activate again.  I went through mobile process to retry automatically.  My UUID has changed.  how can it change?  I thought it was hardware level coded.  the one in my AC and in portal have changed and so has the Mac address registered with my router.

Posted

 

31 minutes ago, bigDvette said:

so, while looking at why I can't get any node servers. I went to portal and it said I needed to activate again.  I went through mobile process to retry automatically.  My UUID has changed.  how can it change?  I thought it was hardware level coded.  the one in my AC and in portal have changed and so has the Mac address registered with my router.

Did you change between wired and wireless network? I know that would change the Mac but I did not know it would change the UUID!

Posted
2 hours ago, bpwwer said:

) First installation will leave some of the node server files with the wrong owner/permissions.  This causes the node server to fail to start.  Using the re-install option should correct this.

2) When it tries to start the node server after doing the installation it will fail.  It actually tries to start the node server before the installation is finished.  After installation, stopping and then starting the node server may get the node server working.

3)??? Since I can only test with my own node servers which don't use the Portal or a license, it's possible there are bugs here that I won't see.  Based on some of the forums posts I suspect there is in which case, it may not be possible to install any node servers.

I installed two node servers and had to reinstall each one twice to get them to start.

Guest
This topic is now closed to further replies.

×
×
  • Create New...