-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mqtt] not reliable after upgrade to 4.2.0 "Command 'NULL' from channel [...] not supported" #17533
Comments
Not really sure what is going on there, might be related to the chaining, might be something different. I suspect it is rather introduced into 4.2.0 and not in in 4.2.2 as the changelog does not show something i can tie to this. Maybe @jimtng has some thoughts on this issue? |
I went back step by step through the releases and can confirm that the warnings occur with 4.2.0. On 4.1.3 everything is working well. I will fix the title. |
I've just created a minimal example and updated the report with which you can reproduce the behaviour. |
Expected Behavior
MQTT plugin isn't treat a message/field/command as NULL.
Current Behavior
I have the following MQTT thing configured:
When I send the following message a second time:
... the following WARN messages appear in the log:
Steps to Reproduce (for Bugs)
sudo docker network create openhab-test
conf/things
(file attached)tele/wp-zigbee-coordinator-01/SENSOR
Your Environment
files.zip
The text was updated successfully, but these errors were encountered: