ISY4Me

The ZSE42 was one of three devices that was not behaving properly after the “move to ZMatter” operation on the EISY… and yes I also saw the missing nodes. in an attempt to see if I could impact the ZSE42 on the EISY I ended up excluding/including. Even then none of the fields would populate and no missing nodes were added. At the end of the day I factory reset EISY/ZMatter and powered it down and put the Polisy 5.4.5 w/Zooz back online. Since I excluded/included the ZSE42 on the EISY, there seemed to be an impact when the same ZSE42 was examined with the Polisy/Zooz running things. Running with the Polisy/Zooz I did another exclude/include and the ZSE42 returned to normal functionality with all expected nodes and data populating. After the next update, I will try again.

My apologies… I typed wrong and corrected it… I was commenting on my ZSE42

I just started to examine the results of a migrate to ZMatter on 5.5.3 and I was seeing the ZSE42 nodes are fewer than existed on Polisy 5.4.5.

There are two of us still seeing the system busy loop on 5.5.3. We are seeing it just on the IoX Restore… before ZMatter migration https://forum.universal-devices.com/topic/39796-support-thread-iox-release-v553/?do=findComment&comment=356459

@Javi After issues trying again to migrate this afternoon, I decided to factory reset everything. With the EISY in factory reset mode I can run Polisy and EISY at the same time as EISY is only in factory reset state right now and not running a z-wave controller. I saw what you meant by the "pressing the search icon" next to the local IP. That worked to allow local test to pass, but when I tested it later with the search it would not find the IP... with ethernet cable plugged in on EISY. I rebooted the box and then I had IoX with EISY.local:8080 and my IP 192.168.27.78:8080 show with search... had not seen EISY.local before and in the next second I hit the search again and EISY.local:8080 did not show. So I left it as the IP:8080. When I run the Settings > WiFi Configuration I finally had it get to the "WiFi Credentials have been uploaded" screen, but the process never completes and always errors out with "could not find System on Network" which is odd as I can load the Launcher and AC. Attached file show the WiFi Configuration responses, in addition to an error that came up when I clicked on the "Reenter WiFi Credentials" button... see the pics. Also for what it is worth, I do run a hidden WiFi network, but I tried it both ways.

I will have to test out your comments on the IP tomorrow. However, no the WiFi setup never successfully completed... all of this being done on iOS. The initial setup was manual with ethernet. As far as the WiFi, yes I started that from the Settings > WiFi configuration. I have taken the EISY off-line for the day and put the Polisy back in control, but I will try again tomorrow and add some screen shots.

