bpwwer

After uninstalling and re-installing I'm still getting Model SE7600A-USS20NHB2 is not yet supported Interestingly that's the older of the two models I have.

Yes, I've played around with the charts on the portal. I was really looking for real-time (at least every minute) info on battery charge/discharge rates that I can feed automatically to my database. While the charts are interesting, they're not real-time. I think the data only updates every 15 minutes and you have to regenerate the chart to see any updated data. I believe the API provides data updates every 5 minutes. It seems like the data should be available over the modbus, and that's probably how the battery communicates it's status to the inverter, but I haven't found any documents that indicate it's possible to access that data over the local network port.

Yup, I suspect the portal and the node server are using the same API calls to get the information. While I have the node server running, I'm not currently using it for anything. I am collecting data locally from the inverters and meter via modtcp and via an external meter. I dump this into a database and generate my own charts. The one things I'm missing is info on the battery. When the battery is charging, it looks like I'm not producing as much, but when the battery is discharging I see it as if I have PV production happening. So it works out in the end, but I was looking into the API to see if I could get some additional data on what's happening with the battery. There is access to a lot of different data vial the API but my understanding is that it's not real-time,

That's basically the system I have too. Two inverters with a battery connected to one of them. What I'm getting with this node server is a Site node which has an aggregate of the two inverters that has a single child node for the battery. However, I installed the node server after everything was installed. As a last resort you could delete the node server and re-install it.

I just pushed a new version that should fix this. Thanks for the report.

Thanks for the report Gary. Looks like WLL refused the connection for some reason, as it started working after the restart, I assume it must be a temporary failure. I added error trapping to the request so it shouldn't crash if it happens again.

Pushed an update that should trap the missing pressure value so it doesn't crash.

The OpenWeatherMap node server no longer works properly with Polyglot Cloud so I'm removing it from the store.

Step #4 was not necessary and may account for some of the issues you're having. Polyglot takes care of all interaction with the ISY, including adding nodes and setting up the node server configuration. Changing things like the ID and password will cause problems with the ISY/Polyglot communication. Given that it's difficult now to know what state everything is in, it may be best to delete everything and start over. Steps 1, 2, and 3 are all correct. After that your step 4 should have been to restart the Admin Console. Once the Admin Console is restarted, all the nodes should show up and start populating with data. Not all fields will necessarily have data, some like wind gust are optional and OpenWeatherMap may or may not send that data. You can try stopping and restarting the node server from the dashboard and then restarting the Admin Console and see if it all starts working, but depending on what you've changed, it may not work and deleting and re-installing would be the only solution. The logging level determines how much information is sent to the node server log file. Off means that almost nothing is sent to the log. You can change that via the drop down menu. All of the other weather service node servers are similar. They differ slightly in the data that they provide, the sources they collect data from, and the forecasting algorithms that they use.

Already did, thanks for the suggestion!

That's a good question and I agree with you about the quality of the documentation given that I'm responsible for a number of node servers with poor documentation. In my case, and I suspect others as well, because we aren't currently being compensated, it tends to be harder to justify the time for it. Having a reasonably good template for documentation and have it be a gate (I.E. done to some standard) before allowing something to be added to the store would help. I'm sure we'll get there eventually. In the meantime, if you see something you'd like better documented in any of my node servers, let me know. I'm always willing to add things to my todo list

Opera, just started happening yesterday for me too.

It looks like it should be reporting it. However, it only reports the reading to the ISY when it changes. If you look at the nodes in the polyglot dashboard. It's GV5 in the main controller node. Does that have a value that matches the data in the log? I think, because I tell the polyglot to only update the ISY when it changes, it's possible that upgrading the ISY, cleared the values in the ISY, but polyglot hasn't seen a change in the value so it hasn't sent an update. It works this way to reduce the load on the ISY. For a lot of my node servers I started forcing polyglot to send the values when the node server starts to as a way to work around this, but this one doesn't do that. I'll have to update it otherwise, you'll probably not see that update until you get more rain.

I've been following this because I'm going to have a SolarEdge inverter soon and would like to use this node server after it's installed. So I took a look at your log. I think the problem is the way that polyglot (and specifically the cloud version) is handling the parameter update. The node server doesn't get the updated value after you enter it. Try doing things in this order: 1) Install the node server 2) Enter the api_key parameter key and value. Save the changes 3) Stop the node server 4) Restart the node server 5) Check the admin console to verify the nodes exist. You should see a SolarEdge Controller node, a Quackenbush1 node with two subnode for battery. Since you already have the key entered (per screen shot), just start with step 3, stop and restart the node server and it should discover your inverter.

