BMS protocol and read-out

[NikArc]

Hello all!

I just had to register because I am stuck with my problem.
I get me a LiFePO4 battery from aliexpress (I can post a link if needed), it's quite nice, but it only communicates using the windows software you get from the vendor.
The battery can communicate with diverse inverters, so I suppose there is some kind of standard protocol for RS485 communication.
But I did not find anything and hacking serial communication is new to me, too

I don't know the type of BMS, the software shows DR-HUANY04, but I can't find anything with that name.
After looking at forum posts here, I don't think its seplos compatible. Converted to ASCII the request looks different.
The software also says "Protocol: DR-1363", nothing relevant found with google.

I sniffed the communication and I found that the software sends
7E 32 32 30 31 34 41 34 32 45 30 30 32 30 31 46 44 32 38 0D
to get data back.

The BMS replies with
7E 32 32 30 31 34 41 30 30 45 30 43 36 30 30 32 37 31 30 31 34 46 35 31 30 30 44 32 30 30 44 30 39 30 44 30 41 30 44 30 42 30 44
30 39 30 44 31 36 30 44 30 39 30 44 31 36 30 44 32 39 30 44 32 45 30 44 30 45 30 44 30 39 30 44 30 41 30 44 30 43 30 44 34 41 30
44 34 36 30 31 34 41 30 31 32 43 30 31 34 30 30 34 30 31 32 43 30 31 32 43 30 31 33 36 30 31 33 36 30 30 30 30 30 30 30 30 30 30
36 34 30 31 32 38 43 41 32 38 43 41 30 30 30 36 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 33 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 44 35 33 35 0D

7E 32 32 30 31 34 41 30 30 45 30 43 36 30 30 32 37 31 30 31 34 46 35 31 30 30 44 32 30 30 44 30 39 30 44 30 41 30 44 30 42 30 44
30 41 30 44 31 37 30 44 30 39 30 44 31 35 30 44 32 39 30 44 32 45 30 44 30 46 30 44 30 41 30 44 30 41 30 44 30 42 30 44 34 39 30
44 34 36 30 31 34 41 30 31 32 43 30 31 34 30 30 34 30 31 32 43 30 31 32 43 30 31 33 36 30 31 33 36 30 30 30 30 30 30 30 30 30 30
36 34 30 31 32 38 43 41 32 38 43 41 30 30 30 36 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 33 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 44 35 32 44 0D

7E 32 32 30 31 34 41 30 30 45 30 43 36 30 30 32 37 31 30 31 34 46 35 31 30 30 44 32 30 30 44 30 39 30 44 30 41 30 44 30 42 30 44
30 39 30 44 31 36 30 44 30 39 30 44 31 35 30 44 32 39 30 44 32 45 30 44 30 45 30 44 30 41 30 44 30 41 30 44 30 42 30 44 34 39 30
44 34 35 30 31 34 30 30 31 32 43 30 31 34 30 30 34 30 31 32 43 30 31 32 43 30 31 33 36 30 31 33 36 30 30 30 30 30 30 30 30 30 30
36 34 30 31 32 38 43 41 32 38 43 41 30 30 30 36 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 33 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 44 35 34 39 0D
(3 examples)

I can do this much, but I don't know how to get the data I want to know from the BMS.
I don't really need cell voltages, but I don't mind to "know" every data I can get out of this data reply.

I use a raspberry pi and node red and I need to know battery current and voltage, also charging states to be able to write the code for my charging script.
And of course temperatures etc would be interesting, too.

Does anyone recognize the protocol by looking at the data above? Google is no help, but since the battery can communicate with different inverter brands out of the box, there must be some standard?

One way to go could be getting a lot of these replies and compare what has changed and maybe calculate 16/32 bit values out of it and then compare them with screenshots of the BMS windows software, but I suppose that's a lot of trouble.

Thanks for hints and with best regards,
Nik

 

[Dave21]

