bpwwer

I apologize for the lack of communication. This took us all by surprise. I believe it was a OS update that changed the Python version, not a change made specifically by UDI. Once we were aware of the issue, we were working just to understand the issue and come up with a fix. The latest upgrade should migrate all the Python based node servers to 3.9 in a controlled manner allowing them to install and run properly again.

Yes, it will charge you again. The current PG3 release treats every node server as unique, with a unique id. Thus even though it may be the same name in two different stores, they are treated as different node servers. The next release of PG3 will change this and allow the same node server ID to be used in different stores so you can purchase a non-production version and then use the same license to install the production version. But this change is still a ways off.

When the node server starts it queries AmbientWeather for information about your weather station(s). It appears that your network is not fully initialized and the query fails Query failed: HTTPSConnectionPool(host='api.ambientweather.net', port=443): Max retries exceeded with url: /v1/devices?applicationKey=7651edae3d7b44ee8ab5c3359b0c99469f30bf3d2a1d4f2c995b25d9c01a2cd3&apiKey=7407c4813e0f41f38be31752905a03377c3e1c41b3dd40b69f74fe4086fbebc8 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x8030f0970>: Failed to establish a new connection: [Errno 8] Name does not resolve')) It's failing because it can't resolve the name "api.ambientweather.net" to an IP address. It does re-try multiple times as you can see by the "Max retries exceeded" part of the message. There's nothing the node server can do to make name resolution work on your network while it's starting.

Yes, Python was updated. I believe the problem is that the new version of python conflicts with the old version so the old version gets removed. This is very bad for all the node servers written in python. Python uses the version number to determine where the third party libraries are installed. So what you're seeing is that the node servers start, but can't find any of the libraries they need. UDI is working on a fix.

I think that's probably about as good as it's going to get, at least for a while. I don't have time to try and reverse engineer the protocol differences in the controller you have right now. So I'm glad it is at least partially working as is.

The MagicHome API isn't documented so everything that works has been reverse engineered and there are still unknowns in the protocol. It looks like the flux_led project has figure out a lot more since the last time I looked at. I just added your device type to the list and set it up similar to another device. That could be completely wrong for your device. It is very possible that the animation speed settings are different for your device. For my devices, switching to another mode (like setting the on level to something) switches them out of effects mode. The devices I have support 3 modes, effects, white, and rgb. Setting the brightness level switches them to white mode. Node servers have no way to implement a color wheel control. Hue changes the color 0 = blue. Increasing will move the hue towards green, then red and finally back towards blue. The RGB level is the brightness level, this should effect all three (red, green, blue) leds equally. So rgb=100% and hue=17 should have been a shade of blue. But that assumes your devices work the same as the ones I have.

Version 1.0.3 should be in the store now, if you refresh the store you should see it. Then restarting the node server should automatically up date to version 1.0.3. Let me know if that work for the LED strip lights.

Thanks Kevin, No, don't buy another just to take it apart. I think that's enough info to add support for that type of device. I'll take a look at it soon.

By design. You could provide the bulb's manufacturer, model, and specs.

It doesn't recognize your bulbs so it doesn't know that they support changing levels.

It is being removed because it never gets installed on the ISY. It's failing to install because the install package is missing. I've uploaded the install package so it should install now. I've been working on major updates to the packaging and install process and apparently, I broke something and it never uploaded the package when I added it to the store.

Yes, the ISY will respond at <local address:8080> however, it does not have a default index.html page so unless you use a path it understands, it will just ignore the request. If you do something like: WEB/index.htm that will bring up the ISY's web interface.

It looks like you've tried a couple of different things, but the ISY configuration in PG3 isn't correct. When you do a Help -> About from the admin console you get something like this: What shows up for My URL is what you need to configure PG3's current ISY IP with. That will look something like: The ISY on Polisy (IoP) port number is 8080 (or 8443 for secure http) PG2's port number is 80 (or 443 for secure http) PG3's port number is 3000 For IoP, you should only use secure http (port 8443) if you have a valid SSL certificate, issued by a recognized certificate authority.