I just tried to clone a new node server I'm working on to the Polisy and got this error: sudo: unable to write to /var/run/sudo/ts/admin: No space left on device fatal: could not create work tree dir 'udi-weatherbit-poly': No space left on device A df of /var/polyglot shows [admin@polisy /var/polyglot/nodeservers]$ df . Filesystem 1K-blocks Used Avail Capacity Mounted on zudi/ROOT/default 5298048 5294859 3188 100% / Yes, the polyglot log file was huge and clearing it freed up about 45% of the space on the file system.

The problem is not knowing the mac-id and my router doesn't let me access the list of dynamic IP addresses it's handed out. I did have to use arp to get a list of mac-id/IP addresses and then go through the IP addresses one-by-one until I found the one assigned to the Polisy. Once I found it's IP and Mac-id, it was no problem to add it to the router with a IP reservation and then add it to my local DNS server.

Ok, so I tried something that I didn't think would work, and it didn't, but it also left the Polisy in a bit of strange state. I'm currently developing a node server on my RPi so it's not yet listed in the store, but is installed locally. I backed up the RPi Polyglot and then restored it on the Polisy. Polyglot thinks everything is fine. It lists the node server in the proper slot, says it's connected, all the configuration and node information is there. So from the GUI, it looks like everything is running just fine. However, the git repository is not present on the Polisy. Hence, I can't view the log and there is no node server process running. So even though it says it's connected, it obviously isn't. I did get this in the log: 2019-10-31 15:30:01 [polyglot] info: RESTORE: WeatherBit.io configured in slot 3 on ISY Sucessfully 2019-10-31 15:30:01 [polyglot] info: RESTORE: WeatherBit.io ISY Restored verifin g WeatherBit.io code installation... 2019-10-31 15:30:01 [polyglot] error: NodeServer WeatherBit.io not found in the store. Can't reinstall. 2019-10-31 15:30:01 [polyglot] info: RESTORE: Restore has been completed. Shutti ng down Polyglot in 5 seconds. It seems like the backup/restore should either include the git repositories or should actually fail to install the node server if it can't find it in the store.

How about adding vim so we can have a good version of vi.

So what's the recommended way to remove these node servers? Can I just delete them from the database I.E. db.nodeservers.remove({'name': 'SolarEdge'})?

@Michel Kohanim, I wouldn't say my network is complex, in fact, probably the opposite. My router is quite old and its DHCP support is pretty basic. When I add devices to my network, I also add a DHCP reservation and manually update my DNS. I need the MAC address to create the reservation. I do have a range of IP's that get assigned if no reservation exist for the device so they work. Many devices include the MAC address on the packaging and I find that helpful. This was just a small issue. If it's not possible to provide the MAC address in the packaging, it's not a big deal. Now that power just came back on, I'll have a chance to play around with it some more.

I only got to play with mine very briefly before the power went out (PG&E). The only issue I had was finding the IP address it was assigned. The DHCP server on my router doesn't provide any information on the leases it hands out so I had to work through the list of currently active leases to find the right one. Knowing the MAC address before hooking it up would have been a big help.

I can understand your confusion as something has gone wrong. Your understanding of should have happened appears correct. 1) Polyglot cloud is supposed to install the node server to the ISY and create the nodes there. Based on your screen shots, that never happened. There may information in the DarkSky node server log to explain why. Without more information, I can't even make a guess as to why it failed. Have you restarted the admin console since installing the node server? The admin console does need to be restarted as some of the installed node server files are only read when the admin console is started. 2) I believe you should be able to delete any duplicate configuration entries. But they shouldn't cause any issues and if the nodes display from the Polyglot dashboard looks like it's updating the data, then, yes, it is correctly configured. I'm not sure why you had to re-enter the configuration multiple times, that's not normal. 3) Someone with more knowledge of how Polyglot cloud works will probably have to help here. Those buttons should be doing what they say. Again, checking the log may provide some additional information. 4) This seems to be tied to #3, but I'm not sure. Based on your screen shots, it looks like you're only running one instance of the node server. EDIT 2) It is possible to confuse Polygot as it doesn't always do a good job of cleaning things up when something goes wrong. I know I've had my local Polyglot database get into corrupted states that make working with it difficult until it's manually cleaned up. But I have no idea if that's possible with Polyglot cloud, or how you'd clean it up if it does happen.

Ah, that makes more sense now. For some reason I was thinking that rain size had something to do with the size of the raindrops. Since the rain data is reported as bucket tips, I should be using this to do the calculations instead of a fixed 0.01 inches. I'll make that change and switch out the rain size on the display as well. Thanks!

@Jim Unroe You're welcome. Did you get any soil sensors? I'm curious to know if that part of the node server works.

The WeatherLink node server is now available in the node server store.