bpwwer

PG3x doesn't know the internet connection was off-line so it can't detect that situation. It doesn't know why the nodes servers failed, just that they have. The problem is with specific node servers. Some don't handle the internet disconnect well others do.

Oops you must not have the updated firmware. 1.0.3 should handle that correctly now.

You should be able to restart the node servers without having to restart PG3x. However, PG3x won't try to restart them automatically. The "failed" state means that the node server failed and disconnected from PG3x unexpectedly. In your case, the node servers are likely crashing when they get disconnected from the internet. Most are not designed to recover gracefully when that happens. This is something that would have to be fixed in each of node servers.

Sorry about that, I didn't realize that the change I made would also effect the code. It should be fixed now in 1.0.2

@BamBamF16 Have you tried starting the node servers? If they don't start, download the PG3 log package and PM it to me.

I can't do anything about #1, that is a limitation of what the IoX will accept for node names. I can fix #2. I'll change it so that it looks like: This also changes the drop down so that the options are "Set Shade Position" and "Set Shade Speed" instead of both being just "Set Shade".

Run "Upgrade Packages" again. Once it completes, reboot. Once everything is back up, refresh the browser page.

@JKlinefelter That makes sense but I'm not sure how the node server can detect that from the incoming data. The incoming data has field names suffixed with 1, 2, 3, etc. The channel number I guess. So the node server lumps everything with a suffix of '1' under a single node. There's no indication in the data that it may be multiple sensors or a single sensor. The IoX considers it illegal to have two node values of the same type. So what's happening is that when there are 2 sensors with a suffix of '1', they both may be reporting battery status, but since the node can only have one battery status it the node server creates an illegal node definition and the IoX rejects it. Because there can be so many different combinations of stations/sensors and Ambient doesn't send anything but a list of field names/values, the node server has no way to know what sensors/values are going to be reported ahead of time, it has to process that in real-time and dynamically create nodes based on what it sees. I don't really have any ideas for a better way to handle this. It seems like trying to do any type of user configuration would be a real challenge given the limitations of the PG3 configuration screen. The right solution would be for Ambient to re-design their data structure format to provide the info needed actually parse it. I can try and improve the parsing logic in the node server, but it is already quite complex because the field naming conventions aren't all that consistent. Anything I do will end up making assumptions that may or may not hold in the future and may simply result in dropping data if it thinks it will create illegal nodes. Since I don't have any Ambient equipment and I haven't seen it documented anywhere, I had no idea the suffix numbers represented channels.

No difference between Polisy and eisy that I'm aware of. But that's not a PG3 issue as the IoX handles the upgrade process so you might want to ask this on the IoX firmware support thread.

I don't believe so. But you can install the node server in multiple slots with each using a different gateway.

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?