Bluesun inverter ModBUS register list

[neofral]

Is your feature request related to a problem?

No

Describe the solution you'd like

Trying to use the integration for Bluesun hybrid inverter. My inverter model is BSE15KH3. I would very much appreciate if somebody shared the register file. I got one from Bluesun but is very old and most of the registers are not correct. I will contribute by sharing the yaml file (after tested) so it's accessible for other users.

Describe alternatives you've considered

Waiting from Bluesun to provide correct file with ModBUS registers

edit: typo

[neofral]

@davidrapan , where can i send you an email with the files and explanation?

[davidrapan]

You can upload it right here. 😉 Just drag and drop the file in the textbox. 😉

[neofral]

old file not showing all correct data, especially the battery. thought was the wrong and asked new file...
google sheets file:
https://docs.google.com/spreadsheets/d/1hLhIKdW9gyouqYl-kxwpdWvRxji5lwPeI-_4htfawfA/edit?usp=sharing

new file, not working giving error loading device
RS485_MODBUS(ESINV-33000ID) Hybrid Inverter.pdf

[davidrapan]

How does your yaml look like currently?

[neofral]

oh constantly working on it. trying the google sheets one. i will post a stable one as soon as i can

[neofral]

connection not stable. disconnecting after a while.
how can i turn on the logger and where to find it?

[davidrapan]

[neofral]

bluesun.txt

this is a stable working file.

need help:
with the double register values
with parsing the state registers

[neofral]

disconnecting often after adding more sensors

here is part of the log:
2024-11-06 15:36:11.252 DEBUG (MainThread) [custom_components.solarman.api] [3514351914] Fetching failed. [Previous State: Disconnected (-1)] 2024-11-06 15:36:11.252 INFO (MainThread) [custom_components.solarman.api] [3514351914] Disconnecting from 10.10.100.254:8899 2024-11-06 15:36:11.256 DEBUG (MainThread) [custom_components.solarman.coordinator] async_shutdown 2024-11-06 15:36:11.256 INFO (MainThread) [custom_components.solarman.api] [3514351914] Disconnecting from 10.10.100.254:8899 2024-11-06 15:36:16.495 DEBUG (MainThread) [custom_components.solarman] async_setup_entry({'created_at': '2024-11-06T12:18:06.318019+00:00', 'data': {'name': 'Bluesun', 'inverter_serial': 3514351914, 'inverter_host': '10.10.100.254', 'inverter_port': 8899, 'inverter_mb_slave_id': 1, 'lookup_file': 'bluesun.yaml', 'battery_nominal_voltage': 48, 'battery_life_cycle_rating': 6000}, 'discovery_keys': {}, 'disabled_by': None, 'domain': 'solarman', 'entry_id': '01JC0PJ7BD713PPG8C0F4P4PCA', 'minor_version': 1, 'modified_at': '2024-11-06T12:18:06.318025+00:00', 'options': {'name': 'Bluesun', 'inverter_serial': 3514351914, 'inverter_host': '10.10.100.254', 'inverter_port': 8899, 'inverter_mb_slave_id': 1, 'lookup_file': 'bluesun.yaml', 'battery_nominal_voltage': 48, 'battery_life_cycle_rating': 6000}, 'pref_disable_new_entities': False, 'pref_disable_polling': False, 'source': 'user', 'title': 'Bluesun', 'unique_id': 'solarman_3514351914', 'version': 1}) 2024-11-06 15:36:16.496 DEBUG (MainThread) [custom_components.solarman.discovery] discover 2024-11-06 15:36:16.496 DEBUG (MainThread) [custom_components.solarman.discovery] _discover_all: Broadcasting on 10.10.100.254 2024-11-06 15:36:16.496 DEBUG (MainThread) [custom_components.solarman.discovery] _discover 2024-11-06 15:36:16.515 DEBUG (MainThread) [custom_components.solarman.discovery] _discover: [10.10.100.254, 402A8F4A4A76, 3514351914] 2024-11-06 15:36:16.544 DEBUG (MainThread) [custom_components.solarman.parser] Defaults for update_interval: 30, code: 3, min_span: 25, max_size: 125, digits: 6 2024-11-06 15:36:16.544 DEBUG (MainThread) [custom_components.solarman.api] {'connections': {('mac', '40:2a:8f:4a:4a:76')}, 'identifiers': {('solarman', 3514351914)}, 'serial_number': 3514351914, 'manufacturer': 'Solarman', 'model': 'Stick Logger', 'name': 'Bluesun'} 2024-11-06 15:36:16.544 DEBUG (MainThread) [custom_components.solarman] async_setup: coordinator.async_config_entry_first_refresh 2024-11-06 15:36:16.544 DEBUG (MainThread) [custom_components.solarman.api] [3514351914] Scheduling 2 query requests. #0 2024-11-06 15:36:16.544 DEBUG (MainThread) [custom_components.solarman.api] [3514351914] Querying 04 ~ 0530 - 0560 | 0x0212 - 0x0230 # 031 ... 2024-11-06 15:36:16.544 INFO (MainThread) [custom_components.solarman.api] [3514351914] Connecting to 10.10.100.254:8899 2024-11-06 15:36:16.547 DEBUG (MainThread) [custom_components.solarman.api] [3514351914] SENT: a5 17 00 10 45 75 00 2a c1 78 d1 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 04 02 12 00 1f 10 7f de 15

