Solar Assistant: Local "Remote" Monitoring

The sunsynk.org Website and Sunsynk Connect app give me access to my inverter statistics and configuration. Unfortunately, this access goes via a remote server which seems to go down quite frequently. Additionally, the updates to the figures only happen every five minutes.

One way to solve this problem is a product called "Solar Assistant".

Solar Assistant is software which runs on a Raspberry Pi which is connected permanently to the RS-485 port on the inverter. The software monitors the inverter continuously and compiles statistics which you can view locally on a built-in web server that runs on the Pi. The Pi connects to your WiFI network.You can also make configuration changes via this web server or access it remotely when you are not at home on you home WiFi.

You can buy the Solar Assistant software and run it on your own Raspberry Pi, or you can buy a pre configured Pi from Solar Assistance in South Africa. They will also sell you pre-made RS-485 cables and a 48V power supply for the Pi (so that it can run from your batteries).

I chose to buy the ready-made solution from Solar Assistant. I figured that I was looking for a monitoring and control solution rather than another hobby! Another factor was that the money saved by configuring my own Raspberry Pi would not be very significant in the grand scheme of things (having just spent thousands on a SolarPV system). It took one week to come from South Africa. The shipping was a significan part of the cost but, fortunately, I did not get hit with additional duties or administrative charges.

Installation was simple. Turn off the inverter. Isolate all three supplies (AC, PV, Battery). Plug in the RS-485 Cable. Connect the power supply to the battery input terminals on the inverter. Power up. Configure the WiFi SSID and password.

The interface provides all of the functionality of the Sunsynk web site LOCALLY with the exception of software upgrading (which must still be done via the Sunsynk interface and requires Installer level access).

I will review the software in detail when I have had a chace to familiarise myself with it.

Comments

Post a Comment

Popular posts from this blog

Automation tasks underway

I have the following automation tasks underway, in various stages of completion: If there is a suitably inexpensive timeslot overnight, use it to top up the batteries to 100%. Using this, instead of solar, will allow more solar to be exported at 15p/kWh. Inexpensive slots during sunlight hours are not as useful because I can't export at the same time as using electricity from the grid. If there is not a suitably inexpensive timeslot overnight, top up the batteries from the grid during the period coming up to peak time (which is usually fairly reasonably priced). Make sure any battery charging from the grid is definitely off before the 4pm-7pm peak rate starts. When the electricity price goes negative, boost the hot water temperature using the heat pump and immersion heater. This is a way of benefitting from being PAID to use electricity and storing a little of it in the form of hot water. Change the colour of a lamp in the kitchen to reflect the current electricity
Read more

No, YAML ain't, but what is it?

YAML is said to stand for "YAML Ain't a Markup Language". This unhelpful acronym (and brazen use of the old "GNU = GNU is Not Unix" joke) doesn't really help in understanding YAML as it pertains to Home Assistant. Well, in this context, YAML is a way of defining the hierarchical configuration settings that drive Home Assistant. So, suppose we have some settings such as: Lights: Left: Brightness: 4 Colour: "Red" Right: Brightness: 6 Colour: "Green" Fans: Extractor: 2 YAML is just the thing to define such a hierarchical structure. For the moment, don't worry too much what these might represent. Consider, however, that we might want the actual settings (such as 4 or "Red") to be controlled by some variable quantity derived from something else within the system. In this case it would be useful to be able to replace the settings with snippets of Python code. And this is, effectively, what H
Read more

A new strategy, a new approach to automation

As I explained before, I was very wary of automating my system beyond what the inverter could do natively. As a retired elecronics and software engineer there is too much danger that such an endeavour would become a slippery slope. Well, I now have one foot on that slope! What prompted this change of heart? Well, during the last month we had some periods with VERY low Agile prices and it got me thinking about how I use my generated solar power. One way of looking at it is to look at the "opportunity cost" of the solar power generated. The incoming solar power, thanks to the sunk cost of the system, comes in at 0p/kWh. However, I can sell any excess back to Octopus at 15p/kWh. That means that, effectively, any solar that I use is costing me 15p/kWh - inasmuch as I could sell it if I want to. This way of thinking leads me to consider a different strategy: What if I were to charge my batteries on a cheap rate at night and, during the day, export most or all of my solar at 15
Read more