Jump to content

Bloubul7

Members
  • Posts

    246
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Bloubul7

  1. I will share my Node Red flows to do this over the weekend. Currently in Germany and don't have access to my server
  2. What I have done is to set up different timetables in Node Red variables. When loadshedding is detected through the API (eskomsepush) then a flow would change the battery charge points in relation to the set timetables. Different settings set up for different loadshedding stages.
  3. You need to change the device/ unit ID on the inverter to 1
  4. Not that I know off directly from the monitoring side. You could try a mix between using the forecast solar from solcast and then turning on a high draw appliance for a period with some node red logic
  5. Awesome, Just an explanation on the other menus: System Settings: Reads the settings that is currently applied on the inverter. You can change settings and write it back to the inverter Default Settings: This save your default settings (typically used) to the local storage LoadShedding Settings: This save a second set of settings (to be used when there is loadshedding) to the local storage. The flow checks a website to see if loadshedding is currently active. If not active it applies the "Default settings" to the inverter, if loadshedding is active then it applies the load shedding settings. I use this flow to preserve the battery capacity during loadshedding times, our area used to be load shedded 4 hours at a time.
  6. See below screenshots from the Node Red Dashboard. These flows are active as part of the flows shared. On the Time mode screen you can select the time and days when the inverter should switch to limit to load only. Make sure to press the buttons next to the timer to set these times.
  7. You shouldn't need to alter the flows, the flow as it is should work for your current needs. I will post a screenshot of the user interface tonight when I'm at home
  8. You can access the dashboard by going to http://ipaddress:1880/ui
  9. Did you try and change it through the dashboard?
  10. Hi, Yes it is part of the Node Red flows that I have shared previously. I have my limit to load enabled to different days and different times of days
  11. Hi, The dashboard should be available at http://noderedip:1880/ui If you want to safe the settings to a local storage file then you would need to enable context storage in your settings.js
  12. Based on the above the flow is definitely communicating with the inverter. Check your MQTT settings on HA.
  13. Have you checked that the OS is seeing your RS485 converter as per the below post? Then cross check the port on which it is assigned against your Node Red assignment?
  14. I'm assuming that you are running HA OS. Can you see your device when it is plugged in? Check under configuration - Addons/ backups/ supervisor - Host - Hardware
  15. On a different note. Your CT Coil appears to be in the incorrect place. It should be in your Main DB on the incoming supply line. Secondly I see that you are not using the ATS ports in which case I would assume you don't have a relay for N-E bonding. Please check it out, a floating neutral during islanding mode can be dangerous.
  16. My RS485 polls the modbus every 0.2 seconds. Values are updated every 2 seconds
  17. Please post a picture of your board. The board should have a RS485 and CAN port, what most of us did was to use the RS485 port for the inverter monitoring and the CAN port for communication with the BMS
  18. Just a note, but you need to measure it twice (with Eskom power on and with Eskom power off)
  19. Because it is illegal to have a second permanent earth neutral bond. SANS requires a separate bond to be created only when the system is in islanding mode.
  20. Your sparky is correct in a situation when Eskom power is available, however when you loose Eskom power then you loose earth bonding. Hence the need for a relay to bond neutral and earth when in islanding mode
  21. I would recommend option 2 with Raspberry PI OS lite. As a 3rd option you can also look at using USR-W630 Modbus RTU at the inverter side. Home Assistant has the modbus protocol built in and you can poll the modbus addresses directly from HA. USR-W630 Industrial Serial to WiFi and Ethernet Converter Supports 2 E – Reliable Store
  22. That is weird, but I'm still on the old firmware. Haven't upgraded as yet. What I have noticed though is that when I can the value of register 243 via Node Red is that the tick on the Inverter screen doesn't go on, but through the inverter monitoring I can see that the inverter's behaviour has changed.
  23. Disable Priority Load. With Priority load enabled all of your solar generation will go towards the batteries until they reach full charge
×
×
  • Create New...