pimatic sonoff bridge tasmota mqtt switch

Samuel Warkentin

Hey,

with an python script i send cmnd/sonoff/RfKey1 to sonoff bridge and then switchs the light on. with cmnd/sonoff/RfKey2 switchts the light off.

i dont know what pimatic must set …
this doenst work for me

    {
      "topic": "cmnd/sonoff",
      "onMessage": "RfKey1",
      "offMessage": "RfKey2",
      "id": "lampe-buro",
      "name": "Lampe Büro",
      "class": "MqttSwitch",
      "stateTopic": "stat/sonoff/RESULT"
    }

any idea?

mwittig

@samuel-warkentin If you have pimatic-mqtt installed and configured you can create a MQTT Switch Device using the web frontend. The switch should have the following properties, for example:

{
  "name": "Your Choice",
  "id": "yourChoice",
  "class": "MqttSwitch",
  "topic": "cmnd/sonoff-bk/power",
  "stateTopic": "stat/sonoff-bk/POWER"
  "onMessage": "1",
  "offMessage": "0"
}

Samuel Warkentin

@mwittig
Re: pimatic sonoff bridge tasmota mqtt switch

i doesnt work …

21:39:49 MQT: stat/sonoff/RESULT = {"Command":"Unknown"}

sonoff rf bridge is an 433 mhz reciever/senderans has 16 RfKeys.

wenn i manually send message it works, but with pimatic not.

cmnd/sonoff/RfKey1 = On i my case
cmnd/sonoff/RfKey2 = Off i my case

Samuel Warkentin

this works, but it is not a switch …

    {
      "buttons": [
        {
          "id": "on",
          "text": "On",
          "topic": "cmnd/sonoff/RfKey1"
        },
        {
          "id": "off",
          "text": "Off",
          "topic": "cmnd/sonoff/RfKey2"
        }
      ],
      "id": "test",
      "name": "test",
      "class": "MqttButtons"
    }

Thrusty

@samuel-warkentin
I have ON and OFF registered there. So all big letters. This is how my mqtt-switches work.
Here is the complete device

{
      "brokerId": "192.168.178.22",
      "topic": "cmnd/4ch18/POWER3",
      "onMessage": "ON",
      "offMessage": "OFF",
      "stateTopic": "stat/4ch18/POWER3",
      "echo": {
        "additionalNames": [
          "4led"
        ],
        "active": true
      },
      "id": "eingang-4led",
      "name": "Eingang 4LED",
      "class": "MqttSwitch"
    },

Samuel Warkentin

Hey,

the switch for rfbridge must send to different route.
First route

cmnd/sonoff/RfKey

Second Route

cmnd/sonoff/RfKey2

For every key must use different payload.
0=send learned key
2=lern new kyey

Thrusty

@samuel-warkentin
Oh, I don’t think that’s gonna work with mqtt-switch. Had rf-Bridge read over.
One possibility would be DummySwitch and two rules. One rules for ON and a second for OFF.
One problem could be the status of the lamp. But a feedback doesn’t send 433mhz anyway.
But the DummySwitch shows you fake status.

daddycool

@mwittig
thanks btw - this was the essential hint for me to get it working. I was messing around with ‘stat/sonoff…’ for the topic too and this can’t work as i see. Now all is fine, but just wondering in case for the TH16 - do i have to ‘split’ it’s functions like an mqtt-switch-device for switching and another mqtt-sensor-device for Temperature and Humidity?

Thrusty

@daddycool
MqttSwitch, first switch of Sonoff 4CH:

    {
      "brokerId": "192.168.178.22",
      "topic": "cmnd/4ch19/POWER1",
      "onMessage": "ON",
      "offMessage": "OFF",
      "stateTopic": "stat/4ch19/POWER1",
      "echo": {
        "additionalNames": []
      },
      "id": "terrasse1",
      "name": "Terrasse1",
      "class": "MqttSwitch"
    },

