H all

Has anyone attempted this ?

I've seen one guy doing it via the console port, using a we mod D1 mini and some other add on.

thinking same code that we use to monitor Sunsync via RS485 can be repurposed by specifying the correct addresses and defining measurement names as option #1, 

other idea.. how to write a program onto a raspberry pi zero, call the address and then package all values int a json payload. actually keen on trying this... if anyone has ?

@scoobe3d @slipx

 

G

Edited September 17, 20232 yr by georgelza

anyone ?

I see the Pylontec has a RS485 port.... any chance anyone has the modbus addresses for the various metrics. could then reuse the esphome bits thats used to extract data from a sun sync and just build the correct yaml file with metrics/modbux address to extract the battery metrics ?

other option is raspberry pi zero > FTDi -> RJ45 onto console port ?

G

Yep, tried it according to https://github.com/irekzielinski/Pylontech-Battery-Monitoring/blob/master/README.md

But couldn't get it working ... somewhere between the D1 Mini, the RSS232 to TTL and the battery I couldn't pickup any comms - eventually ran out of time without it working, sorry can't give more reasons what the issue was...

 

ye found this one also, looks like a good base/starting point, but also that goes into the console port, not RS485.
 

can you confirm, into which Import did you plug. this solution goes into RS485, would that not be Canbus ? with addresses ?

G

Edited September 18, 20232 yr by georgelza

tbh, I'm not familiar with the differences between the ports .... I had plugged into the console port, if I remember correctly the same port that I'd used to read details with Batteryview / do FW upgrades.
So you may be onto something why I couldn't get it working? (using the wrong port)

This was a while ago that I'd tried it so can't remember all details 🤔

 

no, the console port is the right port to be used for BatteryViewer and FW upgrades. 

There are another port there, called a RS485. it's normally the type of port through which can bus protocol is used.

just looking into things.

G

OK, I'm following closely to see if you do come right

I have my D1 mini sitting here on my desk (on the "to-do-when-I-have-time" pile, lol)... do hope to get it up and running one day to feed to HomeAssistant

found this...

https://www.setfirelabs.com/building-automation/pylontech-us2000-us3000-nodemcu-can-reader#comment-57886

and this can bus controllers are available locally.

G

Aha...cheers for that, will check it out tomorrow...

Hi @georgelza

Old thread I know, did you ever come right with connecting to your batteries over the RS485?

I just posted my video on connecting to the PACE BMS's over the RS485 but you need to enable the PACE_Modbus protocol in the BMS for it to work.

As Pylon protocol seems to be the standard on most batteries and it would be nice to just have a plug and play solution. I was wondering if you ever managed to communicate with your Pylon batteries over the RS485.

:-)

in current reality you able create custon modbus register map (or other modules if need) for United BMS framework, and use addon with any batteries what support rs485 connection :

https://github.com/mamontuka/ritar-bms-ha

https://github.com/mamontuka/ritar-bms-ha/tree/main/united_bms

https://github.com/mamontuka/ritar-bms-ha/tree/main/united_bms/united_bms_ssh_cli