Plotting graphs with plot.ly service with luup scene using REST API

[korttoma]

You should use username and not <username>. The same goes for the API key.

In UI5 you can test your Lua in Vera from APPS -> Develop Apps -> Test Luup code

Here is a few more examples of variable_get:
local InAirHum = luup.variable_get("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel", 347)
local OutTemp = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1","CurrentTemperature", 229)
local InAirTemp = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1","CurrentTemperature", 346)
local InAirQ = luup.variable_get("urn:upnp-org:serviceId:VContainer1", "Variable1", 348)

[korttoma]

I'm having trouble with one variable to. I would like to have the status of a qubino switch in the same graph.
I tried this:
local VentOn = 100 luup.variable_get("urn:upnp-org:serviceId:BinaryLight1", "Status", 356)

It gives me the value 100 in the graph. Please let me know what this 100 in front of the luup.variable_get does. If I remove it the Luup code fails.

[samppa]

@korttoma said:

I'm having trouble with one variable to. I would like to have the status of a qubino switch in the same graph.
I tried this:
local VentOn = 100 luup.variable_get("urn:upnp-org:serviceId:BinaryLight1", "Status", 356)

It gives me the value 100 in the graph. Please let me know what this 100 in front of the luup.variable_get does. If I remove it the Luup code fails.

Actually there should be asterisk character between 100 and the luup.variable_get and the (forum editor does not show that) since the returned value 1 or 0 is scaled to 100 so try:

local VentOn = 100 * luup.variable_get("urn:upnp-org:serviceId:BinaryLight1", "Status", 356)

Then you get 100 if binary light is on. Remove the 100 if you like it to be 1 or 0.

[samppa]

@Nuubi said:

Uh...oh...still.. do you need to initialize the graph or what? Still not getting this to work, sorry for being such a dummie :-E

You just send the data and the graph named with "filename":"xxxx" gets created if not yet existing.

[korttoma]

@samppa said:

Actually there should be asterisk character between 100 and the luup.variable_get and the (forum editor does not show that) since the returned value 1 or 0 is scaled to 100 so try:

local VentOn = 100 * luup.variable_get("urn:upnp-org:serviceId:BinaryLight1", "Status", 356)
Then you get 100 if binary light is on. Remove the 100 if you like it to be 1 or 0.

I thought it was a multiplier of some kind. Anyhow the code fails allso if I add the asterisk so I thik it has a problem with:

luup.variable_get("urn:upnp-org:serviceId:BinaryLight1", "Status", 356)

Any suggestions what I should try instead? Tried also this but no luck:

luup.variable_get("urn:micasaverde-com:serviceId:BinaryLight1", "Status", 356)

[korttoma]

Had a chat with @BulldogLowell and he taught me that you can hover the mouse on a variable to check the complete variable name so it turned out I had to use the following:

luup.variable_get("urn:micasaverde-com:serviceId:SwitchPower1", "Status", 356)

[Nuubi]

@samppa Yep, works now, thanks!
The problem turned out to be the actual value I wanted to send. Need to figure out how to read MySensors based values in LUA...

[BulldogLowell]

@Nuubi

have you tried luup.inet.wget( )

local brightness = luup.variable_get("urn:upnp-org:serviceId:Dimming1", "LoadLevelStatus", 118)
luup.inet.wget("192.168.1.50//?brightLevel="..brightness.."&", 1)

[korttoma]

Anyone figured out a way to add another variable to an old graph without deleting the file from plot.ly? Seems like it does not include the new variable unless you delete and create a new file.

[samppa]

@korttoma said:

Anyone figured out a way to add another variable to an old graph without deleting the file from plot.ly? Seems like it does not include the new variable unless you delete and create a new file.

I have noticed the same thing; If you want to add a trace you need to delete the file..
So perhaps it is wise to be prepared and add a few extra traces for some future use.

[korttoma]

@samppa said:

perhaps it is wise to be prepared and add a few extra traces for some future use.

Good suggestion for a workaround but it does not seem to pick up name changes for the trace either. Tried also to edit one of the plots on the website but when I wanted to save I could not save the changes to the file used by "Vera". I had to save the file with a different name so no editing seems to be possible.

[korttoma]

Since the nightly heal at 2 in the morning no data is transferred to plot.ly any more :( anyone else see this and know how to solv it?

[Dwalt]

@korttoma

My plots stopped last night as well, last data point transmitted was at 12:03am GMT, but not after a nightly heal.

-Dwalt

[korttoma]

12 GMT is 2 in my timezone so I guess it was just a coincidence that it happened at the time of the heel. Maybe plot.ly blocked us for some reason.

[samppa]

My graphs stopped as well. I have asked what is going on.. Let's see when it gets back up again..

[korttoma]

I sent them some feedback to but have not heard anything yet. Maybe we should try the "Streaming API" instead?

[Dwalt]

@korttoma

I tried to set up a new graph using the REST API and could not get it to register with Plot.ly. Without any explanation from Plot.ly, I tried sending the same data streams to ThingSpeak.com and it set up with out any trouble. The API is slightly different but just as easy to use. I set up a scene to run every 15 minutes with the following code:

-- Get Light Levels
local LR_LIGHT_LEVEL = luup.variable_get("urn:micasaverde-com:serviceId:LightSensor1", "CurrentLevel", 47)
local BR_LIGHT_LEVEL = luup.variable_get("urn:micasaverde-com:serviceId:LightSensor1", "CurrentLevel", 55)

- - Get Temps
local LR_TEMP = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 46)
local BR_TEMP = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 54)
local OUT_TEMP = luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 23)

-- Send data to ThingSpeak.com
local http = require("socket.http")
http.TIMEOUT = 5
result, status = http.request("http://api.thingspeak.com/update?key=Insert Your API Key here&field1="..LR_TEMP.."&field2="..BR_TEMP.."&field3="..OUT_TEMP.."&field4="..LR_LIGHT_LEVEL.."&field5="..BR_LIGHT_LEVEL.."", "run=run") ````

The service has a limited functionality to manipulate your data but the base configuration is easy to tweak and can be made public or private.  See [here for my sample data](https://thingspeak.com/channels/25629).

...plus it is free to use.

[samppa]

@korttoma

Now plot.ly is back up again.
Apparently they upgraded the infrastructure and broke something. Hopefully that does not happen too often..

[korttoma]

Yes, now it is working again. Maybe you should try again @Dwalt ?

[Dwalt]

@korttoma
I noticed it back online right after I posted my Thingspeak scene. I had not deleted my Plot.ly scenes and they continued to send http requests during the outage and when Plot.ly came back online, my data resumed plotting.

I have both services running right now plotting similar data and I will leave them both running to test reliability and quirks. It seems the time reporting drifts a little in Plot.ly. I am also going to test Beebotte.