Will know one help me with Binary_sensor state config :(

Configuration
1

please help turn this
S:CLOSED,P:1,N:“Hallway PIR”
S:OPEN,P:1,N:“Hallway PIR”

into a workin

state_topic: Paradox/ZS/Z1
payload_on: “ON”
payload_off: “OFF”

Web Page info below

If successfully connected to your IP150 and MQTT broker, the app will start off by publishing all current zone and partition statuses. The following topics are available (and their names are configurable in the config.ini file):

Zone Statuses:
    Topic: Paradox/ZS/Z1
    (ZS = Zone Statuses; Z = Zone; followed by the number that has changed)
        Payload (example): S:OPEN,P:1,N:"Front PIR"
        (S = Status: OPEN / CLOSE (configurable in the config.ini file); P = Partition number, followed by the zone name)
Alarm Statuses:
    Topic: Paradox/AS/P1
    (AS = Alarm Status (Arm, Disarm, etc.); P = Partition, followed by the partition number)
        Payload (example): Disarmed
        (Possible states = Disarm, Arm, Sleep, Stay, Unsure)

config.ini info below

[MQTT Broker]
IP: 10.0.0.23
Port: 1883

[MQTT Topics]
Topic_Publish_Zone_States = Paradox/ZS
Payload_Publish_Zone_States_1 = OPEN
Payload_Publish_Zone_States_0 = CLOSED
Topic_Publish_Alarm_States = Paradox/AS
Topic_Publish_Siren_Status = Paradox/SS
Topic_Subscribe_Control = Paradox/C/

Random attempts at configuring config.yaml below
Things that do work are Sonoff Master Bed light
Arm and Disarm of alarm but don’t get status updated in home assistant

light:

  • platform: mqtt
    name: “Master Bed”
    state_topic: “stat/sonoff/POWER”
    command_topic: “cmnd/sonoff/power”
    qos: 0
    payload_on: “ON”
    payload_off: “OFF”
    optimistic: false
    retain: true

binary_sensor:

  • platform: mqtt
    name: Theater PIR
    state_topic: “Paradox/ZS/Z3”
    Event_OK: “0”
    Event_open: “1”
    qos: 0
    retain: true

  • platform: mqtt
    name: test
    state_topic: “Paradox/ZS/Z3”
    payload_on: "S:OPEN,P:1,N:“Theater_PIR”
    payload_off: "S:Closed,P:1,N:“Theater_PIR”
    qos: 0
    retain: true

  • platform: mqtt
    name: test1
    state_topic: “Paradox/ZS/Z3”
    payload_on: "S:OPEN,P:1,N:“Theater_PIR”
    payload_off: "S:Closed,P:1,N:“Theater_PIR”
    qos: 0
    retain: true

  • platform: mqtt
    name: test2
    state_topic: “Paradox/ZS/Z3”
    payload_on: “S:OPEN,P:1,N: Theater_PIR”
    payload_off: “S:Closed,P:1,N: Theater_PIR”
    qos: 0
    retain: true

  • platform: mqtt
    name: test4
    state_topic: “Paradox/ZS/Z1”
    payload_on: “OPEN”
    payload_off: “CLOSED”
    qos: 0
    retain: true

  • platform: mqtt
    name: test6
    state_topic: “Paradox/ZS/Z1”
    payload_on: “OPEN”
    payload_off: “CLOSED”
    qos: 0
    retain: true

  • platform: mqtt
    name: test9
    state_topic: “Paradox/ZS/Z1”
    payload_on: “OPEN”
    payload_off: “CLOSED”
    qos: 0
    retain: true

switch:

  • platform: mqtt
    name: “Arm Alarm”
    state_topic: “Paradox/AS/P1”
    command_topic: “Paradox/C/P1/Arm”
    payload_on: “Arm”
    payload_off: “Disarmed”
    qos: 1
    retain: true

  • platform: mqtt
    name: “Disarm Alarm”
    state_topic: “‘Paradox/AS/P1’”
    command_topic: “Paradox/C/P1/Disarm”
    payload_on: “Arm”
    payload_off: “Disarmed”
    qos: 1

This is my MQTT output by using this command mosquitto_sub -d -u pi -P 1234 -t "#"

[CODE]

Client mosqsub/7600-raspberryp sending CONNECT
Client mosqsub/7600-raspberryp received CONNACK
Client mosqsub/7600-raspberryp sending SUBSCRIBE (Mid: 1, Topic: #, QoS: 0)
Client mosqsub/7600-raspberryp received SUBACK
Subscribed (mid: 1): 0
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r1, m0, ‘tele/sonoff/LWT’, … (6 bytes))
Online
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r1, m0, ‘cmnd/sonoff/power’, … (2 bytes))
ON
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r1, m0, ‘Paradox/C/P1/Disarm’, … (3 bytes))
Arm
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r1, m0, ‘Paradox/C/P1/Arm’, … (3 bytes))
Arm
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/C/P1/Arm’, … (3 bytes))
Arm
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (10 bytes))
Exit Delay
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/C/P1/Disarm’, … (3 bytes))
Arm
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (8)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z3’, … (26 bytes))
S:OPEN,P:1,N:“Theater PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (9)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z3’, … (28 bytes))
S:CLOSED,P:1,N:“Theater PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (8)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z1’, … (30 bytes))
S:OPEN,P:1,N:“Living Room PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (9)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z1’, … (32 bytes))
S:CLOSED,P:1,N:“Living Room PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z2’, … (26 bytes))
S:OPEN,P:1,N:“Hallway PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (8)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z2’, … (28 bytes))
S:CLOSED,P:1,N:“Hallway PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z7’, … (30 bytes))
S:OPEN,P:1,N:“PERIMETER DOORS”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z7’, … (32 bytes))
S:CLOSED,P:1,N:“PERIMETER DOORS”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z1’, … (30 bytes))
S:OPEN,P:1,N:“Living Room PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z2’, … (26 bytes))
S:OPEN,P:1,N:“Hallway PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (9)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z2’, … (28 bytes))
S:CLOSED,P:1,N:“Hallway PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z1’, … (32 bytes))
S:CLOSED,P:1,N:“Living Room PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (8)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z3’, … (26 bytes))
S:OPEN,P:1,N:“Theater PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))
Unsure: (9)
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/ZS/Z3’, … (28 bytes))
S:CLOSED,P:1,N:“Theater PIR”
Client mosqsub/7600-raspberryp received PUBLISH (d0, q0, r0, m0, ‘Paradox/AS/P1’, … (11 bytes))

