Python Protocol Gateway reads data via Modbus RTU or other protocols and translates the data for MQTT. In the long run, Python Protocol Gateway will become a general purpose protocol gateway to translate between more than just modbus and mqtt. Growatt, EG4, Sigineer, SOK, PACE
Big changes, mainly rewriting the whole thing so that it can cleanly and easily accomodate future data streams, such as canbus, as well as significant added flexibility.
Because of theese significant changes and configs have to be completely rewritten.
The reason for the minor version increament is due to these changes. config wise there is no backwards compatability.
Do not update unless you are prepared to reconfigure / reinstall your setup :S
a transport is describing the device that you are connecting to and it's data.
All existing features remain to exist, but may be a bit buggy until i get back to them for testing.
In the future i will be testing and adding functionality for translating between all "transport" types.
ie, creating two transports, modbus rtu, and modbus tcp, will allow you to essentially create a modbus tcp server/gateway.
you can have multiple devices on one instance, but i recommend against it, and recommend using seperate configs / instances for the sake of stability. this is also currently untested :P
Big changes, mainly rewriting the whole thing so that it can cleanly and easily accomodate future data streams, such as canbus, as well as significant added flexibility.
Because of theese significant changes and configs have to be completely rewritten. The reason for the minor version increament is due to these changes. config wise there is no backwards compatability. Do not update unless you are prepared to reconfigure / reinstall your setup :S
installation procedure is the same as before. I've created two wikis to help document this more flexible way. https://github.com/HotNoob/PythonProtocolGateway/wiki/Configuration-Examples#modbus-rtu-to-mqtt https://github.com/HotNoob/PythonProtocolGateway/wiki/Transports
a transport is describing the device that you are connecting to and it's data.
All existing features remain to exist, but may be a bit buggy until i get back to them for testing.
In the future i will be testing and adding functionality for translating between all "transport" types. ie, creating two transports, modbus rtu, and modbus tcp, will allow you to essentially create a modbus tcp server/gateway.
you can have multiple devices on one instance, but i recommend against it, and recommend using seperate configs / instances for the sake of stability. this is also currently untested :P