BlueIris

[cw-kid]

Temperature Sensors look OK

[toggledbits]

@cw-kid well, this is a bit OK, but hopefully we can just fix it quickly and move on...

Where you select the field value, there's a "+" sign next to the current field value and function, and if you click that, you should be able to choose "Math" and just multiply the value by 100.

[cw-kid]

@toggledbits

Thanks I did try math and * 100 but it kept changing itself back to / 100 instead.

I will have another go.

EDIT:

Got it now, I was tabbing out of that field you have to hit enter instead.

[cw-kid]

@toggledbits

I was looking to use a Thermostat's Current SetPoint value in a panel.

I tried adding these two capabilities so far:

hvac_control and hvac_heating_unit

SetPoint looks to be under the hvac_heating_unit one.

I then tried removing the hvac_control capability from the reactor.yaml file, restarting MSR and refreshing Grafana but it doesn't remove it from that drop down menu, so don't know how to get rid of them.

[toggledbits]

They are displayed on the menu as long as InfluxDB has data in the database. You need to purge all measurements for all entities related to a capability from the database to remove the capability from the menu. This is a good opportunity to mention that you should check your retention policy for the bucket/database in InfluxDB.

[cw-kid]

@toggledbits

I don't know how to do any of that in InfluxDB I will need to read about it.

I can see you have a setting for it in your reactor.yaml file however.

Is that in days then ?

Thanks

[tunnus]

@toggledbits / @cw-kid, sorry to hijack this a bit, but staying closely on the topic.

Running MSR (22004) on Synology Docker and have setup InfluxFeed for InfluxDB (2.1.1), and now it seems to work fine despite yaml giving me headache with incorrect intendation... Capability export is default, so no modifications or filtering done to that in reactor.yaml.

I've also setup Grafana with InfluxDB as a data source (using Flux as query language) and tested the connection, which founds all 3 buckets I have (one for MSR and two default ones).

I don't have any previous experience on Grafana or InfluxDB, so would appreciate if you guys could give some examples of basic queries to get started and to verify there's really data stored... E.g. I have these kind of entities (Vera Plus):

My goal is to migrate away from datamine2 plugin on Vera

[toggledbits]

@cw-kid said in Using Grafana with MSR any tips ?:

Is that in days then ?

No, it's the name of a retention policy you've created in InfluxDB. I'm not an expert on that package, but there are a lot of resources for it and everything I needed to figure out to get started was in the docs and wikis.

[toggledbits]

@tunnus said in Using Grafana with MSR any tips ?:

I don't have any previous experience on Grafana or InfluxDB, so would appreciate if you guys could give some examples of basic queries

I'm not an expert on either InfluxDB or Grafana (and won't be), and I struggled to get going as well, but here are the queries that produced the graphs I posted in another thread

This is the native InfluxDB 2.x graphing module's query/setup, which produced the blue/purple chart:

And here is the Grafana chart query for the same device, for InfluxDB 1.8 and Grafana:

They look a little different because the first was set up for showing a 12 hour time scale, and the second is only 6.

[tunnus]

@toggledbits thanks, I'm using Flux instead of SQL, but managed to get something out:

from(bucket: "msr-data")
  |> range(start: -1d)
  |> filter(fn: (r) => r["_measurement"] == "temperature_sensor")
  |> filter(fn: (r) => r["_field"] == "value")
  |> filter(fn: (r) => r["controller"] == "vera")
  |> yield(name: "_results")

[therealdb]

I’ve built a migrator from datamine format to the format used by MSR in influxdb. If anyone needs it, I could think of releasing it.
I’ve moved 4 years worth of data this way and it’s working beautifully, since I used to run queries with my own engine and now they’re running inside influxdb, that’s very quick, since it’s built for that purpose.