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

therealdb · October 21, 2020, 6:26pm

Using curl is in my backlog. This should give you the flexibility to send whatever you want.

Are we speaking about a value for the authorization header?

RHCPNG · October 21, 2020, 7:18pm

Yes, that’s correct. And maybe with cookies, although I don’t know if that’s even possible. I was looking at the proxmox api today and that uses cookies.

therealdb · October 22, 2020, 5:40am

Ok, I’ll try to implement curl in a future update. With curl you can definitely send cookies and headers.

RHCPNG · October 22, 2020, 6:26am

Thanks, that’s really great!

therealdb · October 25, 2020, 11:41am

v 2.1 on GitHub => dbochicchio/vera-VirtualDevices: Virtual HTTP Devices plug-in for Vera and openLuup (github.com)

New features

Alarm Partitions
Door Locks
curl support (thanks @RHCPNG for the idea)
power consumption for lights (thanks @HeldeRodrigues for the idea)

HeldeRodrigues · October 25, 2020, 12:52pm

@therealdb
Hi!
I’ve been seeing your description, but I feel really stupid because I don’t know how to configure the new options!
Will the app update itself to the new version?
How do I add the new options?
Sorry for these questions!

RHCPNG · October 25, 2020, 3:27pm

That’s fast! Very cool. I will be trying it out soon.

therealdb · October 25, 2020, 3:46pm

Download the release from GitHub.

Go to your controller via web interface, then Apps, Develop Apps, Luup files. Upload all the files. Leave Restart Luup after upload checked. Wait for luup engine to reload. Go to your device, then Advanced.

Set SetUpdateMetersURL to http://youshellyIP/status

The other variables are already set for a Shelly by default. Just update MeterUpdate (in seconds) if you want to change the update frequency.

Reload luup engine again (ie: go to Apps, Develop Apps, Test luup code and insert luup.reload() and press OK). This should be enough

By default it will meause the first relay, just replace [1] with [2] in both MeterPowerFormat and MeterTotalFormat and you should be ready to change the relay.

It’s experimental, but it should work.

ElCid · October 30, 2020, 4:14pm

@therealdb
Hi.

Just moving to v2 on vera. I am a little confused about this section in the read me.
" Be sure to use the new D_Virtual*.xml files as device_json.

Go to every device you want to adopt as children, and

change device_json to the new D_Virtual.xml* version"

do you man the device json or the device file?

therealdb · October 30, 2020, 4:27pm

oh, you’re right. It’s confusing. I’ll fix it.

So, device_file (not device_file) should be set to D_VirtualBinaryLight1.xml, if it’s a binary light, and so on.

Thanks for noticing @ElCid!

ElCid · October 30, 2020, 4:33pm

One more thing that slightly confused me.
Is D_Virtual*.xml only in the child devices or also in the master?

therealdb · October 30, 2020, 5:17pm

both, otherwise they’ll act in legacy mode.

ElCid · October 31, 2020, 10:33pm

hi @therealdb
i was looking at status json data (working on an node-red integration with vera.
I noticed This entry
“Device: 178. Fail to load implementation file D_VirtualMotionSensor1.xml”

In this location startup.tasks

There are 4 array items relating to 4 virtualhttp devices set up as motion sensors. it seems there is no D_VirtualMotionSensor1.xml.

Is this a bug as devices appear to work.

therealdb · November 1, 2020, 6:50am

Sensors are still on legacy mode. I have to package the device files for all of them and I’m planning this for next release.

ElCid · November 1, 2020, 11:16am

Ok i have put them back in legacy mode, as the devices were not updating in OpenLuup via VeraBridge.

cubs2b23 · November 1, 2020, 7:19pm

I have the On/Off working just fine for a Shelly rgbw2 that I just installed. Is there a way to use the Vera UI’s dimmer slider to set the level on the Shelly as well? I see the SetBrightnessURL in the device’s variables but what goes there?

therealdb · November 2, 2020, 6:27am

Yes. Set it to

http://192.168.1.XX/color/0?turn=on&gain=%s

Crille · November 2, 2020, 10:46pm

@therealdb Since you asked I actually have a feature request if it’s possible and you consider it to be useful.

Option to add multiple endpoints for on/off/dimming etc.

Use case: Group physical HTTP devices to act as 1 device.

Example:

You have a fixture with 3 smart bulbs that you have no need to control individually.
You have a lot of cameras that you arm with HTTP calls when house mode change, no need to arm them individually.

Today I do this with Switchboard and Luup code in scenes, but would be neat to have that integrated and sent async in the virtual device instead.

therealdb · November 3, 2020, 5:13am

Good suggestion. I’ll add it soon.

I think a good approach is to write a command per line. What do you think?

Crille · November 3, 2020, 8:43am

Thank you! Yes one per line seems like a good idea.