The most common value is 30 hex (which is 0 in ASCII table). All values between the initial 7E (~) and trailing CR looks like ASCII values. Maybe, it can help to translate these packets into their ASCII forms and you will see much more from the data. Chinese developers like textual protocols even they are usually too verbose compared to binary ones.

 

[NikArc]

ok, that's interesting

the hex values (of a new data packet) are

~22014A00E0C600271014E5100D130D070D080D0A0D080D0E0D070D0C0D180D1A0D090D080D070D080D280D23012C0122012C04012C012C012201220000000000640128CA28CA0006000000000000000000230000000000000000000000000000000000000000000000D56C

in ASCII

 

[Dave21]

Ok, now in ACII representation, it is clear that there are hex numbers. It seems tha you have 16 cells in the system. The sequence of 16-bit numbers like this:

0D13
0D07
0D08
0D0A
0D08
0D0E

represent cell voltages. For example the second value 0D07 seems to be decimal number 3335 where BMSes usually sent out values in mV precession thus I assume that some cell in your pack has 3.335V at that moment. Numbers seems to be encoded using big-endian style. All others will be encoded the same way. You can now easily decode positions of all fields using existing application and searching data packet. Aside of cell voltages, I suppose there will be: SoC, total voltage, charging/discharding current, remaining capacity, cycle AH, temperature sensors if there are some and possibly other values. The very last 16-bit number D56C in hex is highly probably 16-bit check sum of all previous values. I assume it will be one of the standard approach like CRC16.

 

[NikArc]

since it is new to me and to understand it better:
So it is as you said? I have to convert the buffer to ASCII which then contains hex values which I have to decode to 16bit numbers? (well, it might contain status bits somewhere, too, no idea yet)

I think I made some progress, 2 data packages:

~22014A00E0C6002
71014E510

0D13 cell01 3347V
0D07 cell02 3335V
0D08 cell03 3336V
0D0A cell04 3338V
0D08 cell05 3336V
0D0E cell06 3342V
0D07 cell07 3335V
0D0C cell08 3340V
0D18 cell09 3352V
0D1A cell10 3354V
0D09 cell11 3337V
0D08 cell12 3336V
0D07 cell13 3335V
0D08 cell14 3336V
0D28 cell15 3368V
0D23 cell16 3363V

012C temp 30.0
0122 temp 29.0
012C temp 30.0

0401
2C012C012201220000
000000640128CA
28CA SoC/Capacity 104.42Ah
0006000000000000000000230000000000000000000000000000000000000000000000D56C


~22014A00E0C6002
39A150D10

0D27 cell01 3367V
0D29 cell02 3369V
0D2B cell03 3371V
0D29 cell04 3369V
0D28 cell05 3368V
0D29 cell06 3369V
0D2A cell07 3370V
0D28 cell08 3368V
0D28 cell09 3368V
0D29 cell10 3369V
0D28 cell11 3368V
0D2A cell12 3370V
0D29 cell13 3369V
0D2A cell14 3370V
0D28 cell15 3368V
0D26 cell16 3366V

0118 temp 28.0
010E temp 27.0
0118 temp 28.0

0401
0E010E010E010E0285
000000640128CA
252D SoC/Capacity 95.17Ah
0006000000010000000000230000000000000000000000000000000000000000000000D520



That means I have to work with substrings after decoding to ASCII, I guess.

 

[NikArc]

okay, I'm really close now, there are only a few places left to find out

~22014A00E0C600
2710 SoC value 10000%/100
14E5 batt volt 5349mV*10
10 cell count 16

0D13 cell01 3347mV
0D07 cell02 3335mV
0D08 cell03 3336mV
0D0A cell04 3338mV
0D08 cell05 3336mV
0D0E cell06 3342mV
0D07 cell07 3335mV
0D0C cell08 3340mV
0D18 cell09 3352mV
0D1A cell10 3354mV
0D09 cell11 3337mV
0D08 cell12 3336mV
0D07 cell13 3335mV
0D08 cell14 3336mV
0D28 cell15 3368mV
0D23 cell16 3363mV

012C temp 300°C*10
0122 temp 290°C*10
012C temp 300°C*10

