Eric,
There are ‘default’ units for each WeeWX unit system. For the METRIC unit
system the default for altimeter, barometer, and pressure is mbar/hPa. For
additional information see, http://www.weewx.com/docs/customizing.htm#units
rich
On Thursday, 13 May 2021 at 16:26:58 UTC-4
THANKS RICH!!
It really helped to see my actual JSON message get translated into the
weewx.conf file format!
WeeWX got it's first barometer reading shortly after I made the edits and
retstarted weewx at 2:59pm today!
[image: image.png]
*Quick question:*
Since I removed the line "units = hPa"
Using this data point that you posted earlier, I formatted it a bit to
better show the json structure.
21:54:27.154 MQT: sensors/BMP280/SENSOR =
{
"Time":"2021-05-12T21:54:27",
" BMP280":
{
"Temperature":22.0,
"Pressure":990.8
},
"PressureUnit":"hPa",
"TempUnit":"C"
}
I've been looking at Rich Bell's nested json example here:
https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/json-example
He shows a first topic, second topic, third topic, etc.
If you include the time, I think this BMP280 has 5 topics? (Time,
Temperature, Pressure, PressureUnit, TempUnit)
you can try something like this:
# When the json is nested, the delimiter between the hierarchies.
# Default is _.
flatten_delimiter = "_"
# The topics to subscribe to.
[[topics]]
# Units for MQTT payloads without unit value.
# Valid values: US,
I just saw evidence from the mosquitto_sub command, that the BMP280 MQTT
data is making it into the mosquitto broker!
More progress!
I'm still not sure what the Topic and Full Topic fields should be in that
Tasmota MQTT config screen.
weewx@Ubuntu20-WEEWX:~$ mosquitto_sub -h 192.168.7.22 -p
Here's what I've got in my weewx.conf file thus far.
Does this look close to correct, when you compare it to the MQTT message
from the Tasmota log?
21:54:27.154 MQT: sensors/BMP280/SENSOR =
Maybe this line from the Tasmota Console (log) is a clue?
21:54:27.154 MQT: sensors/BMP280/SENSOR =
{"Time":"2021-05-12T21:54:27","BMP280":{"Temperature":22.0,"Pressure":990.8},"PressureUnit":"hPa","TempUnit":"C"}
On Wed, May 12, 2021 at 9:54 PM Eric Koester wrote:
> I've got a BMP280 sensor
I've got a BMP280 sensor (only 2 internal sensors) connected to an ESP-12F
module, running Tasmota firmware.
The example I'm following is a BME280 which has 3 internal sensors.
https://tasmota.github.io/docs/BME280/
Rich Bell mentioned that the BME280 (and BMP280) data is json and nested
and
For those following along, I discovered that the mosquitto_pub &
mosquitto_sub clients were automatically installed when I installed
mosquitto into Ubuntu. Here was the tip-off:
*weewx@Ubuntu20-WEEWX:~$ sudo apt install mosquitto-clients*
*Reading package lists... Done*
*Building dependency
As Greg said, make sure your MQTT infrastructure is up and running
correctly. Since you installed your own broker, a first check is to use
mosquitto_sub and mosquitto_pub to a test topic. Once that is working, use
mosquitto_sub to subscribe to the broker and topic(s) that you want
Eric Koester writes:
> I see I mistyped mosquitto in at least one place above.
> The /etc/mosquitto directory is spelled correctly in my Ubuntu 20 machine.
>
> Ok, on the pid file.
> The version of mosquitto in the Ubuntu 20 deb repo still has provision for
> pid files, so its confusing.
I see I mistyped mosquitto in at least one place above.
The /etc/mosquitto directory is spelled correctly in my Ubuntu 20 machine.
Ok, on the pid file.
The version of mosquitto in the Ubuntu 20 deb repo still has provision for
pid files, so its confusing.
It appears that the mosquitto
mosquitto doesn’t need a pidfile - pidfiles are legacy from init.d (my times!)
> On 12 May 2021, at 1:55 pm, Eric Koester wrote:
>
> I expected a pid file to be created, but it isn't.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
Since I called it out, I expected a pid file to be created, but it isn't.
Here's my current /etc/mosquito/mosquito.conf file:
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example
protocol mqtt
port 1883
allow_anonymous true
pid_file
I'm working around the location of the mosquito.conf file by moving it to
where all the init.d files are looking for it -
/etc/mosquito/mosquitto.conf.
After doing that, the service starts without errors. See:
weewx@Ubuntu20-WEEWX:/etc/rc0.d$ systemctl status mosquitto.service
●
> On 12 May 2021, at 1:22 pm, Eric Koester wrote:
>
> I would bet I need to get mosquitto running properly before I start
> configuring MQTTSubscribe?
yes, it is pointless looking at a mosquitto apps unless mosquitto itself is
working
> I used the example mosquitto.conf file
>
On Tuesday, May 4, 2021 at 3:52:59 PM UTC-5 bell...@gmail.com wrote:
> A few additional things to consider.
> From, https://tasmota.github.io/docs/BME280/, your json data is ‘nested’.
> Meaning the incoming names in MQTTSubscribe will be BME280_Pressure,
> BME280_Temperature, and
A few additional things to consider.
From, https://tasmota.github.io/docs/BME280/, your json data is ‘nested’.
Meaning the incoming names in MQTTSubscribe will be BME280_Pressure,
BME280_Temperature, and BME280_Humidity.
You will want to use the ‘ignore’ option for PressureUnit and TempUnit.
That does sound similar. Thank you for that pointer!
I want to get the Tasmota firmware to output MQTT messags containing the
barometric pressure.
Then, weewx would need to take in that MQTT message and assign the data to
the stock 'barometer' variable from the database schema.
On Tuesday,
I have manage to get a weather station to be the main provider of data to
R-Pi based Weewx installation with add on data into the database coming
from a sensor providing MQTT messages. If that it is similar to what you
are aiming for, maybe this conversation can provide
guidance
> DId you read
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
No, I wanted to make sure MQTT was usable simultaneously with another weewx
"driver", before I spent a lot of time on it.
Thanks for the pointer to service vs. driver configuration!
I'll read through it.
On
Eric Koester writes:
> Thanks for the pointer, Peter.
> I looked through the install instructions and I don't see any mention of
> the weewx.conf file.
DId you read
https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
Agreed that it doesn't say that it is talking about the
Thanks for the pointer, Peter.
I looked through the install instructions and I don't see any mention of
the weewx.conf file.
Does anyone know:
1. does MQTT need to be declared as a station_type in the weewx.conf file?
2. if so, is it ok to have more than one station_type in the weewx.conf
file?
Check this: https://github.com/bellrichm/WeeWX-MQTTSubscribe
On Tuesday, May 4, 2021 at 12:31:55 AM UTC+2 eric.k...@gmail.com wrote:
> I'm currently reading data into weewx using an Acurite Atlas, an RTL-SDR,
> rtl_433, and weewx-sdr.
>
> I'd like to import barometric pressure sensor data into
25 matches
Mail list logo