@4wireE&M Currently, the system has a number of different accounts/passwords none are linked so you have to manually get them all set, which can make the set up confusing. IoP has a username and password PG3 has a username and password Portal has a username and password. Those three accounts are independent but the components do have dependencies. When you configure PG3, you have to configure the ISY that it will communicate with. This is set in the PG3 ISY's -> Edit Current ISY menu. Make sure the proper IoP IP address, IoP username, and IoP password are configured here. If PG3 shows the Ecobee node server installed in one of it's slots, delete that and re-install it. If that doesn't work, post or send me via PM the PG3 log file (from PG3 menu Log->download log) And FYI, when using PG2 or PG3, those programs are what manages the node servers installed on the ISY. You won't need to use the Admin Console's Node Server menu to add nodes.

It will be in a future release.

@CoLongThanks for letting me know it's solved. Checking the IP address was going to be my next suggestion. Based on this issue, I've updated PG3 to do a better job of reporting errors in the log for this type of issue.

PG3 is not able to communicate with the ISY. The first thing I'd try is to reset the ISY password in PG3. Go to the ISY->Edit Current ISY menu in PG3. Enter the ISY password in the password field and save it. If that was the problem then all those errors being reported in the log should stop. When things are working right you won't see any of these: 6/20/2022, 15:59:17 [pg3] error: Error: GET http://192.168.1.116:8080/rest/ns/1/nodes/n001_controller/report/status/SPEED/19.0/48 Failed :: TypeError: Converting circular structure to JSON

There are no errors in the log, the node server appears to be functioning perfectly. Are there any errors in the PG3 log that would indicate that PG3 is having issues communicating with the ISY?

There's nothing in the log (and when set to info, there should be more). So that doesn't tell us anything. Try setting the log level to debug and restarting.

The MagicHome node server currently in the non-production node server store uses flux-led so would probably work.

Just for reference, there are PG3 node servers for other inverters already so it's certainly possible to create one for Sol-Ark. I believe all the existing node servers get data either from the inverter's cloud service or locally over the network. I'm not aware of any node servers that use an rs-232/USB link. You can use a USB hub with Policy if you need more than the 2 available ports. One issue will be that I don't believe node servers have permissions to access the USB ports so that's something that would need to be worked out with UDI to modify the Polisy configuration to allow that.

For PG3, (and even for PG2), the store is cloud based, it always has been. PG3 does make use of the cloud based services to enable more features. However, it is designed to minimize the need to connect to the cloud and to continue running if it fails to connect to the cloud. Features that are dependent on the cloud include the ability to handle subscription based node servers. This is mostly to cover the case where the subscription is about to expire and you renew it. In order to know that the subscription was renewed, it need to contact the portal. Node server updates. Again, to know if a new version of a node server is available, it needs to get updates from the store. It tries to query the store for these updates 3 times a day. When it does successfully query the store, it caches that info locally and will continue to use the locally cached info if it is unable to connect to the store. Similar to new versions, it is possible for node server developers to pass node server specific info to existing installations (think secret keys). During the periodic store queries, it will up date this data if it has changed. Lastly, to process payment for non-free node servers, PG3 must be able to contact the Portal. For free node server, no portal communication is needed. PG3 also uses your portal account info to determine if you are a registered developer and will enable additional features for developers. This doesn't affect non-developers. In theory (I haven't tested this, but if it doesn't work, it's a but) you should be able to refresh the store and then block PG3 from accessing the internet and everything will continue to work. You should be able to start/stop installed node servers and even install new free node servers. You will not be able to purchase node servers. Keep in mind that UI is connecting to PG3 on the Polisy over your local network. So if you unplug the Polisy from the network you won't be able to connect to PG3. But PG3 and node servers not dependent on the network interface should continue to run.

@johnnytYes, confirmed. PG3 supports installing the same node server multiple times and to multiple ISY's. Once you have purchased a license, it is tied the Polisy PG3 is running on. You can then install that node server as many times as you want, on to any ISY that that PG3 is connected to. You could potentially delete PG3 and all it's configuration from the Polisy, re-install it and the license will still be valid. What you can't do, is use that license on a different Polisy (hardware box). The reason the "Target ISY" is shown in the screen shot above is because that dialog box is used for both the purchase and install and when you install, you do so to a specific ISY.

I just changed my password about 5 times without any issues. If it's a database issue, it should show an error in the PG3 log.

Nothing in that log file indicates there's a problem. However, there are restrictions on what characters can be used for node names. It looks like that's the only node that has an '&' in the name so you might want to try removing that.