logo elektroda
logo elektroda
X
logo elektroda

[Solved] OpenBeken MQTT Issues: Smart Water Valve Commands not Working (Tasmota Syntax & Regular)

leonardocapone 1254 4
ADVERTISEMENT
  • #1 20503118
    leonardocapone
    Level 4  
    Hi there, it's been quite a while I'm trying to get my smart water valve to work through MQTT;
    I can easily get its connection status (online/offline), its actual 1 or 0 status (get) but I see there must be some issue with the commands sending;
    if I use Tasmota syntax "cmnd/MYVALVE/POWER on" I see through the webapp log section that it recognizes it as a tasmota command but it doesn't activate or deactivate my valve;
    whenever I use its "regular" syntax MYVALVE/channel/set:
    if it's been toggled to "ON" and I leave it blank (no payload) the log tab returns with the following:
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT in topic SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT topic not handled: SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT client in mqtt_incoming_data_cb data is for ch 0
    Info:GEN:CHANNEL_Set channel 0 has changed to 0 (flags 0)
    and my valve moves...that means it's toggled (see below picture)
    OpenBeken MQTT Issues: Smart Water Valve Commands not Working (Tasmota Syntax & Regular)

    whenever my valve has been toggled to "0" no matter what payload I use, I have no reaction and log tab shows nothing
    OpenBeken MQTT Issues: Smart Water Valve Commands not Working (Tasmota Syntax & Regular)

    the third condition I noticed is that if my valve it's been toggled to "0", and I leave the syntax empty again, I get the following:
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT in topic SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT topic not handled: SmartWaterValve-1FBE44A7/0/set
    Info:MQTT:MQTT client in mqtt_incoming_data_cb data is for ch 0
    Info:GEN:No change in channel 0 (still set to 0) - ignoring

    valve can be moved easily though the main web interface acting on the "toggle0" button
    OpenBeken MQTT Issues: Smart Water Valve Commands not Working (Tasmota Syntax & Regular)

    HTTP interface works perfectly

    so I guess if there's something I miss in the syntax when I want to send a "1" in place of a "0" through MQTT.

    thanks a lot in advance for your help!


    Leo
  • ADVERTISEMENT
  • Helpful post
    #2 20503378
    p.kaczmarek2
    Moderator Smart Home
    Hello Leo,
    I don't know the environment you are using, but the screenshot attached below:
    leonardocapone wrote:

    whenever my valve has been toggled to "0" no matter what payload I use, I have no reaction and log tab shows nothing
    OpenBeken MQTT Issues: Smart Water Valve Commands not Working (Tasmota Syntax & Regular)

    strongly suggests that you are indeed doing a publish under an incorrect topic:
    
    SmartWaterValve-1FBE44A7/0/set 1
    

    The OpenBeken command expects you to put the following string in the topic:
    
    SmartWaterValve-1FBE44A7/0/set
    

    and then, separately, put 0 or 1 in the payload.

    And it seems that you are trying to put both topic name and payload in the topic name...
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20504103
    leonardocapone
    Level 4  
    Good morning, last evening I was able to have it working;
    FYI the environment I was using to publish and read messages is MQTT Explorer;
    your point was just right; I was using MQTT Explorer the same way my Loxone is working while as you said, payload should be separated from its topic.....that Loxone syntax cost me a headache!!!! ;-)

    anyway, now I have that issue completely fixed with my smart valve perfectly working;

    thanks a lot!
    you have a good day!
    Leo
  • ADVERTISEMENT
  • Helpful post
    #4 20504114
    p.kaczmarek2
    Moderator Smart Home
    Thank you, is there anything I can help you with? Or maybe do you need some special feature?
    Helpful post? Buy me a coffee.
  • #5 20504115
    leonardocapone
    Level 4  
    fixed by separating payload from topic into MQTT Explorer
ADVERTISEMENT