BYD HVS Batterie

BYD HVS Batterieabfragedaten

Aktueller Release
1.5.12
Entwickler
Christian
Lizenz
MIT

Captureing of messages

These messages and decrypted by capturing the communication between the software Be Connect and the hardware. The position and information of each information is interpreted by the community and may be incorrect. Please take only valid information from BYD or its sub-companies.

Messages

After a TCP Connection is estalished the communication requires to send a command to receive data or execute a measurement. The project of smarthomeNG describe it as a similarity for ModBus that we read and write registers with the TCP connection. https://github.com/lgb-this/plugins/blob/develop/byd_bat/user_doc.rst All Messages have a Header in Byte 1 and 2.

Message 0 - Initiate connection and Basic data

The send out message is 010300000066c5e0

ByteTypeDescription
3 to 21stringThis is the serialnumber. On the 2. character you can identify the hardwaretype (HVS, HVM, ...)
27 + 28characterVersion in format V(27).(28) for the first BMU
29 + 30characterVersion in format V(29).(30) for the 2nd BMU
33integerused tower BMU
362 seperate byte integer1 byte - towers; 2 byte - modules (23 => 2 towers & 3 modules)
38enum0: OffGrid; 1: OnGrid; 2: Backup

Message 1 - System diagnosis

The send out message is 01030500001984cc

ByteTypeDescriptio
3int16 signedSOC of the whole system
5int16 signedSystem max volts
7int16 signedSystem min volts
9int16 signedSystem SOH
11int16 signedSystem amperes
13int16 unsignedBattery volts with SF 100
15int16 signedmax Temperature
17int16 signedmin Temperature
19int16 signedBattery Temperature
29int16 signedError Number
31 + 32charactersParam T
35int16 unsignedOuput voltage with SF 100
37int16 unsignedTotal charge of the system
41int16 unsingedTotal discharge of the system

Message 2 - System diagnosis

the send command is 010300100003040e

ByteTypeDescriptio
3enuminverter type
5enumBattery type: 0: HVL; 1: HVM; 2: HVS

Message 5 - Tower basic information

ByteTypeDescriptio
5int16 signedTower max Volt
7int16 singedTower min Volt
9intmax volt cell number
10intmin volt cell number
11int16 signedmax temperature
13int 16 signedmin temperature
15intmax temperature cell
16intmin temperature cell number
17 - 32MSB, LSBBalancing Flags
33int32 Unsignedtower charge total with SF 1000
37int32 Unsignedtower discharge total with SF 1000
45int16 signedtower battery voltage SF 10
51int16 singedtower volt out
53int16 signedSOC Percentage
55int16 signedSOH percentage
57int16 signedCurrentamperes
59 + 60hexstate

Glossary

ShortDescription
SFScale Factor (Value 1234 & SF 100 => Real Value: 12.34)

Changelog

WORK IN PROGRESS

  • (copilot) Adapter requires node.js >= 22 now

1.5.12 (2026-05-01)

  • (arteck) fix exCode 0x04

1.5.11 (2026-04-26)

  • (arteck) del deprectated setStateAsync

1.5.10 (2026-04-26)

  • (arteck) fix Modbus Exception – fc=0x3 exCode=0x4 in State 7
  • (arteck) add Max retry attempts after error into settings

1.5.9 (2026-04-25)

  • (arteck) fix wrong package
  • (arteck) fix Modbus-RTU

1.5.8 (2026-04-23)

  • (arteck) typo

License

MIT License

Copyright (c) 2026 Christian github@familie-herrmann.de

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

SOFTWARE.