4CH Pro R2 will not trigger from Homeassistant

Ahmed_I · March 2, 2019, 10:18pm

Hi guys, this is my first post and I have just started using HA.
I currently have 8 sonoff basics running Tasmota and they all are working well but my problem started with the 4CH Pro R2, Flash went well and i can get on to the web interface, entered mqtt like i have with all other basics, adjusted the S6 switch to 1 and flicked all K5 switches to 1. relays work perfectly from the box itself and also from the Web Interface. It also work from TasmoAdmin withen HA. But no matter what i do, I cannot for the life of me get it to run with HA. Used switch, light… you name it.
Here is a copy of my code. Sorry if this post is messed up, mu first time.

  - platform: mqtt
    name: "4Ch Pro1"
    command_topic: "cmnd/Sonoff4CH/power1"
    state_topic: "stat/Sonoff4CH/POWER1"
    payload_on: "ON"
    payload_off: "OFF"
    retain: false

  - platform: mqtt
    name: "4Ch Pro2"
    command_topic: "cmnd/Sonoff4CH/power2"
    state_topic: "stat/Sonoff4CH/POWER2"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: false

Ahmed_I · March 3, 2019, 11:36am

Any idea what I am doing wrong guys.

Thanks

aidbish · March 3, 2019, 11:58am

for the command topic, try setting the power part to capitalised

Ahmed_I · March 3, 2019, 12:15pm

Thank you for the reply, I have tried that too.
What confuse me is that all other Basic sonoffs work perfectly, but this 4ch just will not do anything when i move the switch.

aidbish · March 3, 2019, 12:19pm

on the console on the sonoff, does it have any information as to what topics have been used

aidbish · March 3, 2019, 12:20pm

could you also not enable discovery on the sonoff and then HA will populate automatically?

enter SetOption19 1 in the console to enable it

Ahmed_I · March 3, 2019, 1:02pm

The console reports exactly the topic i used in mqtt on the sonoff portal, I have tried SetOption 19 but HA never discovered it. I also do prefer to do it manual config to have more control.
Also i removed mqtt fully and re configured it just to see if i missed anything.
Also I have re flashed the 4CH Pro
I can see in mqtt log that my 4CH Ip address makes a connection

wills106 · March 3, 2019, 1:04pm

If discovery does not work did you remember to add the discovery option in your HA config?
The bottom two lines.

mqtt:
  broker: !secret host
  port: 1883
  keepalive: 60
  username: !secret mqtt_name
  password: !secret mqtt_pass
  discovery: true
  discovery_prefix: homeassistant

For my non discovery devices this is how mine are set Like @aidbish mention I have POWER1 command part in capitals. I also have the availability_topic set, but I dont know if that is relevant to your issue or not.

  - platform: mqtt
    name: "LivingRoomWallUnit"
    state_topic: "stat/PrStrLivingRoom/POWER1"
    command_topic: "cmnd/PrStrLivingRoom/POWER1"
    availability_topic: "tele/PrStrLivingRoom/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false

  - platform: mqtt
    name: "LivingRoomUSB"
    state_topic: "stat/PrStrLivingRoom/POWER5"
    command_topic: "cmnd/PrStrLivingRoom/POWER5"
    availability_topic: "tele/PrStrLivingRoom/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false
    icon: mdi:usb

Ahmed_I · March 3, 2019, 1:53pm

Thank you guys, I will start testing and I will get back with results!

Ahmed_I · March 3, 2019, 2:59pm

Semi Succses !!
I followed your instructions to add the discovery and sure enough, it got discovered by HA as a switch and a button (BTN).
Now the challenge of adding it manual, I have no clue where the discovered items get stored, to at least read how HA reads it.

Any info will help, thanks again guys.

wills106 · March 3, 2019, 3:02pm

They go into .storage/core.device_registry

But I am changing mine back to non discovered as I can name them better

Ahmed_I · March 3, 2019, 3:04pm

I would also like to change this switch to non discovered, so if you find the way, please share
And thanks again for location.

wills106 · March 3, 2019, 3:07pm

SetOption19 0 in the console on the Sonoff

Ahmed_I · March 3, 2019, 6:06pm

Ok i give up…i did the setting in sonoff console to remove auto detect, and tried to set it up manually again. I get Unavailable in the switch card.
I think it uses another topic name than the mqtt that i have imputed in sonoff console.
wills106 if you get it working on manual, please share

Thanks all and for now it will be on auto discover…

wills106 · March 3, 2019, 6:30pm

Normally you would only config POWER1 to POWER4, but I am using a custom setup with a 5th relay.

configuration.yaml

mqtt:
  broker: !secret host
  port: 1883
  keepalive: 60
  username: !secret mqtt_name
  password: !secret mqtt_pass

#I have part of it setup under the light component
light:

  - platform: mqtt
    name: "LivingRoomWallUnit"
    state_topic: "stat/PrStrLivingRoom/POWER1"
    command_topic: "cmnd/PrStrLivingRoom/POWER1"
    availability_topic: "tele/PrStrLivingRoom/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false

#Other parts are just switches
switch:

  - platform: mqtt
    name: "BobTheSwitch"
    state_topic: "stat/PrStrLivingRoom/POWER4"
    command_topic: "cmnd/PrStrLivingRoom/POWER4"
    availability_topic: "tele/PrStrLivingRoom/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false

  - platform: mqtt
    name: "LivingRoomUSB"
    state_topic: "stat/PrStrLivingRoom/POWER5"
    command_topic: "cmnd/PrStrLivingRoom/POWER5"
    availability_topic: "tele/PrStrLivingRoom/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false
    icon: mdi:usb

automations.yaml

#Check Power Status on startup for Sonoff Devices
- alias: "Power state on HA start-up"
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: mqtt.publish
      data:
        topic: "cmnd/sonoffs/power1"
        payload: ""
    - service: mqtt.publish
      data:
        topic: "cmnd/sonoffs/power2"
        payload: ""
    - service: mqtt.publish
      data:
        topic: "cmnd/sonoffs/Power3"
        payload: "" 
    - service: mqtt.publish
      data:
        topic: "cmnd/sonoffs/power4"
        payload: ""
    - service: mqtt.publish
      data:
        topic: "cmnd/sonoffs/power5"
        payload: ""

The setup on my Sonoff it’s self.

Ahmed_I · March 3, 2019, 8:44pm

Sadly didnt work for me, here is my code for the first switch only

  - platform: mqtt
    name: "Switch1"
    state_topic: "stat/Sonoff4CH/POWER1"
    command_topic: "cmnd/Sonoff4CH/POWER1"
    availability_topic: "tele/Sonoff4CH/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false

wills106 · March 3, 2019, 8:49pm

You have your Full Topic back to front it should be %prefix%/%topic%/

Ahmed_I · March 3, 2019, 8:51pm

hmm how did that happen, let me fix and get back !

Ahmed_I · March 3, 2019, 9:20pm

@wills106 Your a star! Thank you so much, finally its working as it should!!

woooohoooo!

wills106 · March 3, 2019, 9:23pm

Glad you got it sorted.

Have you been trying out different firmware’s on that device? As 2 of my wall switches had the same problem where the Full Topic got reversed for some reason. The only thing that I think could have caused it on mine was swapping about on different firmware’s.