Gradually turn on lights.

[cw-kid]

@LibraSun

That's great thanks I think you just answered my question, think I know what to do now, I will give it a try.

[cw-kid]

@LibraSun

Its working. I now have my current WAN IP address being sent from MSR to a virtual device (Generic IO Sensor) on Vera.

So now know how to send any data stored in an expression / variable from MSR to a device on Vera !

[cw-kid]

Just updated to today's build, the headers are now saved in that field and no longer vanish.

However I've tried this and no data is being returned / stored

[LibraSun]

Try lowercase "uk" the way they show in the API docs, perhaps?

covid19-api.com

accept: application/json

Response should be in the form:

[
  {
    "country": "UK",
    "code": "GB",
    "confirmed": 4319128,
    "recovered": 3748042,
    "critical": 683,
    "deaths": 126445,
    "latitude": 55.378051,
    "longitude": -3.435973,
    "lastChange": "2021-03-25T18:23:06+01:00",
    "lastUpdate": "2021-03-26T14:15:03+01:00"
  }
]

[cw-kid]

@librasun

Doesn't make any difference with lowercase "uk"

My expression in the rule says "null" and no data is being brought down.

[cw-kid]

Not a coder, but have been messing about with Vera's Generic IO Sensor device and managed to create a new instance that can accept multiple variables.

So if these HTTP request headers start working, I should be able to push some Covid stats to this "Generic Sensor" in Vera as a test.

Does something like this kind of device for displaying data already exist somewhere?

[LibraSun]

@cw-kid said in Replacing SiteSensor Plugin (Vera) with MSR:

Does something like this kind of device for displaying data already exist somewhere?

Yes, the SiteSensor plug-in ( also by @toggledbits ) for Vera.

[LibraSun]

@cw-kid said in Replacing SiteSensor Plugin (Vera) with MSR:

My expression in the rule says "null" and no data is being brought down.

If it's any consolation, their site seems to be throwing a 500 error when I try to visit https://covid19-api.com/country?name=uk&format=json in my browser. How about yours?

[cw-kid]

@librasun said in Replacing SiteSensor Plugin (Vera) with MSR:

If it's any consolation, their site seems to be throwing a 500 error when I try to visit https://covid19-api.com/country?name=uk&format=json in my browser. How about yours?

Same for me also.

However try their CURL command in a terminal window, that works and brings back data OK

[cw-kid]

@librasun said in Replacing SiteSensor Plugin (Vera) with MSR:

Yes, the SiteSensor plug-in ( also by @toggledbits ) for Vera.

But aren't we trying to "replace" that plugin

Some decent Generic IO Sensor virtual device we could create and send data too directly from MSR would be nice.

EDIT: I've just noticed my tweaked GenericIO device does not appear correctly in the Vera mobile app but only on the UI7 web GUI.

[LibraSun]

@cw-kid said in Replacing SiteSensor Plugin (Vera) with MSR:

I've just noticed my tweaked GenericIO device does not appear correctly in the Vera mobile app but only on the UI7 web GUI.

Yes, for this reason we can never truly abandon SiteSensor. Why reinvent the wheel, anyway?
But it does beg the question: Why do you need a generic sensor on your Vera when it could "live" on MSR? After all, is it not just a placeholder for data?

[cw-kid]

@librasun said in Replacing SiteSensor Plugin (Vera) with MSR:

Why do you need a generic sensor on your Vera when it could "live" on MSR?

So I can add that device in to the Home Remote dashboard app also.

If it's only on MSR I don't know how to connect Home Remote to MSR directly.

[LibraSun]

Fair enough (although I'm certain that capacity will come once MSR variables get exposed via the API).

[toggledbits]

@cw-kid said in Replacing SiteSensor Plugin (Vera) with MSR:

no data is being returned / stored

Sheesh. I'll admit I'm a little on edge this morning because we had a major storm roll through last night with some nasty lightning (and a tornado very close to us) and it apparently killed my daily-use laptop (cheap, old, no big loss, just a distraction to recover but they were almost two-for-a-dollar on sleezeBay), so forgive me, but...

There have been no fewer than 10 posts since the above quoted post, and despite my admonition in bold text yesterday in this very thread, not one mention of what may lie in reactor.log.

[cw-kid]

Its working now with the new update and pulling down data OK, thanks.

However I am not able to split out the data in to different global expressions. I think I have it setup correctly but all the global expressions say "null".

RULE:

GLOBAL EXPRESSIONS:

[toggledbits]

Notice the [ that starts the displayed value... it's an array. The { that follows tells you there's an object as the first element of the array. So you need to pluck the first element out of the array, then dereference through it to the key you want, like covidstats[0].critical.

[cw-kid]

@toggledbits said in Replacing SiteSensor Plugin (Vera) with MSR:

covidstats[0].critical

That works thanks, my global expressions are now being populated with data.

I just added covidstats[0]. to all of them in the rule.

[cw-kid]

@toggledbits

How about this data for Carbon from the National Grid ?

I want to pick out "forecast" and "index" data.

(object) {"data":[{"regionid":3,"dnoregion":"NPG North East","shortname":"North East England","postcode":"YO1","data":[{"from":"2021-03-27T13:00Z","to":"2021-03-27T13:30Z","intensity":{"forecast":34,"index":"very low"},"generationmix":[{"fuel":"biomass","perc":24.6},{"fuel":"coal","perc":0},{"fuel":"imports","perc":2.2},{"fuel":"gas","perc":0.2},{"fuel":"nuclear","perc":35.4},{"fuel":"other","perc":0},{"fuel":"hydro","perc":4.5},{"fuel":"solar","perc":6.3},{"fuel":"wind","perc":26.9}]}]}]}

Thanks

[LibraSun]

You can take not-terribly-human-readable blobs like that over to a JSON Pretty Print website (such as https://jsonformatter.org/json-pretty-print), paste it in and hit the "Outline" button, to see how the data looks in its underlying structure.
This allows you to quickly pinpoint the blob.key.subkey.data item you need to pull from in MSR.

Traversing the tree from upper-left to lower-right, I see the first instance of "forcecast" lives inside an overall object {} (I'm naming response), then the first item (i.e. element 0) of an array [] within data, then inside another array within another key called data, then a key called intensity, and finally the key you want, forecast, yielding:
response.data[0].data[0].intensity.forecast

[akbooer]

Remember that openLuup’s Test Lua window, gives you the pretty() function to do the same...

local x  = luup.devices[2]
print(pretty(x))

Gives:

{
  category_num = 0,
  description = "    openLuup",
  device_num_parent = 0,
  device_type = "openLuup",
  embedded = false,
  hidden = false,
  id = "",
  invisible = false,
  ip = "",
  mac = "",
  pass = "",
  room_num = 0,
  subcategory_num = 0,
  udn = "uuid:0058c0cb-c730-209a-50ab-6c88b470a8fd",
  user = ""
}