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
I'm using your monitor software for more than a year now and I'm very happy with it. It's been very stable and reliable on my Raspberry Pi Zero W. I'm combining it with Home Assistant via MQTT.
One thing I haven't found out yet is if it's possible to repeat sending the confidence number of each known device. Let's say once every minute. When I'm restarting Home Assistant, my mqtt sensor is reset to "Unavailable". This doesn't change until I restart the Raspberry on which monitor is installed. That way it sends a new confidence state, which is picked up by HA.
It seems that monitor only outputs a MQTT message when the confidence number changes. Can I force monitor to repeat this confidence every minute or so?
Looking forward to your reply.
Roy
The text was updated successfully, but these errors were encountered:
It's on the how-to on the first page.
monitor/first_floor/KNOWN DEVICE STATES
first_floor is the name of your device (raspberry i think is the default name).
You send this mqtt command after a restart
Hi,
I'm using your monitor software for more than a year now and I'm very happy with it. It's been very stable and reliable on my Raspberry Pi Zero W. I'm combining it with Home Assistant via MQTT.
One thing I haven't found out yet is if it's possible to repeat sending the confidence number of each known device. Let's say once every minute. When I'm restarting Home Assistant, my mqtt sensor is reset to "Unavailable". This doesn't change until I restart the Raspberry on which monitor is installed. That way it sends a new confidence state, which is picked up by HA.
It seems that monitor only outputs a MQTT message when the confidence number changes. Can I force monitor to repeat this confidence every minute or so?
Looking forward to your reply.
Roy
The text was updated successfully, but these errors were encountered: