I just noticed that Meteobridge has incorporated direct support for Luftdaten sensors. This must be a newer feature as I had not noticed it before. As you see in the attached images, the Luftdaten can be added as a station and its data shows in the “raw Data” and “Min/Max Data” screens of Meteobridge.
It would be nice to get the Luftdaten sensor data direct from the Meteobridge through the “realtimeMB.txt” file instead of obtaining the data from the internet.
I’m wondering if you were aware of Luftdaten support in Meteobridge, and if you plan to support this in the future.
Yes and no.
The “Yes” is easy. I am aware as a lot of the initial tests were done by Boris at my gear, as I had nearly all devices for the multi-station tests available in September last year.
The “no” is more difficult. The realtime file should not be used for add-ons.
The PWS_Dashboard uses realtime.txt which is a “standard” upload format, used by multiple weather-programs. No problem to use it on a MB although it is not a “built-in”/ API template.
There is currently no API which we can use. Also the available API’s can be used by one receiving website only, otherwise we do get a mess and a lot of problems.
The PWS_Dashboard therefor uses another approach.
We use one of the standard uploads which will be adequate for 80% of the users.
For Meteobridge two standard formats can be used: realtime.txt or clientraw.txt (for MB-nano or larger)
For extra sensor-data (soil sensors, ET a.s.o.) we use an extra-sensor file
For Meteobridge: extra-mb.txt file.
|pm25_crnt1|text|[air0pm-act.1:--]|!
For a user with a luftdaten sensor && Meteobridge we now have 3 options:
[ol]
[li]Most used => direct read from the sensor-database, realtime data only, no MB involved[/li]
[li]extra-mb.txt and use the blocks for station sensor[/li]
[li]Upload from the luftdaten sensor to a special script others/sensorluft.php gives also 24 hour values[/li][/ol]
I think that all options has their pro & cons but one can choose.
Wim
P.S. As it is not widely used, I attach a screenshot how option 3 looks like.
I should’ve guessed that you’re somehow involved with the development and testing of the Meteobridge capabilities!
It’s good to have all the options you’ve listed. I really like option 3 as it provides the high/low values over a 24 hour period. Option 2 would be nice as well since it reduces the station’s dependence to outside data.
It seems like I have a bit of work to do on my site… I’ll have to learn how to generate and use the extra sensor and get Meteobridge to create and setup pwsWD to consume the data for Lufdaten,
Just an FYI;
Boris has just tested processing/parsing the data.json directly from LAN, from a standard nettigo sensor.community sensor-kit on my meteobridge, so it’s right there in the latest mb update. Just pick luftdaten and then fill in your sensor’s LAN IP (assuming that your meteobridge is in the same LAN of course).
There has been an update at December 1/2/3, 2020 to remove the last quircks.
Since then the support has been stable.
Be aware that the sensor mapping has to be set. Tab Staion => last tab: Mapping
And to use with PWS_Dashboard, you need to use an extra-sensor upload file.
Apparently my sensor-kit (this one) did things a little different. Boris has included SHT31 data now, so you’ll see Temperature and Humidity too. Not too bad, actually, since the SHT31 is a pretty good quality sensor (also used for many Davis stations as you probably know…).
