Hi all, I want to replace my existing shutter switches (433mHz) with WiFi shutter switches. For this purpose I bought a roller shutter switch at AliExpress for testing. This shutter switch is controlled by an ESP8266, so you can flash this with tasmota to operate it cloudfree. So far so good.
Now I wanted to integrate the flashed shutter switch via mqtt into pimatic. Unfortunately I found out that the mqtt-shutter-device supports only one topic. The logic of tasmota uses two topics ( …/…/POWER1 and …/…/POWER2) for switching two relays. So one relay for up and the other for down.
Does anyone have an idea how I can realize two topics in one device? (I fear that it is not possible)
Or is there a way to adapt the mqtt plugin to handle the tasmota logic for shutter?
-
wifi shutter device with mqtt and tasmota
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
Hello,
i have shellys to controll my Shutter, the topic my devices via mqtt. -
@wuschel
Thank you for your reply.
What firmware do you have on the shellys? I guess it is not tasmota."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
i use the original latest FW, only shelly1 is flashed with tasmota.
-
It looks like no one has used this constellation yet!? Or given up because a cloud login is necessary.
If I use shelly 2.5, then it unfortunately also only works with the original firmware, so confirmed it to me @wuschel. But for this you have to register with a cloud.
Is there really no other way to use such shutters?
Unfortunately I am not able to code and also with scripts my possibilities are limited.
@bertreb is it very hard and complicated to program a new device selector for the mqtt plugin?
I have no other idea how to bring two mqtt topics in one pimatic device.
I had tried some things with option of rules integrated in tasmota. But with this I didn’t get a successful result."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
@Thrusty, on the original question, did you try a mqtt-buttons device?
A button for ‘open’, a button for ‘close’ and a button for 'stop’
If you know the topic and payloads (the 3 commands) for your ‘esp8266’ device, the configuration is not complex -
@bertreb The best solution for me would be a mqtt shutter device. Unfortunately, I do not know what effort that generates.
Optimal would be a device that can manage two topics and can also display the status. As the respective position of the shutter. The basic problem is that I have two mqtt topics."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
@bertreb said in wifi shutter device with mqtt and tasmota:
You can configure different topic per button.
I have no idea how to do this at the moment.
Do you know tasmota and the logic behind it?"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
@bertreb
But such a wall plug needs only one topic to switch. A shutter has two relays in one device and needs two topics.
The status or a sensor for values has another topic, that is clear. But unfortunately this is not used to operate the shutter."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
So a solution could be:
- 1 mqtt-switch for the up motor
- 1 mqtt-switch for the down motor
- 1 mqtt-sensor for the position, etc values
- a Buttons device with 3 buttons (up, down, stop)
- 3 rules:
- rule stop: when button up is pressed then stop motor down start motor up for xx seconds
- rule down: when button down is pressed then stop motor up and start motor down for xx seconds
- rule stop: when button stop is pressed then stop motor up and stop motor down
The mqtt-sensor values can be used in the rules. In the gui you only need the buttons device.
-
Ok, I have to look at that first in peace and with some time. That could perhaps be a solution. First of all, thank you for your efforts. I will get back to you. With or without success.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
Hallo,
I use the SONOFF Dual R2 with Tasmota. I not use the shutter funktion, I only use “interlock” with the Tasmota firmware.
Here the device in pimatic“topic”: “cmnd/jschlaf/Backlog”,
“upMessage”: “Power1 on”,
“downMessage”: “Power2 on”,
“stopMessage”: “Power0 off”,
“rollingTime”: 20,
“stateTopic”: “/stat/jschlaf/RESULT”,
“echo”: {
“additionalNames”: []
},
“id”: “rollo-schlafzimmer”,
“name”: “Rollo Schlafzimmer”,
“class”: “MqttShutter”Greetings
-
@bertreb
I have now realized this according to your suggestion. I was somehow missing the right approach, but now it works.
I have additionally used a mqtt-sensor for the percentage display of the shutter. and furthermore a mqtt-dimmer which now works as a slider. Basically both works. Unfortunately I get error messages from the mqtt-slider when the shutter is moving. Can you tell me which entry I would still have to make on the device to fix this?"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
@bertreb
The error message is the same as shown in the picture. Every time the tasmota software sends a position change, an error message is displayed.error [pimatic-mqtt]: value: NaN is out of range
Tasmota Console
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
No 100. But I just tried 99. The same error message appears.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)