ISY4Me

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

@bpwwer I have looked at the /var/log/messages and attached the output starting with the last PG3 3.1.16 run. On 3.1.16 I did not look to see if the ISY was loaded, but the log file is different than the subsequent starts of PG3x 3.1.17 where it is complaining that IoX Service is not loaded and it fails to get the platform UUID. Output of "pkg info PG3x" is also attached. This EISY has seen very little activity... I received the EISY, Updated to 5.5.2, Restored Polisy ISY backup and did z-wave migrate, but this issue with PG3x was discovered after the restore of the Polisy ISY file. During this issue I have rebooted and restarted a number of times and it had no impact. PG3x Log File Output messages.txt PG3x Package Info.txt

Yes, I have both logged out and restarted PG3x on the EISY a few times. The EISY has been power cycled a few times. I have noticed a comment in The Portal… “Access Denied. Pending approval by owner”. I have not requested the Portal License be transferred yet nor have I requested a trial for the EISY. I was waiting to see how the Polisy -> EISY migration goes.

Thank you @bpwwer... IoX was restored and I started to look at PG3x restore process. Access to PG3x is not a problem, but it will not contact the server (I assume because I have not activated a Portal access yet). Does the ISY have to be added to configuration for the PG3 restore to work properly? I can't manually add the ISY (it fails with localhost or IP with Port 8080)... and it is not automatically detected... is this related to not yet having the Portal access active? Do these both have to be resolved before I start the PG3 restore process?

@bpwwer My work with the EISY is in progress and from the “out of the box” state, all the packages have been updated, included PG3x. The IoX Launcher is running fine and both my Polisy and EISY ACs are visible and accessible. In thinking about this process of moving to the EISY. I was wondering if the PG3 to PG3x NS migration should be done first or after basic ISY restore and z-wave migration ?

@Jimbo.Automates I saw that @bpwweris working on the issues with PG3x and is hoping for an update in the near future. My ecobee NS is one of the key components of my Polisy and will continue to be so on EISY. With all of the recent activity, I am leaving my Polisy system alone and it runs as my main system. Are there any cautions or guidance you can offer in advance about running Ecobee NS on PG3x?

I received a reply from @Michel Kohanim this afternoon regarding my ticket on this issue. Here is a cut/paste of his response... shared with his permission. There were no suggestions as to how to snap the excess off the board, but at least we are aware of the guideline. Michel Kohanim wrote: 2023/01/01 17:28 Hi Jim, Yes, so very sorry. You need to snap it in the middle. JWeaver01 wrote 2022/12/31 08:05:27 With no guidelines or instructions included with the Enclusure I was trying to mount the “as shipped” ZMatter board into the Enclusure intact getting interference with the posts of the antenna connector. Yes, there was extra depth to the cable that I originally pointed out, which made that interaction worst, but that may be a non-issue. But after looking closer at things this morning and seeing that one image of a mounted board (see attached) I am beginning to think that the full ZMatter board was never designed to mount in the Enclosure. Is snapping (or cutting) off the top half of the ZMatter board the sanctioned method approved by UD? Recommendations on how to do that without damaging the board?

While the old photo shows how the half board cleanly fits in the Enclosure, I am really surprised this was or has not been discussed by the UD Team. Just for clarity to the members reading this, I am not advocating such a physical modification until directed by the UD Team and seeing that this is a holiday weekend we may not see any real guidance until next week. If I get some feedback from UD I will post it… until then I am waiting.

It took me some 30 minutes to get the board in the enclosure as you are right that is not easy to fit it. The board is slightly tilted and one of the antenna pins kept coming off the board. Finally I did get the board (slightly tilted) in the enclosure and hopefully the antenna pin remains in place. I don't remember whether the problem pin is the Zwave or the Zigbee, but my eisy now does recognize Zwave. In other words, I'll have to wait for the Zigbee firmware upgrade to confirm that both pins remain in place. @asbrilFrom your comment it sounds like you did not remove the top half of the ZMatter board as was shown in the photo I added, as I had the same issue with the board being tilted any not completely seated… by not completely seated, I mean I could not use the supplied screws to “attach” the ZMatter board to the existing board in the enclosure (the screws were not long enough). It was tilted enough I was concerned about contact to the lid on the Enclosure and that left me uncomfortable. If removing the top of the ZMatter board is the recommended method (as shown in the photo) I can’t find it documented anywhere. I have submitted the question to the UD experts on a ticket to get an official answer.

I received my ZMatter Enclosure yesterday. In looking at the separately purchased ZMatter board there is no way to mount the full board as originally shipped into the enclosure without interference with the internal antenna posts, which keeps the board from seating properly. I ran across one old forum photo of the enclosure. It clearly shows that to eliminate that issue, the top half of the ZMatter board was removed or snapped off. Not finding any guidelines for this procedure (no instructions included with the Enclosure), I wanted to ask the community if snapping off the top half of the ZMatter board is the correct procedure? I don’t want to do anything that will impact my board warranty.

I will be taking a slow approach to moving to EISY. My base configuration is Polisy, Node Servers and Z-Wave running on 5.4.3 I want to start the configuration and migration to EISY in parallel until everything is stable. The EISY will have a different IP running on 5.5.2 (or later) and will only be powered up when the Polisy is powered down. My work with the EISY will start in a few days and I was wondering if we can have both Polisy and EISY configured in UD Mobile at the same time?

@bpwwer Is it safe to assume that these recommendations of moving PG3 all apply if moving from Polisy to a fresh installation in EISY?

@tmorse305Thank you for the example. I had just started something similar and as I use more node servers this definitely sounds like a great addition. Much appreciated.