Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
Ok, i had make it on windows 10.
Monitoring Bluetti Systems
- Thread starter chromedshark
- Start date
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
@MrGPS Hmmmmmm. That warning that it's using Python 2.7 for pip seems like a problem. I went ahead and installed Python 3.7 just to test this and it works perfectly to install without any dependency issues. You might want to try
python3 -m pip install bluetti_mqtt to force it to use Python 3.7 instead of Python 2.7 on your system. It's also possible that pip3 install bluetti_mqtt would work too - you might not have a pip3 command though.
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
@Tinkerpete Yeah, the string you need to send for the DC Input Power is
"\x01\x03\x00\x24\x00\x01\xc4\x01". I did a detailed breakdown of how this is all built earlier in the thread so I'm not sure if you read that and there was something I said that was still unclear or you just missed that.For the last two bytes you're going to need to find a C++ library that can do MODBUS CRC16 if you you actually want to construct arbitrary commands yourself in C++, but another option would be to just use the Python code for now for that. It sounds like you managed to install the Python code, and so you should be able to use that like this:
Code:
$ python
Python 3.7.3 (default, May 22 2022, 10:21:14)
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from bluetti_mqtt.core import QueryRangeCommand
>>> bytes(QueryRangeCommand(0x00, 0x24, 1))
b'\x01\x03\x00$\x00\x01\xc4\x01'Edit: Feel free to DM me or send me an email at the address on my Github profile if you have more questions. I might not respond immediately, but I'll definitely get back to you as soon as I can. I'm happy to help anyone who wants to work on this.
Last edited:
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
@chromedshark: Many thanks for your help!
I will do it.
stackoverflow.com
I will test it later.
In the moment this is my biggest problem. I know this is hex code. I think i can read this as: 0103-0024-0001-c401. But I did not understand, where i must insert this in a notify characteristic string like this: "0000ff01-0000-1000-8000-00805f9b34fb"?
I have see this, but not analyzed!
I will do it.For MODBUS i found that:
Calculating Modbus RTU CRC 16
I'm implementing a software where I read and write data in Modbus RTU protocolo via serial. For that, I need to calculate the two CRC byte at the end of the string of bytes, but I'm being incapable...
stackoverflow.com
Yes, i can run your python code on my PC. But it did not find the bluetti.
This works!
Are you not comfortable with us continuing this in this thread?
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
@chromedshark:
I have test this function:
unsigned char arr[6] = {'\x01', '\x03', '\x00', '\x0a', '\x00', '\x37'};
Serial.println (CRC16_2(arr , 6));
and get: 7716 = Hex 1E24 !
Is this correct, because the bytes are changed in order?
If so, i can it made right with:
I have test this function:
Code:
unsigned int CRC16_2(unsigned char *buf, int len) {
unsigned int crc = 0xFFFF;
for (int pos = 0; pos < len; pos++) {
crc ^= (unsigned int)buf[pos]; // XOR byte into least sig. byte of crc
for (int i = 8; i != 0; i--) { // Loop over each bit
if ((crc & 0x0001) != 0) { // If the LSB is set
crc >>= 1; // Shift right and XOR 0xA001
crc ^= 0xA001;
}
else // Else LSB is not set
crc >>= 1; // Just shift right
}
}
return crc;
}unsigned char arr[6] = {'\x01', '\x03', '\x00', '\x0a', '\x00', '\x37'};
Serial.println (CRC16_2(arr , 6));
and get: 7716 = Hex 1E24 !
Is this correct, because the bytes are changed in order?
If so, i can it made right with:
Code:
unsigned short rightRotate(unsigned short x, short d) {
return (x >> d) | (x << (SHORT_SIZE - d));
}
Last edited:
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
It's not a UUID - it's just a string of raw bytes. Once you have the write characteristic (the
BLERemoteCharacteristic*) you'll notice it has a writeValue method for either a string or raw uint8_t array. You'll just call it with any command string. The default for setting response to false here works fine. If you did it correctly, then shortly afterwards you should receive a notification on the notify characteristic with a response payload (which you can then decode).Yes, that's the same value I get from the Python function I'm using. Most of the binary protocol seems to use network byte order (big-endian), but the CRC appears to be little-endian, so when you use it to build your string the byte order is reversed.
Code:
$ python
>>> import struct
>>> from bluetti_mqtt.core.utils import modbus_crc
>>> modbus_crc(b'\x01\x03\x00\x0a\x00\x37')
7716
>>> struct.pack('<H', 7716).hex()
'241e'If it's working for you then that's all I'm looking for.
Thanks for the Tip, with the force function is working now by using the !!! "python3 -m pip install bluetti_mqtt"
You have really done agreat work. Thankyou very much.
FYI, i got the following warning:
"The scripts bluetti-logger and bluetti-mqtt are installed in '/home/pi/.local/bin' which is not on PATH."
By changing your command to "python3 /home/pi/.local/bin/bluetti-mqtt" scan, broker and debug are working.
There is only a minor problem left, exactly every 30 minutes I get 0W on "DC Input"in Home Assistant.
Does anybody else with an EP500Pro have the same problem ?
UPDATE: I watched the LCD display on the EP500PRO and it also shows that every 30 minutes both PV Inputs go down to 0 for a few seconds.
I guess it does some recalibration. I'll ask the Bluetti Support.
Anyway, the Python Script works perfect. Once more Thank you very much.
Attachments
Last edited:
@slowdiver:
How do you log data via iobroker? I've connected my Raspberry PI with iobroker and MQTT-Broker. But there are only states from the beginning of the connection but no actual data.
How do you log data via iobroker? I've connected my Raspberry PI with iobroker and MQTT-Broker. But there are only states from the beginning of the connection but no actual data.
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
slowdiver
New Member
- Joined
- Aug 19, 2022
- Messages
- 3
@ApolloSK
Hi ApolloSK,
sorry but I moved the AC300 from my working room now to the final destination (basement). There is currently now Raspi there, so I can't test.
But if it was active, I saw changing values all the time. Values were only NOT changing if it was the same VALUE as before. I'm running only bluetti_mqtt on the Raspi. iobroker is running on a Linux box. There's MQTT Broker/Client running. Please check also If bluetti_mqtt is still running (check the logfiles), because serveral times the process was up, but no news in the logfile. I restartet the process and the updates in iobroker was visible again.
lgb-this
New Member
Fantastic job ! I operate a Bluetti AC200MAX and i monitor the device with a Raspberry Pi 3 and this software. I run bluetti-mqtt as a service in systemd with the following data:
How can i detect the reason for stopping the transmission of data ? Are there log files generated ?
This works fine for a certain time (a few hours up to a few days). Suddently no data are sent to the mqtt broker anymore. I have to restart the service and the data come immediately again.
How can i detect the reason for stopping the transmission of data ? Are there log files generated ?
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
It's possible this is the same reason as this other report. When running services with systemd, logs are automatically sent to syslog, and should be readable by running
journalctl -u name-of-the-service.target. You can use the -n 100 flag to specify the number of lines to print out, or the -f flag to print out each log line as it's generated by the service.
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
@ApolloSK When you run bluetti-mqtt for the first time it "permanently" adds those homeassistant keys, so any time a client connects to the MQTT broker it'll receive that config data automatically. If you're not seeing anything other than those keys then the script is probably not running for some reason. I would check the logs to see if it crashed or something.
lgb-this
New Member
I started the service on the 12. Sept at 22:10 and i see these data in the log:
There are no further data till now, but the service does not send data. The service is still running:
The process is visible in "ps -ef" too.
The data are back, when i restart the service.
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
@chromedshark: Now i have a working ble client! Thank you very much for your help!
Hey guys, first Thank you very much for your efforts and for @chromedshark for all his help answering my emails and getting me this far!
I have everything setup and working to Home Assistant... but I do have a question on how to parse a topic that has json payload.
I'm looking at topic "bluetti/state/AC300-##########/pack_details1" to run an automation in Home Assistant, but I need to check the value of the key "percent" in the json payload and use it to execute action if the value drops below a specific value.
I have everything setup and working to Home Assistant... but I do have a question on how to parse a topic that has json payload.
I'm looking at topic "bluetti/state/AC300-##########/pack_details1" to run an automation in Home Assistant, but I need to check the value of the key "percent" in the json payload and use it to execute action if the value drops below a specific value.
Last edited:
Hey guys. So I did figure out how to parse the json in the pack_details1 topic by editing the mqtt.yaml file and adding a sensor.
One thing that I notice is that when I added my second AC300 the "AC Output" entity bounces back and forth from enabled to disabled. I'm thinking this is because my system is in Split-Phase mode and even the Bluetti app only shows my Master unit's AC Output enabled. The slave unit shows it always off on the app.
Has anyone else seen this?
One thing that I notice is that when I added my second AC300 the "AC Output" entity bounces back and forth from enabled to disabled. I'm thinking this is because my system is in Split-Phase mode and even the Bluetti app only shows my Master unit's AC Output enabled. The slave unit shows it always off on the app.
Has anyone else seen this?
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
@chromedshark: My program fetches one value at a time. Do you do the same? Or is there a way to fetch all values at once?
lgb-this
New Member
I added a periodical restart in systemd with the line "RuntimeMaxSec=3600s":
Now i can monitor my device continuously.
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
@twister36 I only have a single AC300, but I suspect this is because one of the two places that value is stored should be ignored in this case. The question is which. If you use the
bluetti-logger command to collect logs from both your devices (just run it for ~5 minutes against each device) and send them to me I can probably fix this.
chromedshark
New Member
- Joined
- Apr 3, 2022
- Messages
- 33
@Tinkerpete Short answer is that there is a way to fetch multiple values at once and I'm doing that in bluetti-mqtt.
The longer answer is that can you use a query command (the 0x03 command) with a size greater than 1. The command
010300240001C401 will return a single field, the DC Input Power (stored at 0x00, 0x24). The command 01030024000E8405 will return 14 fields (0x0E) from 0x24 to 0x31 inclusive, covering all the data that the mobile app displays on the main page.As far as I can tell, the Bluetti only supports Bluetooth LE communication in fixed size packets. Once you cut out all the overhead, you're left with 20 bytes of data that can be stored in each notify packet - the amount of data that the Bluetti can send back in a single packet in response to a query. The Bluetti messaging protocol has 5 bytes of overhead (3 for the header and 2 for the CRC), so that leaves 15 bytes. If the size of your range query exceeds 15 bytes, then the response is split across multiple packets and you must reconstruct the full response by concatenating them together. This is what I'm doing in bluetti-mqtt, but it means I had to handle a bunch of other complications (timeouts, packet loss, packet corruption, etc.). Also, as the number of packets that need to be combined goes up, the odds of the entire response being corrupted goes up, so I've found that the sweet spot maximum is ~8 packets. If you don't want to deal with this complexity then you certainly achieve what you want by limiting yourself to requests for at most 7 fields in a single request (each field offset is a 2 byte value) and just making more requests.
The ideal architecture for this is two "threads": one for making requests and one for processing the response. You cannot make a new request until the response to the previous request has finished (or some timeout is reached), so the request thread is blocked waiting on the response processing thread. The response processing thread handles concatenating the pieces together, detecting when it has received all the data it's supposed to based on what the query was, verifying the checksum, and then notifying the request thread that the request is completed. This architecture then simplifies how you interact with the device in the rest of your code to making requests and either receiving a response or receiving some error.
Tinkerpete
New Member
- Joined
- Aug 31, 2022
- Messages
- 11
@chromedshark: Thank you for the detailed answer! The query of the individual values works very well for me. I was just wondering if this could put any strain on the Bluetti if, as I do in my programme, 12 values are queried every 5 seconds? In this case I would try to program it as you have described. But first of all, there seems to be no compelling reason for it.
superslide
New Member
- Joined
- Oct 15, 2022
- Messages
- 4
Really appreciate getting all this started @chromedshark and others!
For anyone looking for a super simple way to integrate into HA OS (Home Assistant Operating System), here's the cleanest, lowest code route I've found:
Find your device ID: I did this by getting into the HA OS host, then Docker instance, then manually installing bluetti_mqtt (pip install bluetti_mqtt) and running the --scan command (there's likely an easier way to do this).
Setup MQTT (if you haven't yet): Follow directions here - https://www.home-assistant.io/docs/mqtt/broker/ (including user/password combo)
Create script/shell_command integration: I created a new directory in /config/ called "shell" and placed a new script called install_start_bluetti_mqtt.sh in it. Inside that script (replace USERNAME, PASSWORD, DEVICE_ID with yours):
Once that's in there, add this to the root of your configuration.yaml:
Setup automation: Super simple automation that trigger's on HA start (can create with the GUI in Settings>Automations>Create Automation):
Note: the "id" value here has no connection to the DEVICE_ID, it's auto-generated by HA when creating a new automation
-
Have this up and running for my WIP AC300+2xB300+2xPV350 build - running HA OS 9 on a Raspberry Pi 3. Obviously a temp solution, but working well for now! Going to dig into HA OS 9+ BT support and see if I can help further a native HA integration.
For anyone looking for a super simple way to integrate into HA OS (Home Assistant Operating System), here's the cleanest, lowest code route I've found:
Find your device ID: I did this by getting into the HA OS host, then Docker instance, then manually installing bluetti_mqtt (pip install bluetti_mqtt) and running the --scan command (there's likely an easier way to do this).
Setup MQTT (if you haven't yet): Follow directions here - https://www.home-assistant.io/docs/mqtt/broker/ (including user/password combo)
Create script/shell_command integration: I created a new directory in /config/ called "shell" and placed a new script called install_start_bluetti_mqtt.sh in it. Inside that script (replace USERNAME, PASSWORD, DEVICE_ID with yours):
#!/bin/bash
pip install bluetti_mqtt
nohup bash -c "bluetti-mqtt --broker 127.0.0.1 --username USERNAME --password PASSWORD DEVICE_ID &"
Once that's in there, add this to the root of your configuration.yaml:
shell_command:
install_start_bluetti: bash /config/shell/install_start_bluetti_mqtt.sh
Setup automation: Super simple automation that trigger's on HA start (can create with the GUI in Settings>Automations>Create Automation):
Note: the "id" value here has no connection to the DEVICE_ID, it's auto-generated by HA when creating a new automation
- id: '1665937079543'
alias: Install and start bluetti-mqtt on HA start
description: ''
trigger:
- platform: homeassistant
event: start
condition: []
action:
- service: shell_command.install_start_bluetti
data: {}
mode: single
-
Have this up and running for my WIP AC300+2xB300+2xPV350 build - running HA OS 9 on a Raspberry Pi 3. Obviously a temp solution, but working well for now! Going to dig into HA OS 9+ BT support and see if I can help further a native HA integration.
Last edited:
Thanks for the Tip with the Bluetti_MQTT integration, i’ll try that when i am back from vacation.
I have an EP500Pro with 2 PV Strings attached and currently run the Bluetti_MQTT part on an Raspberry PI.
The native integration via HAOS inlc. native Bluetooth integration would be really great.
I have an EP500Pro with 2 PV Strings attached and currently run the Bluetti_MQTT part on an Raspberry PI.
The native integration via HAOS inlc. native Bluetooth integration would be really great.
Hi thank you for the manual the only what by me make troubles is the Setup Automation show here
have you a idea what is wrong ?
