It’s on the device side. If you only control the device from the Vera, you will have no problems and this is not needed.
AFAIK, Tasmota has no way to call an URL when a button is pressed (it’s based on MQTT). Your option is to setup a light MQTT bridge for Vera (or use the Vera-MQTT plugin, but I never used it) and relay the commands to the Vera. I have a similar setup (MQTT bridge) for my Wifi led strips and it works very well. I truly hope future Vera firmware will support MQTT natively.
Thats what I’m missing. I guess the state is not that important if I use the toggle http call it will trigger no mater what the state is showing on Vera. Great work thanks for the HTTP integration now I can use Sonoff and other wifi device with my vera.
HI guys, I have a two light globes in a Lounge room, both are running Tasmota, one is RGB the other is binary. Both perform perfectly using HTTP calls manually but when Virtual HTTP calls to turn off the Binary dimmable light it does not turn off, it actually turns on. I have done some traces using wire shark and the only difference i find in the HTTP get command is some reference to http 1.1
Actually I have to apologise, i am sure that during my hours of trouble shooting that one of my first tasks would have been to recreate the device from scratch. However I just did that exact move and the problem is solved. Thank you for your time
Can you describe how you are using an MQTT bridge. I have Mosquito set up in a docker container, with my Tasmota devices pointed to the Mosquito broker. Home Assistant allows one to then use the MQTT broker for status messages, and it works well. But I’d like to keep as much automation as possible in the Vera ecosystem. How are you doing this with Vera?