04 ?

012C Tmp1 300°C*10
012C Tmp2 300°C*10
0122 Tmp3 290°C*10
0122 Tmp4 290°C*10

FE5C current -420A*100

000000640128CA ?
28CA SoC/capacity 10442mAh/10
00060 ?
0 error state
0 OverVoltage error state
0 error state
000 ?
0 charging states (0, 1, 2, idle, charge, discharge)
0000000000230000000000000000000000000000000000000000000000D56C ? probably error states which are all 0 right now + checksum

 

[DrSolar]

Hi,

Just last week I received the same type of battery as you and will be figuring out this protocol soon, just as you are. Thus far I have found one very useful document. Search for and download this pdf: "PYLON LFP Battery communication protocol - RS485 V2.8 20161216.pdf" It contains the basics of the communications protocol this battery seems to be using including how to decode numbers and compute the necessary checksums.

In addition to reading the current state, cell voltages, etc., I hope I can also read and possibly change settings as well.

Cheers.

 

[Jaxonwood]

okay, I'm really close now, there are only a few places left to find out

~22014A00E0C600
2710 SoC value 10000%/100
14E5 batt volt 5349mV*10
10 cell count 16

0D13 cell01 3347mV
0D07 cell02 3335mV
0D08 cell03 3336mV
0D0A cell04 3338mV
0D08 cell05 3336mV
0D0E cell06 3342mV
0D07 cell07 3335mV
0D0C cell08 3340mV
0D18 cell09 3352mV
0D1A cell10 3354mV
0D09 cell11 3337mV
0D08 cell12 3336mV
0D07 cell13 3335mV
0D08 cell14 3336mV
0D28 cell15 3368mV
0D23 cell16 3363mV

012C temp 300°C*10
0122 temp 290°C*10
012C temp 300°C*10

04 ?

012C Tmp1 300°C*10
012C Tmp2 300°C*10
0122 Tmp3 290°C*10
0122 Tmp4 290°C*10

FE5C current -420A*100

000000640128CA ?
28CA SoC/capacity 10442mAh/10
00060000000 ?
0 charging state (I saw 0, 1, 2)
0000000000230000000000000000000000000000000000000000000000D56C ? probably error states which are all 0 right now

Are you planning to do anything with the data like supply a monitoring app?

 

[NikArc]

@DrSolar I see, I still have one or 2 unknown parts in the information packet from the BMS, maybe it's listed there, I have to check it
It looks like mine is similar to the Pylon protocol, but actually different order and partly different data

@Jaxonwood: currently I have planned nothing like this. Since I use node-red, everything needed is there, you just have to split the data into substrings and you have the values for everything you might need. So I just do this and I'm able to work with the values to charge the battery with my PSU.

 

[kanenas]

Hi,
I also bought one with 48v and 120Ah. The BMS seems to be the same.
I have the software for where some things become visible.
I can sent it to you if you want.

Regards
Kanenas

 

[NikArc]

I have the software, too
but since it runs on windows, I can not use it with my Raspberry Pi

but beside this, do you know more about the settings you can adjust using the software?
I did not play around with it yet because I don't want to f*ck something up :>
I also noticed that some fields are password protected.

 

[kanenas]

The PW from my BMS is 666666. But be carefully with changes.
I am searching for a solution to readout the Parameters. I test the "solaranzeige.de" with a Pylontech Batterie Protokoll but the protocols are not compatible.

After i put the PW i became more Informations in the menu "Help":



And know the big question: If i change the protocol to pylon1363 then maybe then the "solaranzeige.de" software can read the parameters. If that is the case, then it will be possible to read the data via the MQTT server from solaranzeige.de

On the other hand i am afraid that it will be not more possible to have a communication with the own software to change the parameters of the BMS.

I will inform you if i have some news ...
Many Regards

 

[NikArc]

ohh, I will try that password later, can't do it right now

for me it works fine now with node red.
the few missing (or unknown) values are not important for normal use

 

[kanenas]

ohh, I will try that password later, can't do it right now

