Thanks - really appreciate the info. One thing you can do with Home
Assistant to make sure you are not filling up your DB with lots of sensor
data that is constantly changing is to exclude specific sensors from
recorder - looks something like this:
recorder:
db_url:
mysql://homeassistant:xxxxxxxxxxx@core-mariadb/homeassistant?charset=utf8
purge_keep_days: 2
exclude:
domains:
- automation
- group
- script
- adtimer
entities:
- sun.sun
- sensor.i_air
- sensor.i_bedroom_2_3
- sensor.i_cooktop_oven_a
On Sunday, May 17, 2020 at 3:12:23 PM UTC-4, Greg Troxel wrote:
>
> Something else I forgot to mention:
>
> weewx sending loop packets to mqtt works fine, by many reports on this
> list, as does other things getting those reports.
>
> However, with Home Assistant, what you do is construct a sensor of type
> mqtt, and that sensor sees an udpated value every time it receives a
> notification via MQTT. There is a notion of storing each update in a
> database, so you can graph it, etc.
>
> I am currently sending only archive packets to MQTT, because I don't
> want 43200 temperature datapoints in my HA sqlite3 database, because I
> think it might cause trouble and I don't feel the need. Perhaps that is
> silly of me and it would work 100% fine. And if it were just temp,
> that might be one thing, but there are two temps, two humidities,
> pressure, rain, wind speed/direction and so on so really this is 0.5M
> observations per day.
>
> So, you might want to think of modifying the mqtt sender in weewx to
> send wind every 5 minutes, or when it's higher than the last report, or
> something like that, so you can get the rapid response you want without
> storing tens of thousands of uninteresting data points.
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/34559622-c521-4bac-80b1-b33da0a7643e%40googlegroups.com.
