Issue of the topic:
Recently my BasicUI has stopped working with MQTT in/out; it previously worked fine for about 6 months. I cannot control switches, and data is not being displayed from sensors.
However MQTT/Mosquitto is definitely working, I can control devices directly and I can also get telemetry data and display it to BasicUI if parsing through Node-Red to Update the Item?
Only thing I can think of is general updates being applied, Iâve been though all of the configs etc and canât find anything, items etc. havenât changed, PaperUI shows both the Action and Binding for MQTT being active, and json transformations are still active.
Please post configurations (if applicable):
Items configuration related to the issue
example:
Number wemos1_temp "Inside temperature: [%.1f C]"
{ mqtt="<[mosquitto:tele/sonoff_wemos1/SENSOR:state:JSONPATH($.DHT11.Temperature)]"}
Sitemap configuration related to the issue
example
Sorry that âsensorâ one was a test, Iâve just tested again removing and re-adding âwemos1_tempâ from both the items and sitemap, but did not get the same error. But still no resulting data when the telemetry triggers; when I re-activate my Node-Red flow extracting the data from the json from the telemetry and passing it to wemos1_temp it DOES update and display in BasicUI
listening for MQTT topic: tele/sonoff_wemos1/SENSOR
through JSON parser, then extracted via function
var value = msg.payload.DHT11.Temperature
msg.payload = value;
return msg;
Your item config is correct.
The hint about removing the action and reinstalling it is good. It has created problems before.
Do you really need the action?
Thanks vzorglub and opus, I think I thought opusâs post was part of the page footer! Have uninstalled the Action and Binding via PaperUI, rebooted, re-installed, and itâs back working!
Strange that the solution didnât come up in any of my searches, I did update/reinstall mosquitto as that was mentioned elsewhere but that didnât solve the issue.
That said itâs more of a band-aid than a solution, doesnât really solve what the problem was and still seems to be a recurring issue a year later.