Errors after updating to MQTTController build 25139

[cw-kid]

OK so lets say I now have a variable in MSR that contains some data pulled down from a HTTP Request to some online API somewhere.

How can I send that value / information to a Generic IO Sensor in Vera ?

I know how to create a GenericIO device in Vera and I know how to send data to it from a simple HTTP command, for example this command will send the text "Hello World"

http://Vera-IP/port_3480/data_request?id=lu_variableset&DeviceNum=128&serviceId=urn:micasaverde-com:serviceId:GenericSensor1&Variable=CurrentLevel&Value=Hello World

And here is the device in Vera:

But how to create a rule to send the contents of an MSR variable (expression) ?

[LibraSun]

I'm going to assume the data was returned in JSON format? In which case MSR treats that like an object {}, whose keys can be referenced with dot notation.
For example, if your variable respData stored the response {animal:"cat", clothing:"suit", food:"chow"} and you want to send the current value of the "chow" key therein, simply reference that value with respData.chow.

One hurdle you may have to overcome, since the data is being fetched and stored in Rule A, but you want to reference the results in Rule B, is that you'd then have to either (a) store respData as a Global Expression, or (b) create a blank Expression in Rule B, and tell Rule A to [Set Variable] on it.

[LibraSun]

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

But how to create a rule to send the contents of an MSR variable (expression) ?

In case you revised your question, or I misinterpreted it earlier, here goes:

It sounds like you want to send data from MSR to a plug-in / virtual device / sensor over on Vera. Before you begin, go to that "device" > Advanced > Variables and determine which of its variables is intended to receive the data.

Click "EDIT" next to that variable, and look for its complete "service" name in the window; copy that string for use back in MSR.

Close that window on Vera, then head back over to MSR.

In MSR, you will want an [ENTITY ACTION] in the Set Reaction. Choose the target device as the 'Entity' and choose "x_vera_device.set_variable" as the action.

Fill out the three fields, where "service:" and "variable:" come from the string you copied earlier. For "value:" either type a constant (numeric or "text"), or a variable name properly clad in curly brackets ( e.g. ${{respData}} ) so the value gets substituted next time the Rule triggers.

Hope this helps!!

[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.