MQTT configuration question

[toggledbits]

There's a OWMWeatherController built-in to MSR. If you're going to use OpenWeatherMap, that's a more efficient way to go about it. For other API integrations, the method described above is useful.

[gwp1]

@toggledbits I dug about a bit and found this in the manual. How would I invoke this, I don't see anything in Entities (post-config)?

[toggledbits]

In your reactor.yaml, did you switch the "enabled" setting for the weather to enabled? Maybe show/post your config section for that controller?

[gwp1]

sigh

Wow. More coffee required. Yeah, it was set to false. Correction made. I now have entity OWM Weather > weather.system > sys_system.state (primary)

[toggledbits]

Great. If you filter the "Entities" list (left nav) for the "wx" capability, you should find the entity that contains your local weather data.

[LibraSun]

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

There's a OWMWeatherController built-in to MSR.

Could you possibly shoe-horn lat, lon, location (city) name, time zone, etc. with that object? Or do those values already surface elsewhere in MSR?

I'd be interested in using them as part of my "Weekly Report" quasi-mailmerge notifications.

[LibraSun]

OPENWEATHER PRO TIP

Users of MSR's built-in weather object ('weather>default') may wish to know how to convert the value in wx.icon to an actual thumbnail image.

Here's how:
Suppose the value stored in that variable is '01d'
Simply prepend 'http://openweathermap.org/img/wn/' to the beginning, and append '.png' to the end. (You can enlarge the image by including '@2x', '@4x', etc. before the '.png'!)

Better still, gather all of the icons files from https://openweathermap.org/weather-conditions and host them on your own local server/repo, to spare OWx from excess bandwidth. You can also grab their table of "Weather Condition Codes" containing a description of each possible value in wx.condition_code.

These tirbits would be helpful in designing a dynamic "Weather" tile for the MSR Dashboard feature!!

EXAMPLES:
Condition: 01d = "Clear Sky (day)"
Condition: 04n = "Clouds (night)"

[LibraSun]

FEATURE REQUEST

Add "Solar Noon" to Sunrise/Sunset trigger in MSR, even if it's just derived as "halfway point between Sunrise and Sunset"
(No need for "Civil Noon" since that's automatically 12:00pm)

Could be useful for farms, solar installations, etc.

[toggledbits]

That's easy, it has it, so all I need to do is add the menu item to the UI.

[gwp1]

@toggledbits I found this:

Oddly, the historical is returning Melgrove lol I left the config so that it would pull from the default location which is using lat/long.

[toggledbits]

I'm not sure where you're going with this post? Are you reporting a problem?

[gwp1]

@toggledbits I guess I am - unless I'm misreading the docs. I believe to have OWM set to use the default location of MSR which is Hanahan SC, not Melgrove Someplace.

I don't want to file a bug until I'm sure it's MSR and not me.

[toggledbits]

OK. In order to sort that out, I need to see your configuration for both the default system location and OWM. Post here or PM is fine.

[gwp1]

@toggledbits Posted via PM.

[toggledbits]

OK. Looks like all is good, OWM is just returning an odd place name (who knows what data they sourced that from), and since you are using "default" configuration (home location from Reactor main config), it's using OWM's returned name for the entity name. If you do a custom location in the OWM config, you can set the name by adding the "name" to the custom config. I'm going to extend that behavior to the default location config as well, and that will be in today's build. If you want to get it fixed before that, just add a location to your OWMController config section:

  - id: weather
    enabled: true
    implementation: OWMWeatherController
    name: OWM Weather
    config:
      appid: "yourappidhere"
      locations:
        - id: home
          name: "My Custom Place Name"
          latitude: nn.nnnnnn
          longitude: nn.nnnnnn

[gwp1]

@toggledbits I'm a few nightly builds behind so I'll wait until you have tonight's out. Thanks!

[cw-kid]

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

My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR

I never used SiteSensor plugin for Vera before.

Thanks for the MSR example you wrote.

I wanted to try this out and found this Covid-19 API here.

However the http command they give doesn't seem to return any results data, either just in the web browser or in my MSR rule.

https://covid19-api.com/country?name=UK&format=json

The curl command does work OK however

curl -X GET "https://covid19-api.com/country?name=UK&format=json" -H "accept: application/json"

How do I specify the application/json in the MSR rule? Assuming the problem is related to that.

[toggledbits]

Same way. One header per line in that field.

[cw-kid]

@toggledbits

In the "Request Headers" field in the "Set Reaction" I have tried the following:

Accept: application/json

and tried:

Content-Type: application/json

It allows me to save the rule but when I go back in to the rule that field is empty again and its not collecting the response data in to my empty expression / variable.

[toggledbits]

So there are two separate issues here:

1. First, we need to figure out if the UI is correctly storing the headers or not, and if the problem is merely that it is not restoring/displaying them correctly when you go back into the editor. The check for that is to go into the reaction, add the headers, and save. Then, open the rule status view and it will show you the rule ID underneath the rule condition status and expressions. Go to your reactor/storage/rules directory, and grab the same-named file (with .json suffix) and post it here. Let's see what's being stored.

2. Look at the logs to see where the reaction is running and what the request is doing. There may be errors logged.

It's entirely possible that the problem is 1, 2, or even both.