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

this is http://192.168.xxx:3480/data_request?id=variableset&output_format=json&DeviceNum=297&serviceId=urn:upnp-org:serviceId:SwitchPower1&Variable=Status&Value=1

Are the DeviceNum different for each channel?

Yep, device 293 and 297. I think Debug should be enabled and some logs shared in order to have a proper triage here.

Sorry for the question, how do I do this?

In the variable section of the vera device, set debugmode to 1
Then in a browser go to http://your_vera_ip/cgi-bin/cmh/log.sh?Device=LuaUPnP for log

1 Like

but when connected to my network at home right?

yes if you use browser.
Or
You can ssh in to the the vera if you know your home IP and password, from a terminal window
ssh root@ip_address
Enter password ( you will not see the characters you enter) hit return.
cd /var/log/cmh (to go to folder)
ls -a (to view contents)
cat LuaUPnP.log (to view log file in terminal)
http://wiki.micasaverde.com/index.php/Logs

It’s easier for me to do when I get home! :slight_smile:

Good afternoon guys!
I’m already at home and I already have Vera’s log!
Did you want the data you need?
I don’t understand any of this! :slight_smile:

No one whats to trawl through a log.

So turn on and off the http devices via vera. Then copy and paste the end of the log , from the time just before you turned on and off the devices. Remember to turn on debug in both Virtual http devices.

Best save to a txt file and zip it , then post it here.

it´s that?Documento.zip (4.5 KB)

the request from 297 is responding 400 bad request. and the \ after the off looks wrong to me.

03/27/20 18:50:49.299  luup_log:297: VirtualBinaryLight: HttpGet: "http://192.168.1.101/relay/1?turn=off\" - 1 - "400" - "Bad turn!" <0x73596520>

where 292 is returning 200 success

50  03/27/20 18:50:35.304  luup_log:292: VirtualBinaryLight: HttpGet: "http://192.168.1.101/relay/0?turn=on" - 1 - "200" - "{\"ison\":true,\"has_timer\":false,\"timer_remaining\":0,\"overpower\":false,\"overtemperature\":false,\"is_valid\":true}" <0x738cc520>

Looks like a invisible caraige return or some thing. How did you input the url?

Sorry No Shelly?
The Link I put on Shelly?

no the link you put in powerOffUrl in device 297.
if you copied and pasted try deleting and typing in manually.

When coding try using a text editor like notpad++ as some word proccessors add invisible characters

I deleted the link on Vera and started writing again and the matter was resolved! :slight_smile: :slight_smile: :slight_smile: :slight_smile:
I do not know what to say! : $
Sorry for all this trouble and for having upset you!

stop using a word processor for coding, as explained above.

No upset, you have to learn some how, mistakes happen.

@therealdb
Just to let you know that the http sensor is working fine.
I have connected a Kanlux ROLF JO, microwave sensor to a shelly 1. this is hidden in my meter cupboard near my front door. Now when anyone walks by the box to get to the door, i get a message from alexa .

I plan to make some mains powered motion sensors for the lighting now. Thanks again for your pluigin

1 Like

I’m more than happy if this sensor is useful to you. I’ll too have a couple of shellies I recycled from an old project and I’ll probably use them in a fancy way like you did.

Has anyone managed to get Shelly status in Vera?

Yes just configure the Shelly on and off urls in the shelly app, you need to update to latest Shelly firmware.

http://192.168.1.110:3480/data_request?id=variableset&DeviceNum=178&serviceId=urn:micasaverde-com:serviceId:SecuritySensor1&Variable=Tripped&Value=1

Edit the serviceId and variable as needed and set the DevicNum