v0.8.0

Major release

This version comes with the option to select the level of detail for cells_monitoring.
From now on, it is possible to choose how much you need to know about the parameters of the battery cells. You will have 3 levels "low", "medium" and "high" which will give you the freedom to configure the monitoring system based on your needs.

The main changes:

• new: cell monitoring level of detail -- close #38
• change: Updated documentation to reflect changes

Compatibility:
Backwards compatibility is ensured for sensors automatically discovered in Home Assistant, MariaDB (Sensors and Records).
Pay attention to the configuration file that has been modified. This version does not work with previous configuration files.
For clarity, the [event] section has been split into two, [event_monitoring] and [cell_monitoring].
A new line "monitoring_level" has also been added to the [cells_monitoring] section.

Delete previous Home Assistant devices, they will be recreated when the program is restarted.
ENJOY

v0.7.4

• fix: system sensors become 'unknown' after Home Assistant restart - close #34

v0.7.3

• fix: missing some elements in log file close #33
• update: requirements.txt

v0.7.2

• enhance: optimize MQTT to reduce unnecessary trafic -- close #31
• fix: console display for discovery progress %
• clean-up

0.7.1

This release comes with bug fixes and improvements after cells monitoring implementation.

Main changes:

• fix: Pylontech no cells data -- close #26, close #27 @vapopescu , @chinezbrun
• fix: MQTT publish -- refactoring, split topics to avoid overloads -- close #28 , close #29 @vapopescu
• fix: MQTT discovery -- refactoring
• new: auto start as background service instructions
• update: documentation to reflect all changes

Note:
As the MQTT discovery was updated is mandatory to delete all created devices in Home Assistant before start this release. Devices will be created in new configuration. Backward compatibility of the sensors name, history is maintained.

v0.7.0

Major release

This release come with cells monitoring option. Meaning that, as of this release you can have available sensors in Home Assistant for every single battery cell. On top, additional statistics are now available like min, max or delta per each battery. Statistics are performed by the program based on cells data.

Main changes:

• new: cells monitoring -- close #24
• new: statistics for cells -- close #25
• enhance: MQTT discovery -- refactoring, improved speed
• change: documentation updated to reflect changes

Compatibility:
Backward compatibility is ensured for auto discovered sensors in Home Assistant, MariaDB (sensors and records), but you need to pay attention to config file that was changed. This release doesn't work with previous config files, a new row 'cells_monitoring' was added in [event] section.

enjoy!

v0.6.2

fix: reported 100% CPU when running -- close #23

v0.6.1

fix: cells data could not be read - error message -- close #22

v0.6.0

Major release

This release come with possibility to have in Home Assistant multiple devices from all systems where pytes serial is running. Meaning that, as of this release you can have more pytes serial running in different hosts/location and the output to be captured in Home Assistant as multiple devices.

Main changes:

• new: Home Assistant device name can be customised now in config file (i.e pytes, pytesone, pytestwo, pylon ...) -- close #20
• fix: wrong 100% SOC display in log files -- close #19
• fix: sensor nickname display for HomeAssistant -- close #21
• change: renamed one json field name for better alignment with pylon ('pytes' to 'devices')

Compatibility:
This release doesn't work with previous config files, as a new section was added. Backward compatibility is ensured for HA, MariaDB (sensors and records), but you need to pay attention to config file that was changed.
If you have only one pytes serial that is running the changes are minimal for you and you will not notice the differences except bugfixes #19, #21.

Home Assistant:
For the auto discovered sensors, backward compatibility is ensured if default values in new section are kept.
If you have sensors, manually declared in Home Assistant, please re-check the yaml file, they may be affected as the JSON file format was changed.

MariaDB: if two or more pytes serial instances are running you need to create an additional table in the database for each and to have corresponding settings in the individual configuration file too.

MQTT: if two or more pytes serial instances are running state topic will be in line with each device name

v0.5.0

Major release

This release come with two new functionalities: logging and cells monitoring.

Main changes:

• new: logging level, log size, number of backups can be selected now in config file (close #16)
• new: power_events, bat_events, sys_fault are now monitored (close #18)
• new: events are human readable (system faults only) (close #17)
• new: cells details are logged in 'battery_events.log' when a selected event happened - log is created automat
• new: pytes-serial events are now logged in 'pytes_serial.log'- log is created automat
• new: no of events since script started are reported now in section 'serial_stat' of JSON file
• info: old event.log is deprecated

Compatibility:
This release has backward compatibility (MQTT, MariaDB, JSON) but you need to pay attention to config file that was changed (two new sections added to the end) to accommodate new features #16, #18
More info here