My current strategy is to keep my Polisy as the main working system and try to migrate to EISY and move to the EISY when it is stable. My Polisy remains on 5.4.5 and my EISY is now on 5.5.3 So, with the new 5.5.3 version I thought I would try again. Go to the AC of EISY and Factory Reset Go to the AC on EISY and Update Purge Java files and update Launcher and restarted EISY and verified Firmware and AC were the same version. From a fresh copy of the Polisy backup restored the Polisy backup file to the EISY with the ZooZ z-wave plugged in. I was able to get through step 4, but after that the "System Busy" box would come up again and take forever to go from 0 to 100 over and over again (Zooz USB still in) with system busy all the time. At a high level it does look like it restored the devices, but every time I restart the EISY it still goes into the "System Busy" loop (Event Viewer shows it's last step as Refreshing Views). At a high level, this is the same as it was before the update.

I set up the EISY using ethernet and all the normal connectivity is fine. Today, I started WiFI config on UD Mobile. My Local WIFI network is set in UD Mobile - Settings - Local Network Connections - Systems Network Relations. Use ONLY Local Connection is OFF. In that Settings menu when I tell it to Test System on Local Network it fails if I am on WiFI and passes if I am on Ethernet. Portal configurations are not yet set up. I have my WiFi configured with MACID Local Access Control on an Apple Time Capsule 2Tb unit... currently running on 2.4 GHz. I have entered the UUID of the EISY box in the MACID list, but usually the WiFi MACID is different from ethernet. I tried with Access Control disabled and I get the same setup fail, so I suspect that on it's own is not the main issue. When I perform the UD Mobile WiFi setup I get through all the questions. It sees my WiFi as set in the Settings and I enter the passphrase for the WiFi access and it asks permission to join. At that point the progress bar just about finishes and it just hangs and nothing happens. Suggestions?

@bpwwer Thank you for the feedback. I completed the MacOS OS re-install on my MacBook Pro Java machine and it had no effect on the Log Out / Login process as the solution to accessing the EISY PG3x web access in Safari. Perhaps some of this is just the age of the MacBook Pro (2013 release)... the machine is old and Apple dropped support for it some time ago. At least I have FireFox as an alternate on that MacBook Pro. Thanks again

@bpwwerThe MacBook Pro system is used for all Java work and is by default where I run all the ISY work. This is the system that demonstrated the initial issue with "Not connect to server" and "IoX not found" in EISY PG3x. This system has been in use for some time so I am concerned about unknown issues with years of updates. I am getting a current backup of the computer as I type and when that is done I will reinstall the OS. That should reload an new version of the OS and all its components. Sadly that is the only way to refresh the Safari app. Since this system has been in use for a long time, this seemed like the better thing to try first. When everything is back up and running, if the Log Out / Login process changes it's behavior I will send a reply to this message. If re-installing Safari does not change the behavior of EISY PG3x, then I change the default browser to FireFox which seems to work. Thanks for your help.

@bpwwer I have notice that on the MacOS on MacBook Pro the Log Out / Login process does not work on Safari. I have seen the red box for "Not connect to server" and "IoX not found" on Firefox too, but there, the Log Out and then Login process works just fine. Might you have any idea as to why Safari is not responding as expected to the Log Out / Login. process?

I have seen the UD Portal token expiring message... I think the Portal handshake simply times out. All I do is logout of the Portal and log back in and so far that problem seems to go away.

@asbril @bigDvette I was going to respond that I have tried all of your suggestions, but I had to stop typing and think a little. I had tried a different browser, but on review it was also Safari on a different computer, so it really was not different. What really deeply brothers me is that accessing the PG3 on Polisy works just fine on Safari on my MacBook Pro which is my machine I use for all my JAVA work... so it has been my default UDI computer. So it is human nature to think that it would work on a slightly different IP address for EISY PG3x. So, I went to my desktop MacPro. Even there in Safari, EISY PG3x shows that same error... I guess that was no surprise. Then I cranked up FireFox on the MacPro... I keep it there as a alternate as sometimes things just don't work right on Safari... I should have remembered that. On Firefox I used the same IP for EISY PG3x and the Dashboard came up exactly as it should. SUCCESS. Now what is really strange... I went back to the MacPro. On that system I run Parallels and I have a virgin installation of MacOS that runs in a Virtual Machine. It was installed from the rescue disk from my MacPro MacOS. In that Virtual Machine I started Safari and EISY PG3x started up just fine on that machine with no errors. So, at least I have a workable solution for EISY PG3x with FireFox, but the fact that EISY ran fine on a virgin copy of Safari in the Virtual Machine tests bothers me as it says that fundamentally Safari is compatible, but that my installations of Safari on the MacBook Pro and MacPro are somehow broken. @asbril and @bigDvette thank you for taking the time to think about this issue and making the suggestions that you did... they woke me up to trying an alternate method.

I think I have seen that error once, but I can't comment on what was unique about that day. I can only recommend making sure you are using the right URL or start PG3x from the Launcher and see if the response is different. I have never had the error persist, so it is essentially I can't comment on exactly what I did to make it go away.

As noted in the comments I have already done that and the current state is post factory reset.

The image says it all... This issue has existed since I started with EISY. I waited until PG3x 3.1.17 was released before attempting anything with the EISY or the migration process and this issue was present starting on the first attempt of bringing up PG3x. My first Polisy -> EISY backup/restore migration attempt had some minor issues so everything was factory restored and the image above is from this morning... fresh factory restore, base IoX no nodes - no devices, Z-wave or ZMatter not installed. The original discussion is embedded in original support thread (under the postings from ISY4Me, shown below... Current status: No issues connecting to the IoX Launcher. All hardware has links in Launcher and any of the sub-links to AC or PG3x work fine No issues starting the PG3x interface, except for no communication to the server and no detection of IoX. PG3x connects to the Portal just fine and I can see all available node servers, but can install anything with IoX not detected. Old Polisy links in the Launcher all work fine, including the PG3 link. Polisy PG3 link does not have these connection issues and the Polisy IoX AC works as it should and it's PG3 environment is completely functional. As the z-wave has yet to be migrated, both Polisy and EISY are running at the same time. However, in the first attempt to migrate, once the migration occurred ONLY one device would be powered on at the any time to avoid any z-wave controller confusion. But, even in the environment of EISY only running, I would still get these PG3x errors. There was an activity in the original support thread where it was mentioned that the EISY -> Portal communications had to be "approved" for the PG3x to work as designed. That approval (after Trial setup) was executed last night and the problems I have defined above still existed... no change. Also, please note my AC and PG3x activity are all running on Java and Safari on MacOS There have been some ticket communications with @Michel Kohanim. In the support thread discussions@bpwwerhad commented on some posts, but overall this issue has not advanced. @garybixlerhad noted some similar behavior in his thread... but it appears that his discussion has also made no advances. I would love to have the experts involved in this problem and hopefully anyone else that is having similar EISY only PG3x issues can provide a history of their problem so we can expose the collective issues to the expert team.

Well, I was finally able to get it approved. @bpwwer had indicated earlier that a license was not required for PG3x to function, but the EISY required a license to get that communication to the Portal to approve. So, I installed the trial and activated it in the AC after a power cycle. Sadly, approving the communication did not impact the "IoX not found" and the "Not connected to the server" in PG3x and it also can not be manually added. Time to update my ticket.

I have tried rebooting from the local terminal, power cycling and a few other things and the approval continues to fail... but I have not given up.

Yes it is... and to be assured it was active I was logged into it in a separate window. Hopefully @Michel Kohanim has an easy solution or suggestion.

@asbriland @dwengrovitzYes I did. I even removed the Portal UUID item that was there for the EISY, logged out and went back into the Portal and added it just as you showed. Even then the approval in AC -> Configuration -> Portal still failed. I am not sure what else to try... I have an active ticket on this issue and it has been updated with this issue.

@asbriland @dwengrovitz When I click on "Approve" I get a Stop Sign response with "Bad Request" in the box. Any suggestions?

I never added it the EISY... it was just there when I went to the Portal to see what was going on. Is it safe to assume that I am only approving only the device addition and that this has nothing to do with license migration or trial?

@asbriland @dwengrovitzCan you please clarify what you mean by the "approve" action. I also have the "IoX not found" in PG3x and it also can not be manually added... are you saying that approving a pending action in the portal will remove this problem? When I look at the Portal my UUID for the EISY is not grayed out, but the status light is yellow with the comment "Pending approval by owner?. When I look at the AC - Configuration - Portal. It says the Portal is Online and Registered. In the same page where it says Requested Services it says Pending with Approve or More Info options. So, you are saying that this Approval has to be done? What am I approving? I don't want to move my license yet and I was hoping to delay activating a Trial until things started to look clean. Thanks in advance.

@bpwwerAfter continuing to examine the EISY, there were issues with how the system was preforming after the restore of Polisy backup and z-wave migration in addition to the issue with ISY not autoloading into PG3x. In an effort to assure the initial setup was not at fault, I decided to reset ZMatter and factory reset the EISY. I was expecting to see the factory reset return the state of the box to where it was when shipped, but based on the "pkg info isy" results it returned the state to what existed after the last Update as the PG3x and the ISY was still at the updated 5.5.2_1 version and PG3X was still 3.1.17_1 version and not the 3.1.16 that was present when shipped. Anyway, starting fresh after factory reset, I am still seeing the same issues with PG3x and the IoX Service not starting and therefore not loading into the PG3x configuration nor allowing me to manually add the ISY. Attached is the log file after the restart... I hope this helps shed some light on the issue. pg3_1-5-2023_95139-AM.zip

As shown in my post in this discussion. I am dealing with a very similar problem with the ISY not auto loading in PG3x or not allowing me to manually load it. In looking at my /var/log/messages I see that the system is complaining that IoX Service is not started. I had not checked this before upgrading to PG3x 3.1.17, but the log file indicates IoX Service was running under 3.1.16. If you see the same thing it would be good to comment so @bpwwercan look into it deeper.