MQTT ack=true as it is a system generated foreign message
Closed this issue · 1 comments
Describe the bug
MQTT adapter is fetching power values from SolarAssistant´s MQTT Server
All values written are written with ack=true
The go-e adapter throws in silly log level that this will not be used - for no good reason
To Reproduce
Steps to reproduce the behavior:
- Setup MQTT Client
- Fetch Power Consumption Values from an MQTT Server e.g. SolarAssistant
- Define the corresponding values in go-e adapter
- Change log level to debug
Screenshots & Logfiles
More details and screenshots, and community troubleshooting:
https://forum.iobroker.net/topic/69016/mqtt-ack-false-forcieren/11?_=1697024896489
a user commented over there:
Possibly the Adapter has the (in my eyes wrong approach) that a state describable by the user is entered here in the Config, e.g. 0_userdate.xxxxx. If you write this own state by script there can be ack=false of course.
However, the approach is wrong in my opinion, since for the processing of the state as input with an adapter applies:
Input State === own State of the instance -> ack=false
Input State === foreign State of a foreign instance -> ack=true
There may be exceptions - but I don't see any here.
Versions:
- Adapter version: 4.1.1 of MQTT + 1.0.27 of go-e
- JS-Controller version: 4.0.23
- Node version: 16.19.1
- Operating system: docker on qnap
You can choose if the adapter should read messages with ack or without ack in the settings.
The issue in the forum happens because the content of the object is unexpected wrong. It requires an integer to work on.
I will close this issue here because it does not relay to the go-e adapter.