bpwwer

Please submit a ticket. The 403 error is not something I've encountered before and it's not something fixable in PG3, it's the IoX firmware.

Looks like there's an AWS issue effecting many of our AWS based services (portal login, node server store, etc.) No ETA for resolution at this time.

A bug in the UI, reloading the browser page should correct it.

When PG3 tries to add the nodes to IoX, the IoX is responding with forbidden (http error 403). The initial connection to the IoX is succeeding so it's not a problem with configuration and forbidden isn't an authentication error. I don't know why the IoX would return that. Have you exceeded the number of nodes allowed on the IoX? I'm not sure what the limit is, 1000 maybe more.

Eventually, only PG3x will be supported and PG3 will be deprecated. The current state is: * eisy can only run PG3x * Polisy can run either PG3 or PG3x, but once you migrate to PG3x, you can't migrate back. PG3x has remote access capabilities that PG3 doesn't. Currently the Ring node server makes use of this and thus, will only run on PG3x. PG3 is probably a bit more stable and we're working to get PG3x to the same point. My slowly transitioning uses from PG3 to PG3x we have time to stablize PG3x without dealing with a flood of migration issues.

The reboot is supposed to: 1) install PG3x, overwriting PG3. (There is no visual indication this is happening) 2) start PG3x, which detects that it needs to migrate from PG3 and starts migrating node servers - If you connect to PG3x via the WebUI during this process, you'll see pop-up message as each node server is migrated Note, that you do have to close the WebUI to PG3 and open a new browser window for PG3x. Note2, PG3x uses the same login credentials as the Admin Console, it has no default nor does it use whatever you changed PG3 login credentials too.

I'm not familiar with the SolarEdge node server code, but typically, a node server will attempt to create the nodes on the IoX when it starts. First try restarting the node server, it should attempt to add all of it's nodes to the IoX. If it still doesn't work, we'll need log information (download log package from the node server log screen) and post or PM the node server author.

It would be better to move issues with OpenWeatherMap to the node server specific forum. However, if you enable debug level logging, you'll see the actual URL that the node server is using to query data from the servers. You can copy and paste that URL into a browser and see exactly what the server is returning. @apostolakisl if the store isn't displaying you might want to try rebooting then refreshing the browser page. It may be that PG3(x) doesn't have Portal credentials but something is cached and not allowing it to prompt you form them. @kurelgyer If you can't log into PG3x and you don't get an error response when you try, it typically means that a system service on the eisy/polisy is hung and you'll need to reboot to get it working again. In some cases, you may need to run "Upgrade Packages" followed by a reboot.

@Michaelv Looks like the same issue as @mitchmitchell, the plug-in is not able to see or connect to the eisy. Make sure you have the correct ipaddress / port information and the correct username/password.

Hello Everyone, This is the support thread for PG3x v3.1.29

Hello all, We are very happy to introduce PG3x v3.1.29 for eisy and Polisy. With these releases, there are changes to how Portal access tokens are managed. Prior releases attempted to manage the Portal access token in the web UI code. This tied the access toke to the PG3x login/logout functions requiring a new access token every time you logged into PG3x via the web. With version 3.1.27, the management of the Portal access token has moved into the PG3x server code. PG3x will request the WebUI to obtain a Portal access token only when it needs a new token. The server side will maintain the token indefinitely so you will no longer need to provide PG3x with a new access token when logging in to PG3x via the WebUI. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure and enable features based on remote access. Polisy users may update their systems to use PG3x if they want access to the new features. PG3 will continue to get updates for the foreseeable future. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you should restart/reboot the eisy. Do this from the Admin Console, Configuration, Reboot. Once PG3x has restarted, reload /refresh the browser page. Changelog for 3.1.29 - If refresh token expires, request UI get a new token. - Add menu item to UI system menu to reset portal credentials. Changelog for 3.1.28 - Remove unnecessary log messages. - Update local globalsettings when db is updated. - Add log message to warn of missing key if a key that doesn't exist is queried. - Handle 'seq' field in incoming messages from frontend clients - Synchronize settings with frontend. - Clean up error and log message for portal based queries. - Force devMode to be 0 or 1

Thanks, that's currently the expected behavior. There's a timing bug that causes it to prompt a second time but it doesn't cause any problems. With this version, you shouldn't get prompted again for portal logins. PG3(x) should now manage the portal access token for an indefinite amount of time.

What have you set the IP address/port too? What shows up in the log when you start the plug-in?

Are you sure the plug-in is configured properly? From the log, the plug-in is not able to connect to the eisy at all.

As far as I know, it should work with the eisy, but it's possible that a recent firmware update breaks the plug-in. Does the plug-in log anything that might indicate what the problem is?

I like the Rainforest device a bit better than the Vue. I think it's more expensive, but they are bit more open with their API. Have you tried the Eagle 200 node server with it? The Eagle 200 is a Rainforest Automation device.

Thanks @Jimbo.Automates You're setting a good example for how node servers should behave.

PG3x uses another UDI component called UDX to authenticate. UDX does a bunch of system level tasks for the eisy (and Polisy) including the package upgrade process. Depending on what state the system is in, when UDX starts it may have a lot of work to do, my guess is that sometimes it is so busy doing other stuff (maybe trying to bring the system up-to-date) that it can't properly service PG3x's request for authentication. The result could be that the process seems to hang so that nothing happens when you click login or you get authentication failed as above. Once UDX is finished and is able to service the request, things start working. This is just my guess. UDX is mostly a black box to me, I don't know anything about it's internal workings. PG3x also had dependencies on a MQTT service and the IoX firmware so it could be something related to one of those as well.

Purchase the product and install it per the instructions that come with it. In my case, I had to contact the power company to get it setup with my meter. Install the Vue node server and configure it to communicate with the Vue device.

I just tried one of your queries and this is the response from WeatherBit

Just to explain a bit. The WeatherFlow hub sends the data via a UDP network broadcast. Without special router configurations, UDP broadcasts are limited to a single network subnet. Meaning the hub and the eisy/Polisy need to be on the same subnet for this to work. If it's not possible to have them on the same subnet, you can configure the node server to use remote data vs. local data. It will then query the WeatherFlow servers for the data instead. The trade off being that you're now dependent on the your external Internet connection for the weather data.

Thanks! I reviewed the log and see the problem, there's a bug in PG3. I've provided Michel with the steps needed to work around it so you should be good after the remote session.

Yes, there have been a lot of accuracy issues with the haptic rain sensor. To resolve that, WeatherFlow does a lot of server side processing/modeling to try and correct for that. That's the corrected rain value that they report in their app. I've not had a need for accurate rain info myself, so it hasn't been an issue for me, but I'd say that's one of the main weaknesses of the Tempest (the other, as @MrBill points out, is a high hardware failures). However, they are pretty good about replacing failed hardware.

This thread is probably not the right place to continue working your login issue. But if a reboot doesn't help, then you'll probably have to submit a ticket. It may be that something failed during an update and is now not working properly.

In general, once PG3(x) gets the access token, it will manage that and you won't ever be prompted to enter those credentials again. So the fact that you're not getting prompted probably means that it is working as intended. Lack of an access token is one reason why for it to not display purchased node servers so the steps above have been to try and make sure that's not the problem. Can you attempt to view your purchases (Refresh the listing or refresh the browser page) and then download the PG3 log? either PM me the log or attach it to the ticket. The log should have the reason why it's not able to get the purchase list.