If that isn’t the issue I would strongly recommend using MQTT Explorer or MQTT.fx to watch all traffic to/from your broker. That will make debugging a lot easier.
Of course, make sure that the Item that is linked to your Channel has an actual value…
As mentioned by @hafniumzinc , try to change the command topic.
I am also not sure if you need the / in the value format as for me it works without, example
I don’t see any errors or useful output. just the changes to the item;
2022-01-11 14:11:51.116 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'NSPanel_NSTemperature' received command 8.7 °C
2022-01-11 14:11:51.116 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'NSPanel_NSTemperature' received command 25
2022-01-11 14:11:51.117 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'NSPanel_NSTemperature' predicted to become 8.7 °C
2022-01-11 14:11:51.118 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'NSPanel_NSTemperature' predicted to become 25
2022-01-11 14:11:51.119 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'NSPanel_NSTemperature' changed from 25 to 8.7 °C
is there something I can do to increase the level of loggging that appears in openhab.log
nothing to do with the the MQTT message that’s trigger on the change
Is there anyway to increasing the logging level about what the channel is doing to make the payload up?
I think the issue was that channel was a Number. It seemed sensible to me, since it was a number I needed to pass to the json, but i think it was struggling in conversions. So I made the channel a String. Then when I set the item linked to the channel (which was pulled from another item which was Temperature) I did this;