for me it works fine now with node red.
the few missing (or unknown) values are not important for normal use

I right you the same here: https://forum.drbacke.de/viewtopic.php?t=5510&sid=f05fa9ee9457ecd383db731a0a695fd4&start=30.
With your comments here i use now node red too. I never used bevor and it takes some days to understand how it works and to fount a solution for me. I node red send the data over MQTT to FHEM for automatikaly charge - discharge.
Know it works for me fine too.

 

[dingbsums]

Hello and sorry for digging up this thread. But it seems I have a similar or same battery only without software or cables or a manual.

May I ask what the software is called for the PC? I would also like to get the data into my smarthome later to monitor the akuu somewhat.

 

[kanenas]

Hello and sorry for digging up this thread. But it seems I have a similar or same battery only without software or cables or a manual.

May I ask what the software is called for the PC? I would also like to get the data into my smarthome later to monitor the akuu somewhat.

Hi, I hoppe it helps.
if you need the Code for Node Red, give me a feedback.

PW: 48V_LIFEPO4_BATTERY

Regards

 

[dingbsums]

Hello, thank you very much, I will try it. Thanks to @NikArc I have now also two three data from the battery can read and display them via Node Red.

 

[msawalhi]

Hi, I hoppe it helps.
if you need the Code for Node Red, give me a feedback.

PW: 48V_LIFEPO4_BATTERY

Regards

hello, can you please confirm the password since it doesn't work?
many thanks

 

[kanenas]

hello, can you please confirm the password since it doesn't work?
many thanks

PW it works (48V_LIFEPO4_BATTERY). I used 7-Zip 22.01 ->

7-Zip

 

[kanenas]

Hello, thank you very much, I will try it. Thanks to @NikArc I have now also two three data from the battery can read and display them via Node Red.
View attachment 119637

my Overview:

 

[nepumuk]

hello, can you please confirm the password since it doesn't work?
many thanks

use "48V_LIFEPO4_BATTERY ", one space character at the end!

 

[dingbsums]

my Overview:
View attachment 120434

View attachment 120435

Is this Node-Red? Looks amazing!

 

[kanenas]

Is this Node-Red? Looks amazing!

Yes... THX.
I didn't know Node Red before and I had to find a solution in a week. Maybe is my solution not the smartest but works stably.
Atached the code...
Have fun.

PS: Ich schreibe hier weil auch nicht deutschsprachige die Interessen haben, davon profietieren.



And the Solution in FHEM over MTTQ

 

[rrroonn]

This is a great thread. I too have been working on monitoring these batteries which appear to use an old version of the pylontech protocol which I cannot find any doco for. They use version "2.2" but I can only find doco for ver 2.8, so having this thread saved some time decoding the dumps!

I am mostly after some basic information such as SOC, voltage and current and have created a Node Red flow to publish to MQTT. Its just a different take on the same problem. I have shared in case it can save someone else some time. I have two batteries so the code may need adjustment depending on your situation.

No warranty and no support!

