kellerza

Please let me know which sensors you end up using. I'm not sure if "Peak shaving" or "grid always on" makes any sense https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions/single_phase.py#L246-L251

Today this sensor only exists in the 3-phase definitions - https://github.com/search?q=repo%3Akellerza%2Fsunsynk shaving&type=code Do you know the register? Try a custom sensor, and feel free to create a PR to add missing ones

I assume this is 3ph with these reg numbers? Can you write other sensors? Have you considered using something else than nodered, like my HA addon or the ESP32? With your current hw, it should be a no brained to get my addon working

I use essential_1_power & non-essential power. My load_power returns a value, but in your case might be that your "load" is wired to AUX.

It’s not a table, but these generally work well for Sunsynk/Deye and others https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py

Filter on total_grid_import?

The 3.6k, 5k and 8k single phase use the same registers. Deye, sunsynk, TurboE what are you trying to read that gives a timeout?

@Dariusz I'm not sure if these are applicable on the Sunsynk (I don't have them enabled). It was added for a Turbo Energy inverter - https://github.com/kellerza/sunsynk/issues/72#issuecomment-1335577324

Indeed, the inverter measures power frequently. These are used to update energy/kWh measurements (it has to be measured whenever the power changes!). So if you run a local solution like the addon, you can see changes per-second for immediate power usage. It's good to know that Sunsynk is typically measuring extra energy usage for export - since most people in SA gets penalised for this! I doubt measuring every second is enough, there are too many factors changing on a sub-second basis (the load, panel shading, mptt tracker, sampling rate on the CT sensor, maybe even some effect of hysteresis in the CT coil, slight voltage changes on the grid, speed at which these voltages changes are measured and factored into the measurement). If you know more about the external meter & inverter internals you could probably come up with a bigger list.

1. Read up on config packages here - config-packages 2. Save the code above in a "package" file 3. Add your elements to your HA dashboard If your inverter's mode (load_limit sensor) is set to "Zero export" and your inverter's CT sensor is working, then total_grid_import is very close. If you set load_limit to only essentials or to export then the inverter does not include the non-essential power draw. Why you should ask Sunsynk, but so far, they have told us to update the inverter firmware, without any success.

mbusd is lightweight with no dependencies on external libraries. Docker gives you very little/no benefits in this case. Trying to run a container built for HASS OS on another platform forces you to understand Docker, mbusd, and the way the HASS OS container was built to load your configuration etc. Which makes things more challenging. Just run mbusd natively, you will save yourself a lot of effort.

Did you try reading more often from your Solarman dongle? You should be able to do 15 seconds read/60seconds report - https://kellerza.github.io/sunsynk/reference/schedules#proposed-schedule-overrides-for-solarman With RS485 I read every 1/2 seconds and report every 60 seconds.

The SD card won't last long. In my setup I use an SSD and my write interval is only 60 seconds. The 2 second read interval is to ensure I can react quickly to significant changes in power.

The adaptor you have is perfectly fine,- it has a GND and some protection. Agree that, the native mbusd timing is far superior to what Python and Node V8 offers. I have mbusd running on a 10+ year old Pi Model 1b. The mbusd addon on HASS OS also works flawlessly. My production Pi-4(HA+SSD) + Pi-1b(mbusb) pulls data every 2 seconds, ~15m of RS485 bus and maybe 2 timeouts per day.

This is very good advice! The raspberry Pi PSU also floats somewhat, and since its not isolated it's important to wire the GND on the USB-RS485 adaptor (this is not the shield). In my setup I have non-shielded solid-core CAT5e (RS485 on one twisted PAIR !!) and GND. Around 15m with <1m in close proximity to the AC. The twisted pair helps, but if you have longer runs in close proximity to AC/DC then you must go shielded. The Waveshare USB adaptor I link in the docs has everything except optical isolation: Support USB to RS485 bidirectional conversion Onboard Original FT232RL and SP485EEN chip. Fast communication, stable and reliable, better compatibility Onboard TVS (Transient Voltage Suppressor), effectively suppress surge voltage and transient spike voltage in the circuit, lightningproof & anti-electrostatic Onboard resettable fuse and protection diodes, ensures the current/voltage stable outputs, provides over-current/over-voltage proof, improves shock proof performance

I doubt you have an issue with MQTT This clearly states the modbus interface is not responding, so no connection to the inverter. The addon will only connect to MQTT once it connected to the inverter and verified your serial number. As others also pointed out, this URL usually points to a Modbus gateway/mbusd add-on on your local homeassistant node. If this is not what you intended, you should rather connect to a USB port

I don't really have one to experiment with and everyone out there only integrates via the cloud (not ideal in my view)

@Dunc your port is wrong - it tried to connect to an IP on port 502. This is typically the port that the mbusd addon would expose, but no mention that you use it? Set the port to an empty string - "" then use the DEBUG_DEVICE to select the usb port

I did try to get some battery data from the sunsynk at a point, but those 600 regs were empty. Have not tried recently & my ide was to rather quesry the battery directly.

Try https://kellerza.github.io/sunsynk/reference/schedules#proposed-schedule-overrides-for-solarman Try those. YMMV depending on the amount of sensors you read. In this case less is better, else the dongle resets and disappears for a while

Thanks, glad you find it useful! Since you use sensor groups in your config (power_flow_card) https://kellerza.github.io/sunsynk/reference/definitions#power-flow-card-power-flow-card it includes several sensors. It seems like the names of the three-phase sensors do not match exactly, or these are not present in the three-phase inverter definition. Single phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions.py Three phase defs: https://github.com/kellerza/sunsynk/blob/main/src/sunsynk/definitions3ph.py Apparently the solarman dongle is quite temperamental. There is some improvement (using native errors correction) in the edge addon. I've also asked the pysolman authors what they recommend to make this more reliable. Probably best to open an issue, as its easier to track on Github than in a forum.

Use the raw register values and not the twos-complement. So not the negative number. Since 24612 is a smaller number it's pretty straight forward. 0x6024

Hex is your friend...

@Sc00bs with my addon, you can connect directly to your solarman dongle as well (not the new e-linter one) - you need a DONGLE_SERIAL_NUMBER and PORT: tcp://<local-ip>:8899 You should be able to read every 10 seconds - so probably need to supply less aggressive SCHEDULES than the default The author of the PR did write settings with it AFAIU. I must have a dongle somewhere around the house, will try test over the weekend.

If you do monitoring, you need two RS485 adaptors (for my addon & solar-assistant). Even for ESPHome based solution. Can't tell you specifically for solarman or e-linter.