[\CODE]

Ive tried all sorts of random stuff trying to stick to how the working sonoff is configured but just cant work out how to configure the binary sensors to update the states

2

still no luck

  • platform: mqtt
    name: test
    state_topic: “Paradox/ZS”
    payload_on: “OPEN”
    payload_off: “CLOSED”
    qos: 0
    retain: false

    • platform: mqtt
      name: Theater
      state_topic: “ZS/Z3”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

    • platform: mqtt
      name: test2
      state_topic: “Paradox/ZS/Theater_PIR”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

    • platform: mqtt
      name: test4
      state_topic: “Paradox/ZS/Theater PIR”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

    • platform: mqtt
      name: test6
      state_topic: “Paradox/ZS/P1/Z3”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

    • platform: mqtt
      name: test9
      state_topic: “Paradox/ZS/Theater PIR”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

    • platform: mqtt
      name: test88
      state_topic: “Paradox/ZS/Theater_PIR”
      payload_on: “OPEN”
      payload_off: “CLOSED”
      qos: 0
      retain: false

3

I think your topic is “Paradox/ZS/Z3” you only seem to be using parts of it. But I have no real knowledge of MQTT other than getting owntracks to work. I’m going to start playing with it for another project in the next few weeks I think, but I’m not there yet.
Sorry

4

thanks for your reply I am lost lol when it comes to mqtt but am learning a lot just cant get this to work and don’t know why
third week trying lol yawn

Zone Statuses:
Topic: Paradox/ZS/Z1
(ZS = Zone Statuses; Z = Zone; followed by the number that has changed)
Payload (example): S:OPEN,P:1,N:“Front PIR”
(S = Status: OPEN / CLOSE (configurable in the config.ini file); P = Partition number, followed by the zone name)

also tried this format
state_topic: “Paradox/ZS/P1/Theater_PIR”
state_topic: “Paradox/ZS/P1/Z3”

5

maybe my payloads a wrong and that’s why not sure how i would add this payload
S:OPEN,P:1,N:“Front PIR” into it if it just needs a 1 o or open close

payload_on: "Armed"
payload_off: "Disarmed"
payload_on: "0"
payload_off: "1"

payload_on: S:OPEN,P:1,N:"Front PIR" lol just dont work or look correct to me 
payload_off: S:Closed,P:1,N:"Front PIR"
6

You either have to match the payload exactly or use a value_template to extract a certain part of it. So

    payload_on: S:OPEN,P:1,N:"Front PIR"

is the exact match and might work, but it might be confused by the quotes.

Note quotes are not necessary around the payload_on: or payload_off: values so in the simple case

   payload_on: 1

works fine.

I have never had to work with value_template: except to extract json format, so I can’t help there.

7

thanks for your input you are correct it seems to be confused by the quotes.
Ive been able to get some state changes on the Arm and Disarm now but there
payloads are simple for example .

switch:

  • platform: mqtt
    name: “Arm Alarm”
    state_topic: “Paradox/AS/P1”
    command_topic: “Paradox/C/P1/Arm”
    payload_on: “Armed”
    payload_off: “Disarmed”
    qos: 1
    retain: true

this works but the Disarmed status does not I think because
Armed state comes from “Paradox/C/P1/Arm”
and the Disarmed comes from “Paradox/C/P1/Disarm”
anyways my main concentration is on the PIRs states as I mainly care about using the sensors for automation…

So it looks like I have to look at the value_template: thing because this format below does not work like you say
its confused by the quotes.
S:OPEN,P:1,N:“Front PIR”

I have found this inside the python script that creates the weird message above i might see if i can change it in some way to create a more user friendly message in MQTT.

client.publish(Topic_Publish_Zone_States + “/Z” + str(counter), “S:” + newZoneState + “,P:” + ZoneNames[counter2-2] + “,N:” + ZoneNames[counter2-1], qos=0, retain=False)

8

edited to this
client.publish(ZoneNames[counter*2-1], qos=0, retain=False)
now mqtt out put is this
“Theater PIR”
lol not working yet but looking better

9

If you are able to edit the source, you should aim to get the topic to include the location (zone), as this is what HA works best with.

Then you can do

   state_topic: "Paradox/ZS/Theater PIR"
   payload_on: OPEN
   payload_off: CLOSED
10

LOL I WAS LIMITED ON WHAT I COULD CHANGE IT TOO NOW IM WRITING IN CAPS OMG.
anyway ive got it working like this seems to work perfectly so far

  • platform: mqtt
    name: test9
    state_topic: “Paradox/ZS/Z3”
    payload_on: OPEN1"Theater PIR"
    payload_off: CLOSED1"Theater PIR"
    qos: 0
    retain: false