Releases: jollyjinx/modbus-2-mqtt-bridge
2.2.0 added bitmap and rawValues and GoodWe inverter
This has now the GoodWe inverter added as well as supporting raw and bitmapped values.
When using the map dictionary to convert values to names the original rawValue key is now added to the json output.
E.g.
{
"address": 1000,
"modbustype": "holding",
"modbusaccess": "read",
"valuetype": "uint16",
"mqtt": "visible",
"interval": 10,
"map": {
"0": "NONE",
"1": "MESSAGE",
"2": "WARNING",
"3": "ALARM",
"4": "FAULT"
},
"topic": "heatpump/errorstate",
"title": "Heatpump Error State"
}
results in the following json:
{"address":1000,"rawValue":0,"title":"Heatpump Error State","value":"NONE"}
You can use specific bitfields and name them like:
{
"address": 2,
"modbustype": "holding",
"modbusaccess": "read",
"valuetype": "uint16",
"mqtt": "visible",
"interval": 5,
"bits": { // you can bit mappings for values
"0": { "name" : "running" }, // a single bit will be mapped to a boolean
"1-3": { "name" : "mode" }, // multiple values will be mapped to the integer number with those bits shifted to the right
"4-15": { "name" : "reserved" }
},
"topic": "test/state",
"title": "Test State"
}
}
2.1.3 Strict Concurrency
Updated to use Swift Strict Concurrency.
Released Version on docker with release tag jollyjinx/modbus2mqtt:2.1.3 additionally to :latest
2.2.1
This release adds a feature to use the mapping dictionaries for requests as well.
E.g. instead of sending:
topic: lambda/request/heatpump_requesttype
{
"topic": "heatpump/requesttype",
"value": 4,
"date": "2024-02-14T14:31:56Z",
"id": "D33456D6-9361-489D-97E7-C4A082781B7C"
}
you can also send:
{
"topic": "heatpump/requesttype",
"value": "DOMESTIC HOT WATER",
"date": "2024-02-14T14:31:56Z",
"id": "D33456D6-9361-489D-97E7-C4A082781B7C"
}
2.0.1 Release
Bugfix release: Correctly resubscribes to topics when mqtt server disconnects/reconnects.
2.0.0 Release
As nothing has come up during beta, this is the 2.0.0 release
2.0.0-beta2 release
2nd beta 2.x release
fixed readme and lambda.json
2.x release as it now supports mappings for json files , changed factor to be factor not divisor which makes it incompatible with 1.x json files.
Docker image now provided.
2.0.0-beta1 release
First 2.x release as it now supports mappings for json files , changed factor to be factor not divisor which makes it incompatible with 1.x json files.
Docker image now provided.
1st Release
1.0.0