[davidrapan]

You cut it off (the log ends) just before it could reveal any information.

Edit: Rather upload it as a file. It's better.

[neofral]

home-assistant.log

[davidrapan]

Something really strange is going on here...

Is connection between HA and inverter at least somewhat semi-good? Because the connection timeouts very often.

[neofral]

i'm using mini-pc with HA operating system. using the wifi of the pc to connect to the wifi dongle AP.

they're right next to each other.

the wifi dongle is connecting to solarman platform via router that is about 4 meters away with signal quality 98%

[neofral]

maybe the query time of 30sec is too often, i'll try 60 sec and see what happens

[davidrapan]

maybe the query time of 30sec is too often, I'll try 60 sec and see what happens

No, that's not it.

[neofral]

i was also trying modbus board with esphome connected to another comm port of the inverter trying it out.
i disconnected that device. since we got it working this way, i don't think i need that one.
let's focus and keep the connection stable.

however, i have to mention that the inverter was also disonnecting from solarman platform. i do a restart of the dongle via the webpage and it's back on.

but i'm crazy how rare is the upload interval between inverter and the solarman webpage

[davidrapan]

however, i have to mention that the inverter was also disonnecting from solarman platform. i do a restart of the dongle via the webpage and it's back on.

but i'm crazy how rare is the upload interval between inverter and the solarman webpage

This really could indicate some problems with/on your network, imo..

[neofral]

why am not able to connect via the dongle's lan ip address and not use the dongl AP?
anything settings that i've missed?

[davidrapan]

I really don't think you can turn web off so it looks like the stick is just unresponsive.

[neofral]

well what do you know. my mikrotik router had the upnp disabled by default. i presume the stick uses it to open ports and since it failed was behaving strangely.

just enabled upnp, reverted to 30sec update interval, and finally got connected through the lan ip address of the stick

[davidrapan]

well what do you know. my mikrotik router had the upnp disabled by default. i presume the stick uses it to open ports and since it failed was behaving strangely.

I don't think it should be like turning it on and off again repeatedly? But who knows... nothing surprises me anymore (after working on this integration)

just enabled upnp, reverted to 30sec update interval, and finally got connected through the lan ip address of the stick

Yeah it should handle even once a second updates. (5 seconds is the lowest possible w/ integrations though)

[neofral]

disconnected again. not a full hour working... any ideas?
edit: definitely its an issue with the stick. just restarted it via the page and the sensors up and running immediately

[davidrapan]

Run it with enabled debug logging from the time of the restart of the stick until it stops working again. Maybe the transition will reveal something.

[neofral]

home-assistant (1).log

[neofral]

do you know why the sensors are not showing in groups?

[davidrapan]

do you know why the sensors are not showing in groups?

That's not their purpose. It's only for profile configuration. You can set update_interval and code for groups.

[neofral]

did a new setup with the wizard on the stick. disabled/hided the AP now no clients connecting on it.
another issue i might have is that i have a lot of switches and sensors using esp8266 and esp32 devices . i have 4 access points and about 60 wifi/lan clients. i'd say that the wifi is quite congested maybe the stick doesn't like the environment.

it's been running stable for more than 3 hours now.

by the way you have to give contact, let's see how we can cooperate

[davidrapan]

it's been running stable for more than 3 hours now.

That sounds promising!

[neofral]

update: very stable and working.
moving on with setting variables.
@davidrapan, need help with time addresses

<style> </style>

√	AC charging start time 1	TimeOnAcChg1	2509	U16	2	H:0-23 M:0-59
√	AC charging end time 1	TimeOffAcChg1	2510	U16	2	H:0-23 M:0-59

tried this:

  - name: AC Charge Time 1 Start
    platform: time
    rule: 9
    code:
      read: 0x03
      write: 0x06
    registers: [2509]

when i set hour 0, is ok. above 1 i get response

[davidrapan]

fix: Enum class & Select platform dictionary default

And tell me which entities (registers) are you missing in that afore_hybrid.yaml profile so I can add them.

[neofral]

fix: Enum class & Select platform dictionary default

this did enable the device load, but now reading incorrectly the state of this feature.
timing AC charge is on, the feature is reading it off. i will even try to change it.
every time the inverter shuts down, i lose power to the house since all my house is now connected to the EPS power outlet of the inverter.

