Virtual HTTP Light Devices, supporting RGB(WW), Dimmers, Switch and much more (Tasmota, ESP*, Shelly)

The http switch is for controlling devices via http requests. You will find the variables you need to set under Advanced - Variables

to control smart life devices with this switch you will need to use the smart life api or ifttt or node-red

https://nodered.org/

The easiest option would be Ifttt as it will not need any coding just create applets for each function you require using webhook and smartlife and create a iftt platform account.

Thanks @therealdb for a great plugin!

Was just wandering if you had any update on retrieving the current status so it is reported correctly in Vera. I know you mentioned you don’t like the idea of polling, have you had any further thoughts?

Thanks. The other mentioned options remains valid. you can poll yourself, or push the status. What are you using?

I have create my own api for controlling Teckin switches, so I have the ability to use either polling or pushing. Does the http device support these now? I didn’t see any configuration options for it.

nope, but you can simply call Vera’s HTTP endpoints in order to do it.

see Virtual HTTP Light Devices, supporting RGB(WW), Dimmers, Switch and much more (Tasmota, ESP*, Shelly) - #86 by Stripe - General Plugin Discussion - Ezlo Community

Sorry, I meant the " Alternate App Store" ALTUI : Alternate App Store - Alternate UI - Ezlo Community

I can help if needed, but I’m not going to put it into the store myself… needs to be originated by the author.

I never did it, but I’ll be more than happy to add this, Opensprinkler and VeraAlexa to AltAppStore. Please @akbooer send me the instructions. Thanks.

Thanks therealdb. If you follow the link to the app store thread, the second post has a detailed description on how to publish a plugin.

1 Like

Indeed so…

What is the VeraAlexa @therealdb?

C

1 Like

Its AlexaTTS, catman you have the plugin installed. lol

2 Likes

DOH! It’s too early!

C

3 Likes

New version on GitHub:

  • more polishing for Dimmers/Lights/RGB
  • Heaters are almost completed

I will update it very soon on App Store and try to submit it to the AltAppStore.

Nice work @therealdb. I find your work to be most help full in making things work with vera.

Some feature requests for future versions -
1 a master device to keep track of all http devces.
2 the ability to edit child device urls in master device.
3 the ability to post requests with json body
{ type: 'smarthome', payload: { entity: 'Lamp', action: 'setColor', value: '#FF00FF' }} with %s subsitutions.

1 and 2 require some work, so it’s a maybe.
3 is doable. I will investigate and plan in a future version.

Thanks for your words.

1 Like

Thinking about this, @ElCid, is GET enough, or do you need to make a POST?
I’m thinking about giving the flexibility to decide the method (defaulting to GET) and payload to send as body. do you also need to send headers?

it might become quite complicated, but I’m exploring this option as we speak.

The option to select GET or POST would be best as some api’s only work with POST requests. As to headers, they may be needed, as in authenication

maybe a change in variables
say-
Url = The url of the request
Request - Get or Post
Type - Form data or json
onData - the form or data body for on request with substitutions .
ToggleData - toggle data
offData - off data
Headers - any headers you may want in json name value form

1 Like

I’m thinking about adding a second variable to every command, called something like TurnOnCommandParameters, and when present, just send it via curl as command line parameters. This should be easier and you can send whatever you want. I will still support replace into the parameters as well.

Since every request should potentially be different, every commands should have this option. Default will be no arguments specified, the HTTP call will be sent via GET as today.

2 Likes

You are correct , it would be better to have seperate requests, more versatile.