Virtual Devices Plug-in update (with async HTTP support)
-
I just published an update to my Virtual Devices Plug-in.
What's new in version 1.5:
- support for async HTTP (out of the box on openluup, just download https://github.com/akbooer/openLuup/blob/master/openLuup/http_async.lua and copy with the plug-in files on Vera)
- experimental support for setpoints management in Virtual Heaters (you know, the device will turn itself off if temperature is reached, and automatically on when temperature is not beyond the setpoint)
- external device for temperature in Virtual Heaters (just set urn:bochicchio-com:serviceId:VirtualHeater1/TemperatureDevice variable)
- small fixes, stabilization
Grab your copy from https://github.com/dbochicchio/vera/tree/master/VirtualDevices
As always, 100% local, 100% apps friendly, 100% supported by Alexa (and Google Home, I guess).
-
I just released a new version with
- DoorLock (also, to combine two existing sensor+relay)
- AlarmPanels (if you have an HTTP alarm panel - both with simpliefied (_2) and complete UI (_1) - ALTUI friendly)
- curl support (to send headers, cookies, POST/PUT/whatever)
- new power consumption for lights (to have KWH and total consumption reported under the devices - already configured for shellies)
-
I've just released a new update, fixing power consumption for Shelly devices reporting KWMin instead of KWH.
I've just fixed a couple of other things and since I've received no complaints, I'll probably release 3.0 in the coming weeks. -
Hello @therealdb , good evening!
I recently had to restore my VeraPlus and after that the Virtual Devices plugin stopped to work. I was using the version 2.3 (from the App Store) and when my Vera came back, the devices won't respond to on/off commands... I was wondering if you could help me solve the issue. I'm thinking there is something that got corrupted in Vera that I would need to delete (I've already tried deleting the files), but not sure what..
Thank you! -
@therealdb , thanks for helping me with this! I've installed version 3, but still not working. I'm trying to trigger an ifttt webhook (that somehow worked before) for power on or off (2 different hooks). I've enable the log and this is what I have:
08 01/05/22 11:29:46.177 JobHandler_LuaUPnP::HandleActionRequest device: 196 service: urn:upnp-org:serviceId:Dimming1 action: SetLoadLevelTarget <0x72868520>
08 01/05/22 11:29:46.177 JobHandler_LuaUPnP::HandleActionRequest argument action=SetLoadLevelTarget <0x72868520>
08 01/05/22 11:29:46.177 JobHandler_LuaUPnP::HandleActionRequest argument newLoadlevelTarget=0 <0x72868520>
08 01/05/22 11:29:46.177 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:Dimming1 <0x72868520>
08 01/05/22 11:29:46.178 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=196 <0x72868520>
50 01/05/22 11:29:46.179 luup_log:196: VirtualDevices3.0-beta5@196:actionBrightness(196,"0") <0x72868520>
50 01/05/22 11:29:46.180 luup_log:196: VirtualDevices3.0-beta5@196:New Position: 0 - original 0 <0x72868520>
50 01/05/22 11:29:46.180 luup_log:196: VirtualDevices3.0-beta5@196:setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelStatus","0",196) old value "0" <0x72868520>
50 01/05/22 11:29:46.181 luup_log:196: VirtualDevices3.0-beta5@196:setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","0",196) old value "0" <0x72868520>
50 01/05/22 11:29:46.182 luup_log:196: VirtualDevices3.0-beta5@196:actionPowerInternal(196,false,false) <0x72868520>
50 01/05/22 11:29:46.182 luup_log:196: VirtualDevices3.0-beta5@196:setVar("urn:upnp-org:serviceId:SwitchPower1","Target","0",196) old value "0" <0x72868520>
50 01/05/22 11:29:46.183 luup_log:196: VirtualDevices3.0-beta5@196:setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","0",196) old value "0" <0x72868520>
50 01/05/22 11:29:46.184 luup_log:196: VirtualDevices3.0-beta5@196:sendDeviceCommand("SetPowerOffURL","off",196) <0x72868520>
50 01/05/22 11:29:46.186 luup_log:196: VirtualDevices3.0-beta5@196:sendDeviceCommand.url("https://maker.ifttt.com/trigger/fecha_cortina_1/with/key/XXXXXXXXXXXX") <0x72868520>
02 01/05/22 11:29:46.186 luup_require duplicate http_async <0x72868520>
50 01/05/22 11:29:46.187 luup_log:196: VirtualDevices3.0-beta5@196:httpGet("sync") <0x72868520>
50 01/05/22 11:29:46.237 luup_log:196: VirtualDevices3.0-beta5@196:httpGet("https://maker.ifttt.com/trigger/fecha_cortina_1/with/key/XXXXXXXXXXX", "", "-1", "") <0x72868520>At some point I've noticed it is asking for the http_async, so I've installed it on Vera... but still get the same error as above.
Can you give me some more advice on this?
Thank you very much!
-
Also found this on the log: luup_require [string "..."]:7: unexpected symbol near '<'
-
http_async is optional, it will work regardless. from logs it seems OK. Could you please post more logs? Enable debug mode and post again. I have it working in prod in my system and it's OK, so maybe it's something related to the call. Try also with curl, since it will bypass certains https errors.
-
With curl now I'm getting a error in the address name... probably I'm using the wrong syntax - do you mind sharing the proper way to send the curl command? Thanks!
-
according to the docs, you should use:
curl://-k 'https://maker.ifttt.com/trigger/fecha_cortina_1/with/key/XXXXXXXXXXX'
-
@therealdb Now, it worked perfectly! Thank you!