You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great little tool...now I can graph the progress of my BBQ efforts in HomeAssistant!!...anyway, running it as a service (and headless) it's a bit of a mystery what's happening if it doesn't connect, so I created another topic and put in MQTT publications mirroring each log entry so you can see from the MQTT side what's happening. I also made it so that if a probe is null it will still publish (a null value)...in combination with the log messages, if something goes wrong you can use the MQTT output to see problems so you won't be sitting there and thinking all is well when it isn't. If this seems useful I'll create a PR.
The text was updated successfully, but these errors were encountered:
It sounds useful, but publishing null probe values should be an option. I use io.adafruit.com as my MQTT broker, and they limit you to 30 messages a minute on their free tier, so sending empty probe data isn't desirable when using them, but if you are using your own broker that's not a limitation. maybe add a config file option like sendNullProbeValues:trueor something like that.
This is a great little tool...now I can graph the progress of my BBQ efforts in HomeAssistant!!...anyway, running it as a service (and headless) it's a bit of a mystery what's happening if it doesn't connect, so I created another topic and put in MQTT publications mirroring each log entry so you can see from the MQTT side what's happening. I also made it so that if a probe is null it will still publish (a null value)...in combination with the log messages, if something goes wrong you can use the MQTT output to see problems so you won't be sitting there and thinking all is well when it isn't. If this seems useful I'll create a PR.
The text was updated successfully, but these errors were encountered: