@hongtat I’ve been trying numerous different things in trying to make some Sonoff dyi mode stuff work. It’s been quite challenging. Just realized there seems to be some truncating occurring sometimes in either the request or the body line on the Gateway interface. Let me illustrate:
After saving the changes and closing out the screen, if you go back into it, the request line seems to have been truncated to what you see on the image. So < “deviceid”:“whatever”} > is missing.
@hongtat , let me try to explain my current problem.
I have a Shelly1 device flashed with Tasmota used as a garage door opener. I have integrated it into SmartThings using your driver.
In order to close the garage door, the duration of the impulse needs to be short, e.g. 0.5 seconds or 1 second. A command such as PulseTime 10 sets it to 1 second and it works fine.
When the power is lost or the hub reboots, it writes a new rule1 to the device, for example:
Rule1 ON Power#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW":"%value%"}} ENDON ON Power1#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW1":"%value%"}} ENDON ON Power2#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW2":"%value%"}} ENDON ON Power3#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW3":"%value%"}} ENDON ON Power4#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW4":"%value%"}} ENDON ON Power5#state DO
12:07:45.472 RUL: Rule1 +WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW5":"%value%"}} ENDON ON Power6#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW6":"%value%"}} ENDON ON Power7#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW7":"%value%"}} ENDON ON Power8#state DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","STS":{"POW8":"%value%"}} ENDON ON Wifi#Connected DO WebQuery %mem1% POST %mem2% {"Mac":"%MACADDR%","cb":"Status 0"} ENDON
That rule completely messes up the PulseTime setting (basically the power stays on for more than 5 seconds), and the result is that the garage door does not close properly (it starts to close, then reverts to open). If I delete the rule or set it to off, everything works normally, but the next time there is a power loss or hub reboot the rule is there again. Can you think of a solution for this annoyance?
@hongtat Follow up to the above. It doesn’t quite work yet. The same effect happens on the ‘Web Query’ line. It truncates it when it reaches the first " char. So upon saving, the actual POST request is not properly saved (that is, is saved truncated)
What you see below is a slightly more complex request, issued to a Tasmota device. The intent is to have the Tasmota issue a HTTP POST via “WebQuery”. so the complete command line should be:
@hongtat Little issue still. Rechecking on the Tasmota console, the driver is NOT sending the whole message, yet. It does show it on the Web Gateway, but it does not send it effectively with the POST request.
I’ve noticed my bulbs color temperature don’t change and the ST device that represents them has a slider that has a temperature range that is way wider than the bulbs can do. If I type in a specific temperature value that is in the bulb range, there doesn’t seem to be any change on the bulb.
I have CCT and RGBW bulbs, running Tasmota v12.
Am I missing something to make the temperature work?
ok guys… i have a new problem.
I am running tasmota 12.2 on a few NodeMCU ESP8266 and contact sensors status updates from the devices to ST app are super delayed.
It takes 2-3 mins (some times longer) for ST App to update the status. The console from the tasmota shows the changes instantly tho.