[neofral]

as far as i am concerned, i am very happy and greatly thankful for your integration and the great work you put in maintaining it.

after the resolution of the reading and writing the registers with the times, i have created many automations:

• automations depending weather conditions to change charging power and min/max states.
• changing Ban discharge times for days that we have low cost electricity, i can control the battery not to charge and be used
  unnecessarily.
• charge power depending on battery state and the available time of low tariff for the 2nd cycle
• etc.

therefore, if you decide to close this issue - please do.
i will be available to share any automations and helpers i created for a sophisticated utilization of the battery

if you want you can keep the thread open and i can periodically check it and provide active support for any additional testing that you might need.

p.s.: i'm out for tonight, got early morning tasks. again, thank you very much.

[davidrapan]

fix: Enum class & Select platform dictionary default

[neofral]

did you change any other file?
i implemented this change and the status still doesn't read correctly.
feature is On, on the integration is read off

[davidrapan]

Specifically, I tested it on my installation and it worked, guess something strange must be happening in your case.

Open parser.py and add (not replace) this line on the row number 116:

if "bit" in o:
    _LOGGER.warning(f"{from_bit_index(o["bit"])} == {value}: {from_bit_index(o["bit"]) == value}")

So the row which is originally on the row number 116 moves to 118.

Restart HA and show me what's in the log.

[neofral]

is this ok?

[neofral]

tried with this code:

  - name: "Timing AC Charge"
    platform: select
    registers: [0x00CE, 0x00CF]
    code:
      read: 0x03
    rule: 1
    icon: "mdi:home-lightning-bolt"
    lookup:
      - key: 0
        value: "Off"
      - bit: 0
        value: "On"
      - bit: [0, 4]
        value: "Timing AC ChargeEnable"

result:

[davidrapan]

is this ok?

Yes.

tried with this code:

Could be wrong order of registers.

Code edit just added additional logging, so what's in the log?

[neofral]

tried the registers order too.
this is the log
home-assistant_solarman_2024-11-28T18-26-59.877Z.log

[davidrapan]

I don't see those messages in there, You probably made a mistake somewhere.