[{"id":"e8741fa499dd6155","type":"tab","label":"Batteries From China","disabled":false,"info":"","env":[]},{"id":"b80ca6efc679cf53","type":"function","z":"e8741fa499dd6155","name":"request","func":"/*\nSAMPLE\n 1: ~   SOI\n 2: 22  VER\n 3: 01  ADR\n 4: 4A  CID1    \n 5: 42  CID2    Get analaog values\n 6: E0  LEN1    Length checksum = E\n 7: 02  LEN2    Length 2 hex bytes\n 8: 01  INFO    Get pack 1 data\n 9: FD  CHKSUM\n10: 28  CHKSUM\n11: CR  EOI \n*/\nvar cmd = []\n\ncmd[0] = \"~22\"      // SOI, VER\ncmd[1] = msg.addr   // ADDR: \"01\" or \"02\"\ncmd[2] = \"4A42\"     // CID1, CID2\ncmd[3] = \"E002\"     // LEN\ncmd[4] = \"01\"\n\nvar cmdstr = cmd.join('');\nvar C = 0;\nfor (let index = 1; index < cmdstr.length; index++) {\n    const c = cmdstr.charCodeAt(index);\n    C += c;\n}\nC = (~C & 0xffff) + 1\n \nmsg.payload = cmdstr + C.toString(16).toUpperCase() + \"\\x0d\"\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":370,"y":360,"wires":[["67f3703dd92df2ef"]]},{"id":"a79405afce98bcd2","type":"inject","z":"e8741fa499dd6155","name":"5s","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":true,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":70,"y":360,"wires":[["084f2bcfa9d4ad43"]]},{"id":"67f3703dd92df2ef","type":"serial request","z":"e8741fa499dd6155","name":"","serial":"91d1aae3823e1ef2","x":530,"y":360,"wires":[["e9e6b0f2ad058063","b42e1447116f89e2","d42f8c64bea41df4"]]},{"id":"e9e6b0f2ad058063","type":"function","z":"e8741fa499dd6155","name":"extract","func":"/*\n          ~               = SOI\n 01       22              = Ver = 22\n 03       01              = ADDR\n 05       4A              = CID1\n 07       00\n 09       E0C6            = Length + length checksum\n 13       00\n 15       2704            = SOC 99.88 (/100)\n 19       1533            = Pack voltage 54.27V (/100)\n 23       10              = 16 cells\n 25       0D44            = cell voltages, 3396mV\n 29       0D57            = 3415 mV\n        0D2D\n        0D14\n        0D11\n        0D13\n        0D6F\n        0D22\n        0D70\n        0D70\n        0D6D\n        0D34\n        0D33\n        0D0F\n        0D5C\n        0D55            = cell 16 voltage\n        010E            = 27 deg C (/10)\n        00FA            = 25 deg C (/10)\n        010E            = 27 deg C (/10)\n 101    04\n 103    0104\n 107    0104\n 111    0104\n 115    00FA\n 119    0000            = Current ?\n        0000\n        0064\n        01\n        30D4            = 125 Ahr total capacity\n        30C6            = 124.86 Ahr available\n        0005            = 5 cycles\n        0000\n        0000\n        0000\n        0000\n        0023            = 35\n        0000000000000000000000000000000000000000000000\nD563            = checksum\n*/\nif (msg.status != \"OK\")  return; // no data\n// check RTN code for valid (==\"00\")\nif (msg.payload.substr(7, 2) != \"00\") return; // no data\nmsg.D = msg.payload  // save original data\n\n/* it appears that sometimes we get results for different battery, maybe\n because of a timeout on previous call? Either way, we can use the data\n  as long as it is valid\n*/\n\nmsg.addr = msg.D.substr(3, 2)\n\n// Checksum validation\nvar C = 0;\nfor (let index = 1; index < msg.D.length-5; index++) {\n       const c = msg.D.charCodeAt(index);\n       C += c;\n}\nC = (~C & 0xffff) + 1\n\nvar rxC = parseInt(msg.D.substr(msg.D.length-5, 4), 16)\nmsg.valid = (C == rxC)\nif (!msg.valid) return;  // return with no data if invalid\n\nmsg.payload = {}\n\nmsg.payload.soc = parseInt(msg.D.substr(15, 4), 16) / 100\nmsg.payload.voltage = parseInt(msg.D.substr(19, 4), 16) / 100\n// Parse current\nvar a = parseInt(msg.D.substr(119, 4), 16)\nif ((a & 0x8000) > 0) a = a - 0x10000; // need to handle negative hex number for current\nmsg.payload.current = a/100;\n//\nmsg.payload.cellcount = parseInt(msg.D.substr(23,2),16)\nmsg.payload.cellvoltage  = []\nfor (let index = 0; index < msg.payload.cellcount; index++) \n{\n       msg.payload.cellvoltage[index] = parseInt(msg.D.substr(25+4*index, 4), 16)         \n}\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":520,"y":280,"wires":[["b08a5271bceeaa98","0842c048ba4040fd"]]},{"id":"54a14510753a8c7f","type":"mqtt out","z":"e8741fa499dd6155","name":"Publish","topic":"","qos":"1","retain":"true","respTopic":"","contentType":"","userProps":"","correl":"","expiry":"","broker":"9cb0be1e.1c82a","x":960,"y":210,"wires":[]},{"id":"b08a5271bceeaa98","type":"split","z":"e8741fa499dd6155","name":"","splt":"\\n","spltType":"str","arraySplt":1,"arraySpltType":"len","stream":false,"addname":"key","x":650,"y":280,"wires":[["439a6141cc9dad27"]]},{"id":"cd8a4e22f0d435dc","type":"debug","z":"e8741fa499dd6155","name":"debug 12","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":950,"y":280,"wires":[]},{"id":"439a6141cc9dad27","type":"function","z":"e8741fa499dd6155","name":"make key","func":"msg.topic = \"NRED/Power/battery/china/\" + msg.addr + \"/\" + msg.key\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":790,"y":280,"wires":[["cd8a4e22f0d435dc","da41da0092a687b6"]]},{"id":"da41da0092a687b6","type":"rbe","z":"e8741fa499dd6155","name":"","func":"rbe","gap":"","start":"","inout":"out","septopics":true,"property":"payload","topi":"topic","x":820,"y":210,"wires":[["54a14510753a8c7f"]]},{"id":"b42e1447116f89e2","type":"debug","z":"e8741fa499dd6155","name":"debug 13","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":800,"y":360,"wires":[]},{"id":"d42f8c64bea41df4","type":"switch","z":"e8741fa499dd6155","name":"addr==01?","property":"addr","propertyType":"msg","rules":[{"t":"eq","v":"01","vt":"str"}],"checkall":"true","repair":false,"outputs":1,"x":480,"y":500,"wires":[["7ccdb8358f62bed5"]]},{"id":"7ccdb8358f62bed5","type":"change","z":"e8741fa499dd6155","name":"addr=02","rules":[{"t":"set","p":"addr","pt":"msg","to":"02","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":630,"y":500,"wires":[["20be21bf678fd47d"]]},{"id":"084f2bcfa9d4ad43","type":"change","z":"e8741fa499dd6155","name":"addr=01","rules":[{"t":"set","p":"addr","pt":"msg","to":"01","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":210,"y":360,"wires":[["b80ca6efc679cf53"]]},{"id":"f561167b68f27b78","type":"link in","z":"e8741fa499dd6155","name":"B-again","links":["20be21bf678fd47d"],"x":195,"y":260,"wires":[["b80ca6efc679cf53"]]},{"id":"20be21bf678fd47d","type":"link out","z":"e8741fa499dd6155","name":"link out 1","mode":"link","links":["f561167b68f27b78"],"x":725,"y":500,"wires":[]},{"id":"2ccc611d35c3595e","type":"comment","z":"e8741fa499dd6155","name":"loop for 2nd battery","info":"","x":650,"y":460,"wires":[]},{"id":"0842c048ba4040fd","type":"debug","z":"e8741fa499dd6155","name":"debug 14","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":620,"y":200,"wires":[]},{"id":"91d1aae3823e1ef2","type":"serial-port","serialport":"/dev/ttyUSB2","serialbaud":"19200","databits":"8","parity":"none","stopbits":"1","waitfor":"","dtr":"none","rts":"none","cts":"none","dsr":"none","newline":"300","bin":"false","out":"interbyte","addchar":"","responsetimeout":"2000"},{"id":"9cb0be1e.1c82a","type":"mqtt-broker","name":"MQTT_R1","broker":"192.168.7.101","port":"1883","clientid":"nodered_client1","usetls":false,"compatmode":false,"protocolVersion":"4","keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","birthMsg":{},"closeTopic":"","closeQos":"0","closePayload":"","closeMsg":{},"willTopic":"","willQos":"0","willPayload":"","willMsg":{},"sessionExpiry":""}]

 

[Yaza]

Can I have a password please, because the given one doesn't work, I'm using 7zip.

The password works, sorry to disturb you.