Solar PV Monitoring/Automation Thread

I have these defined in my code already in registers.py file and puliing all that data.

https://github.com/NosIreland/solismon3

I had this too, and the reason was that the firmware on the solis wifi stick was too old.

I spoke to my installer and he go onto solis and they performed the update, that fixed it.

Try that

Guys I have this thing happening that is driving me crazy. I am pulling a few solis register via python and pymodbusv5 method, however everytime I restart home assistant it breaks all of those value by adding wrong data from yesterday and I have no idea how to fix that.

See these little spikes:

This breaks the energy dashboard values basically and I have to go in sql and fix that which is getting old fast.

See below for the code, it ain't pretty but I'm still testing it out for now:

""" A basic client demonstrating how to use pysolarmanv5."""
from pysolarmanv5.pysolarmanv5 import PySolarmanV5
from paho.mqtt import client as mqtt_client
import time


class Register:
  def __init__(self, number, quantity, scale, topic, haName):
    self.number = number
    self.quantity = quantity
    self.scale = scale
    self.topic = topic
    self.haName = haName

broker = '192.168.0.100'
port = 1883
topic = "home/solar/consumption/today_energy"
client_id = 'solis_test'
username = 'homeassistant'
password = 'xxx' 


def connect_mqtt():
    def on_connect(client, userdata, flags, rc):
        if rc == 0:
            print("Connected to MQTT Broker!")
        else:
            print("Failed to connect, return code %d\n", rc)
    # Set Connecting Client ID
    client = mqtt_client.Client(client_id)
    client.username_pw_set(username, password)
    client.on_connect = on_connect
    client.connect(broker, port)
    return client


def publish(client):
    msg_count = 0
    modbus = PySolarmanV5(
        "192.168.0.200", 12345678, port=8899, mb_slave_id=1, verbose=1
    )
    
    registers = []
    registers.append(Register(33163, 1, 0.1, 'home/solar/battery/charged_today', 'Solar Battery Charged Today'))
    registers.append(Register(33167, 1, 0.1, 'home/solar/battery/discharged_today', 'Solar Battery Discharged Today'))
    registers.append(Register(33179, 1, 0.1, 'home/solar/consumption/today_energy', 'Energy Consumption Today'))
    registers.append(Register(33171, 1, 0.1, 'home/solar/grid/today_import', 'Grid Import Today'))
    registers.append(Register(33175, 1, 0.1, 'home/solar/grid/today_export', 'Grid Export Today'))


    for reg in registers:
        #"""Query single input register, result as an int"""
        #print(modbus.read_input_register_formatted(register_addr=reg.number, quantity=reg.quantity, scale=reg.scale))
        register = modbus.read_input_register_formatted(register_addr=reg.number, quantity=reg.quantity, scale=reg.scale)
        if(reg.scale == 0.1):
            msg = format(register, '.1f')
        else:
            msg = format(register, '.0f')
        result = client.publish(reg.topic, msg)
        # result: [0, 1]
        status = result[0]
        if status == 0:
            print(f"Send `{msg}` to topic `{topic}`")
        else:
            print(f"Failed to send message to topic {topic}")
        msg_count += 1


def run():
    client = connect_mqtt()
    client.loop_start()
    publish(client)    


if __name__ == "__main__":
    run()    

It happens like clockwork on every restart of the HA server

Baffling as to why it happens, I had turned off my other nodered mqtt stuff just in case it was affecting it and I still saw it after restart.

I do know that this only happens when I have the python script running and not when pulling data from nodered and solis cloud.

Not sure where those mqtt values are lingering, any suggestions where to track it on HA side?

I just noticed this in mqtt explorer:

These are the dodgy values (from yesterday) and every time I open mqtt explorer I see the wrong values until the update comes from the python script, strange AF

I worked it out at 1am last night 😂

It was the RETAIN being set to TRUE on my nodered stuff but not on the python side, so whenever a new client would connect it would send that old value it had until a new came in

Once I set it to true on python side it stopped doing it. I knew it was something silly.

SolarEdge and SolaX are super easy, can be done without manual MODBUS / RS485 hacking.

I run it in a docker container on a vanilla Ubuntu install. Easy to update.

Yeah using an rpi4 with an SSD here and daily backups to google drive, nothing to lose that way.

Or you could go with the HA amber official kits https://www.crowdsupply.com/nabu-casa/home-assistant-yellow

I think you can get them with the cm4 included.

I used this https://rpilocator.com/ to source some pi zero 2s recently, just follow them on twitter and be ready to jump once you get the notifications.