BTW, As I said before already, your file contains many errors as seen here (long term statistics won't work, etc.):

MainThread) [custom_components.solarman.sensor] async_setup: async_add_entities
2024-11-28 19:26:56.875 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_pvt_total_power (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.876 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_pvt_total_power_day (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.879 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_pvt_total_power_all (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.880 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_state (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('enum') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.881 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_voltage (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using native unit of measurement 'V' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.881 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_current (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using native unit of measurement 'A' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.882 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_daily_charge (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.882 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_daily_discharge (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.882 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_total_charge (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues
2024-11-28 19:26:56.883 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.bluesun_battery_total_discharge (<class 'custom_components.solarman.sensor.SolarmanSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/davidrapan/ha-solarman/issues

[neofral]

bluesun2.txt

i fixed the file for the "total" as you suggested. i'll look into the other things

[neofral]

i just loaded the device with afore_hybrid.yaml
the work mode shows the same. didn't try the register order though

[davidrapan]

I need to see output in the log of that code change we did few moments ago. Did you restart HA?

[neofral]

home-assistant_solarman_2024-11-28T19-03-00.796Z.log
yes, i restarted. just didn't change the order of the registers. i needed the device back online with my file since i need the entities

[davidrapan]

I would advise you to switch from your file and change your dashboards, automations and template sensors to use this default profile, it will be way easier for you. And not just now but in the future too. 😉

[neofral]

nope sry, too late now. i need the long term entity records. will use the data to show the benefits of using battery compared to just solar.
i need to this data to calculate savings and who this to customers

[davidrapan]

nope sry, too late now. i need the long term entity records.

Your history is messed up already anyway, because of those errors in your file. 😉 You are using this for like 2 weeks tops, so it's no history, I wouldn't call it too late at all. There is a guide in Discussions how to transfer/merge history under different names. But sure it's up to you.

Anyway inverter is currently set to 5308417, which translates as (set bits):

• B0:switch machine: inverter is on
• B16:Timing Forbid discharge enable: is on
• B20:DisselGenFunction: is on
• B22: is on

You need to add additional options:

      - bit: [0, 4, 16, 20, 22]
        value: "Time of Use & Forbid Discharge & Generator & B22"
      - bit: [0, 16, 20, 22]
        value: "Forbid Discharge & Generator & B22"

[neofral]

yes, my el. invoice period is on the 12th of the month. these too weeks are very valuable to me, can't wait for the next invoice...
i think this algebraic calculation of import/export will ruin my calculations.
i have custom sensors calculating positive and negative values for each phase.

i also took your advice and set the export to 100w.
let's see how it goes.

however, you could make possible that we could load as second device with the other file and have them both 😉
edit: i could just use the missing entities on the other device, and we are both happy 😉

[davidrapan]

i think this algebraic calculation of import/export will ruin my calculations.
i have custom sensors calculating positive and negative values for each phase.

I don't know what you mean by that. And sure it can be valuable insight if you have phases and their consumption somewhat logically separated.

i also took your advice and set the export to 100w.

It really depends on how is electricity billed in your region. So make sure it's good for your case.

however, you could make possible that we could load as second device

I think it would just create unnecessarily communication overhead with the logger. But you can overcome the limitation of 1 serial number = 1 device by creating device with some made up serial number and then proceed with manual edit of the entry of newly added device in /homeassistant/.storage/core.config_entries and change inverter_serial item.

It's not about me being happy. I'm just trying to help you. 😉

[neofral]

i think this algebraic calculation of import/export will ruin my calculations.
i have custom sensors calculating positive and negative values for each phase.

I don't know what you mean by that. And sure it can be valuable insight if you have phases and their consumption somewhat logically separated.

i also took your advice and set the export to 100w.

It really depends on how is electricity billed in your region. So make sure it's good for your case.

however, you could make possible that we could load as second device

As i could ready from that page where you suggest this, it seems our countries have the same type of meter. A pulse counting meter that reads pulses generated when electricity is flowing. I understand this as whatever the flow of electricity, pulses are generated and counted.
The tech. support of BlueSun somehow thinks that some European countries have "algebraic total" of phases. Meaning, if you export some electricity while importing some - if the algebraic sum of positive and negative is near 0 - than you don't pay.
Personally, i think they are totally wrong. How wrong, i will know in about 2 weeks.
That's why i need my sensors to store data until billing period finishes and i get the invoice so i can raise another issue with them. they offered that if necessary, they can add additional features for the inverter firmware.
This is also important why we must keep the file separated (clearly identify that is for BlueSun), correctly identify model and i guess firmware versions too since there will be additional features added to the inverter.
I'm really positively surprised with their tech. support and let's see how it goes.

[davidrapan]

some European countries have "algebraic total" of phases

Yes. Germany for example (as stated in our wiki), more info: Smart meter reading method v1r0A 20170622.pdf

This is also important why we must keep the file separated

I really don't think so and the plan for the future is to get rid of the files completely anyway. 😉

[neofral]

some European countries have "algebraic total" of phases

Yes. Germany for example (as stated in our wiki), more info: Smart meter reading method v1r0A 20170622.pdf

Yes, exactly. This document even questions the operation of a "smart" meter.
In my country you can't report a system and can't get a bi-directional smart meter with inverters higher than 6 KW or max PV capacity <6 KW (max 5.99KW).
So, if you have larger system you're stuck with consumption only. Therefore, you're stuck with an old meter which is not bi-directional nor smart.

[davidrapan]

This energy distribution mafia is p*ssing me of too... Even so, we don't have it THAT strict, but what can you do, right?

[neofral]

As a businessman, it's my job to find solutions to "limitations".
That's why i'm trying so hard to log data and use as "proof" that there are solutions to some of the "limitations".
And i have to mention again how happy i am with Bluesun tech. support.

This "mafia" in our country has 4 blocks of high tariffs. Each block is significantly with higher price.

I estimate that with 15kw inverter and 30kw of batteries, a large house with heat-pump can escape the high tariffs and remain only in the low tariff.
I will make a public Grafana dashboard next month and launch a local marketing campaign.

[davidrapan]

That sounds briliant!

May I ask you for your current power and distribution prices in both tarts?

Edit: Can you please help me with something? I would like to know how unique_id looks like for entities under solarman integration. Do you know where to look?

[neofral]

That sounds briliant!

May I ask you for your current power and distribution prices in both tarts?

Edit: Can you please help me with something? I would like to know how unique_id looks like for entities under solarman integration. Do you know where to look?

sry, been away for a few days. you still need help?
official prices in North Macedonia:
https://www.erc.org.mk/page_en.aspx?id=287

High Tariff 1 ( ~180 kw): 0.1253850732 E/KW
High Tariff 2 (next 460kw): 0.146575187 E/KW
High Tariff 3 (next 460kw): 0.1802023089 E/KW
High Tariff 4 (above 1080kw): 0.3836746016 E/KW
Low Tariff (currently no limit to qty): 0.07831362602 E/KW

[davidrapan]

You have it tiered by total consumption?!? WTF!

BUT, yeah... I guess it's probably always necessary to look at it from a bigger perspective because the state of the network has the most to say here and maybe it's needed for grid stability (Incentivizes saving, etc.). But then the prices aren't THAT BAD, but not the best either, on the other hand I'm pretty sure the situation in most places in the EU is currently worse on average.