Sorry finity, even I’m confused by that
Can you post your version with say an extra sensor following it (ie akin to my template ones) ?
Sorry finity, even I’m confused by that
Can you post your version with say an extra sensor following it (ie akin to my template ones) ?
see my edit above.
But here is one I use:
- platform: mqtt
name: "BI Livingroom Motion"
state_topic: blue_iris/lr_cam/motion
payload_on: "on"
payload_off: "off"
device_class: motion
OOPS now I understand what you are asking for. see my other edit above.
so : -
binary_sensor:
- platform: mqtt
name: "BI Livingroom Motion"
state_topic: blue_iris/lr_cam/motion
payload_on: "on"
payload_off: "off"
device_class: motion
- platform: mqtt
name: "BI Kitchen Motion"
state_topic: blue_iris/kn_cam/motion
payload_on: "on"
payload_off: "off"
device_class: motion
- platform: mqtt
name: "BI Bedroom Motion"
state_topic: blue_iris/br_cam/motion
payload_on: "on"
payload_off: "off"
device_class: motion
???
You almost had it:
binary_sensor:
- platform: mqtt
sensors:
freezer_door:
state_topic: tele/rf_wifi_bridgeB2EB97/motion3
value_template: '{{value_json.RfReceived.Data}}'
payload_on: 'E6690A'
payload_off: 'E6690E'
device_class: door
Yeah, sorry. cross posted. see my edits above.
Jesus,
MQTT is a bit of an outlier, all on it’s own
Actually I just looked at the docs. What I wrote was completely wrong. Finity has the correct format.
I’m not really sure where people are getting the idea that you need to add the “sensors:” bit. You don’t. and it will cause errors if you add it.
ah yes, the seed drill, i thought you were referring to seeding as in torrents!
Yeah just corrected myself. Sorry for adding to the confusion.
Ooooh ! did that hurt ?
Did you buy it in as a service or do you subscribe to self flagelation ?
Back to the OP…
if that updated binary sensor doesn’t work (turn on & off with operating the door) then could you post a screenshot of the MQTT messages and payloads (along with a text dump of the MQTT messages/payloads) that you’re seeing when you operate the door?
I’m far from infallible on my good days.
Who isn’t ?
this is what gets sent from the rf-wifi bridge when i open and close the freezer door, so it is working as expected.
I can get it to alarm if I set the automation up using mqtt, but then I can’t turn it off in a usable way.
13:23:13 RUL: RFRECEIVED#DATA=E6690A performs "publish2 /tele/rf_wifi_bridgeB2EB97/motion3 ON"
13:23:13 MQT: /tele/rf_wifi_bridgeB2EB97/motion3 = ON (retained)
13:23:25 MQT: tele/rf_wifi_bridgeB2EB97/RESULT = {"Time":"2020-09-03T13:23:25","RfReceived":{"Sync":14130,"Low":480,"High":1390,"Data":"E6690E","RfKey":"None"}}
13:23:25 RUL: RFRECEIVED#DATA=E6690E performs "publish2 /tele/rf_wifi_bridgeB2EB97/motion3 OFF"
13:23:25 MQT: /tele/rf_wifi_bridgeB2EB97/motion3 = OFF (retained)
OK your template looks correct for the received data.
have you tried to set up the binary sensor from my last suggestion above yet (post 19)?
EDIT:
Oh wait. Your binary sensor is using the wrong topic (needs a ‘/’ at the beginning) and payload (the sensor is already sending “ON” & “OFF” payloads). You shouldn’t need the json template
it should be:
binary_sensor:
- platform: mqtt
name: "freezer_door"
state_topic: /tele/rf_wifi_bridgeB2EB97/motion3
payload_on: 'ON'
payload_off: 'OFF'
device_class: door
Yes, I did, sorry for not mentioning that; it passes config check and I restarted hass, but the alarm doesn’t go off. I also tried looking at it usng dev tools>states and it never changes state when i open the door, so it seems the info is being sent but not received.
Sorry, I just edited my post above. Did you see that?
So ???
Is it okay now ?
If so mark whomever’s post helped you out as the solution (I’d go with finity 's post #19 )
He reached the limit of posts in one day for a new user and can’t respond until later today.
He PM’d me about it but went offline almost immediately after my first reply there so we didn’t get any further. Maybe IRL got in the way…