Skip to content

Releases: Tom-Bom-badil/samson_trovis_557x

v2.0.0a Minor Bugfixes

29 Nov 10:34
1cf8801
Compare
Choose a tag to compare

This is a small service release with internal changes only.

While the plugin worked fine in a Python 3.10 / pymodbus 3 / Modbus RTU or TCP / Trovis 5579 environment,
a combination of Python 2.7 / pymodbus 2 / Modbus RTU on a Trovis 5576 threw some weird log entries.

Fixed in this release.

Release v2.0.0

28 Nov 16:08
8db5a84
Compare
Choose a tag to compare

2.0 changes:

Added support for Python 3.8+ and pyModbus3 (auto-switch between pymodbus2.2+/3.0+)
Added ModbusTCP support (for adapters with built-in TCP/RTU gateway like USR-TCP-K7 or USR-TCP232-E2)
Changed connection behaviour - added connect() and disconnect() to regular polls (formerly only at startup)
Updated register/coil tables, added new information, revised existing information, included Rk3 for 5579
Updated plugin.yaml: Rev 2 in format x.x.x, status 'ready', added 'werte' attribute to prevent errors in log
Removed unnecessary development files (templates, tools, assets) from official shNG-Plugins repo
Updated trovis.yaml items file, added Rk3+Sensors (e.g. for 5579)
New optional item attribute 'invalid_to_zero' to change response of 32767 (=switched off/unavailable/error) to 0
Updated Wiki, included A LOT of useful background information: github.com/Tom-Bom-badil/samson_trovis_557x/wiki

Minor bug fixes, bunch of new explanations in readme's

10 Sep 10:17
3e92638
Compare
Choose a tag to compare
Update __init__.py

Changed revision to 1.0.1 for new release

Release 1.0

08 Sep 16:30
d6165ba
Compare
Choose a tag to compare

This release includes the latest bugfixes, changes and amendments.
It replaces older files in /plugins/trovis_557x.
Please do not forget to delete pycache if manually installed.

Initial release

06 Aug 22:43
b22d090
Compare
Choose a tag to compare

As the plugin is running well and smooth meanwhile, it is time to get it to the first release.

Still only reading out of registers/coils (no writing intended so far), and still without smartHomeNG Web Interface support.