MqttSensor with BME280 on same Sonoff 4CH

  {
      "brokerId": "192.168.178.22",
      "attributes": [
        {
          "name": "BME280.Pressure",
          "topic": "tele/4ch19/SENSOR",
          "type": "number",
          "unit": "hPa",
          "acronym": "P",
          "messageMap": {}
        },
        {
          "name": "BME280.Humidity",
          "topic": "tele/4ch19/SENSOR",
          "type": "number",
          "unit": "%",
          "acronym": "rH",
          "messageMap": {}
        },
        {
          "name": "BME280.Temperature",
          "topic": "tele/4ch19/SENSOR",
          "type": "number",
          "unit": "°C",
          "acronym": "T",
          "messageMap": {}
        }
      ],
      "xAttributeOptions": [],
      "echo": {
        "additionalNames": []
      },
      "id": "4ch-sensor",
      "name": "4CH Sensor",
      "class": "MqttSensor"
    },

daddycool

Thanks a lot for your help @Thrusty , finally i could adopt it to my TH16/AM2301:

 {
      "brokerId": "MosquittoSRV",
      "topic": "cmnd/sonoff/power",
      "id": "sonoffth16",
      "name": "SonoffTH16",
      "class": "MqttSwitch",
      "onMessage": "1",
      "offMessage": "0",
      "stateTopic": "stat/sonoff/POWER"
    },
    {
      "brokerId": "MosquittoSRV",
      "attributes": [
        {
          "name": "AM2301.Temperature",
          "topic": "tele/sonoff/SENSOR",
          "type": "number",
          "unit": "°C",
          "acronym": "Temp",
          "messageMap": {}
        },
        {
          "name": "AM2301.Humidity",
          "topic": "tele/sonoff/SENSOR",
          "type": "number",
          "unit": "%",
          "acronym": "LF",
          "messageMap": {}
        },
       ],
      "xAttributeOptions": [],
      "id": "sonoffth16-temp-rlf",
      "name": "SonoffTH16 Temp/RLF",
      "class": "MqttSensor"
    }

btw: couldn’t get it work for the Timestamp like this - here’s the console output:

MQT: tele/sonoff/SENSOR = {"Time":"2019-04-10T20:20:41","AM2301":{"Temperature":21.9,"Humidity":39.3},"TempUnit":"C"}

so i created another atrribute called sonoff.time using the same topic with a string-type var - but it’s not showing off in pimatic…

Thrusty

@daddycool
It looks like tasmota not sending the timestamp automatically.
You can do it with a rule in the TH16, I read.
Look here
https://github.com/arendst/Sonoff-Tasmota/issues/4770
Then the sonoff sends the time stamp via mqtt.

Then you can query with mosquitto_sub -v -t \#.
Then you should see what you have to put in as an attribute.

I have not tried it. Write if it works.

daddycool

@thrusty
Thanks - it worked for me like that:

19:59:47 CMD: rule 1
19:59:47 SRC: WebConsole from 192.168.0.166
19:59:47 RSL: Group 0, Index 1, Command RULE, Data 1
19:59:47 MQT: stat/sonoff/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Free":436,"Rules":"on power1#state=1 do publish stat/sonoff/TIME {"Time":"%timestamp%"} endon "}
20:01:02 HTP: Main Menu
20:01:05 HTP: Console
20:01:08 HTP: Main Menu
20:01:10 SRC: WebGui from 192.168.0.166
20:01:10 MQT: stat/sonoff/RESULT = {"POWER":"ON"}
20:01:10 MQT: stat/sonoff/POWER = ON
20:01:10 RUL: POWER1#STATE=1 performs "publish stat/sonoff/TIME {"Time":"2019-04-15T20:01:10"}"
20:01:10 SRC: Rule
20:01:10 RSL: Group 0, Index 1, Command PUBLISH, Data stat/sonoff/TIME {"Time":"2019-04-15T20:01:10"}
20:01:10 MQT: stat/sonoff/TIME = {"Time":"2019-04-15T20:01:10"}

Mosquitto is doing fine too:

Client mosqsub|13000-raspberry received PUBLISH (d0, q0, r0, m0, 'stat/sonoff/POWER', ... (2 bytes))
stat/sonoff/POWER ON
Client mosqsub|13000-raspberry received PUBLISH (d0, q0, r0, m0, 'stat/sonoff/TIME', ... (30 bytes))
stat/sonoff/TIME {"Time":"2019-04-15T20:01:10"}

the only issue for now is that it’s ‘One-Shot’ even if it says it’s not (“Once”:“OFF”)