Arming Envisalink panel from MSR

[LibraSun]

This post is deleted!

[LibraSun]

@cw-kid if one wanted to set all 5 parameter values at the same time, using an HTTP call to Vera, could that be done? (If so, I'd need to see a working example of a GET Request that does this.) Or would I have to issue 5 distinct calls to set those variables?

P.S. I see from this old post that I'm not the first one to wonder.

[akbooer]

It’s so trivial to make a custom request handler in Luup... really it’s one of its best feature. So, in this case, indeed, “roll your own” and simply set the required variables per the content of the request.

[cw-kid]

@librasun

I am doing a different http request to Vera to set each variable not one request that set them all.

[LibraSun]

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

@librasun

I am doing a different http request to Vera to set each variable not one request that set them all.

Yeah, something tells me setting more than one at a time isn't possible, anyway. Just thought I'd ask the pros. Thanks!

[gwp1]

@librasun Reviving this a bit because this right here is where I think I'm failing spectacularly.

I'm working with the Ambient API for my weather station via Site Sensor in Vera. This thread has been fantastic at guiding me toward migrating the Site Sensor into MSR. Here's where I'm falling down:

The GET returns expected results. However, I believe I've messed up in creating the expressions for temp, wind speed, wind gust, and solar radiation.

I've entered response[1].lastData.tempf into the ambient_temp field and it returns Last value:(error) Invalid reference to member 1 of null. This is taken right from the Site Sensor recipe where it's working wonderfully so I know I'm probably close. I know the expression logic in MSR is slightly different than that of the Vera Reactor plugin - combined with my almost total befuddlement of proper expressions go isn't helping

Appreciate any guidance!

[Elcid]

should that be response[0].lastData.tempinf

[gwp1]

I thought the same but, after editing, it returned the same error just with ...member 0 of null instead.

[gwp1]

@elcid For full transparency, here's how the ruleset is configured (and it's pulling in expected results:

It's only the latter half that's making me stumble.

[Elcid]

so to set temp expression should be ambient_api[0].lastData.tempinf

[Elcid]

This post is deleted!

[gwp1]

@elcid Whadya know, that did the trick. Interesting to a noob like me how the original Site Sensor in Vera uses response[1].lastData.tempif and that works just fine.

[gwp1]

@toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it? The way I work my Site Sensors is the one for OWM stays deactivated until the one for Ambient throws null at which point the OWM turns on, carrying the load until Ambient throws real data back out there again (at which time OWM shuts back off.)

This saves wasted calls to the API for OWM.

[tunnus]

@gwp1 Put a constraint for the OWM rule, something like "ambient == null"?

[Elcid]

@gwp1 vera uses lua, which arrays count from 1
MSR uses javascript which counts from 0

[gwp1]

@tunnus That would work if I were creating the OWM like I've created the Ambient expressions and ruleset. But @toggledbits has OWM built-in, controlled by reactor.yaml config file. The frequency of calls to the API is configured there in minutes and it creates an entity in the Entities list. As I understand it, the entity is always refreshed data-wise by the frequency of the calls set in reactor.yaml.

[toggledbits]

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

@toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it?

No. Controllers can only be switched on and off via configuration.

[gwp1]

@gwp1I got this all working, Ambient's API and OWM's API all dumping to global expressions.

ambient_api
ambient_temp
ambient_windspeed
ambient_windgust
ambient_solarradiation

openwxmap_api
openwxmap_temp
openwxmap_windspeed
openwxmap_windgust

Everything is glorious. I've planned for when the Ambient API drops (they were having big ol' issues today and into the evening now) it returns a NULL and I flip my HVAC control over to OWM API.

Except... Reactor gets very angry.

Now it's entirely possible this is on me - so let's review:
HVAC has three master rulesets, Cooling, Heating, and Neutral. You'll notice I've broken out the rules into Ambient vs OWM.

The triggers for OWM include a "when Ambient returns NULL" clause, if you will.

These are my two "Site Sensors" in MSR:

This, too, works as intended with OWM sitting idle until Ambient goes "null" and then OWM starts making API calls and populating the global expressions with data.

In real world usage today/this evening the switch happens flawlessly. Where the angry Reactor comes in is after the switch happens. My confusion is around why any ruleset referencing the Ambient data (via global expressions) as a trigger suddenly has all the compile errors, throttling because update rates exceed 60/minute, etc. My expectation is that the "null" will blank the triggers in the ruleset and, since the ruleset is not triggered, it will go dormant until triggered again.

Where have I lost my way?

[tunnus]

@gwp1 I get similar throttling warnings as you do when rules are not able to get values they used to get (via API), but at least you can eliminate those "invalid reference" errors using the following expression structure:

[gwp1]

@tunnus Pardon my ignorance but where do I utilize this structure?