Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Search the Community

Showing results for tags 'pm2.5'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

Found 4 results

  1. This QuickApp reads the PM1, PM2.5, PM4, PM10, Temperature, Humidity and Air Pressure (and calculated absolute Humidity) values directly from a sensor. With this sensor you can measure air quality yourself. This QuickApp will send notifications when PM2.5 or PM10 readings reach a breakpoint. The Air Quality sensor is a DIY setup for less than 50 euro. It is very easy to assemble and ready to make kits are available, see also https://sensor.community/en/sensors/airrohr/ for more info. You can order seperate items from for example AliExpress for the lowest prices, or order a complete set from: https://nettigo.eu/products/sensor-community-kit-sds011-bme280-english-language or https://www.tinytronics.nl/shop/nl/luchtwachters-delft-maak-zelf-een-fijnstofmeter-workshop-kit The Air Quality Sensor has a WiFi interface and Application Programming Interface (API). This QuickApp uses the API to get the measurements available to the Fibaro Homecenter. Changes version 1.2 (11th April 2021) Added support (child devices) for PM1 and PM4 levels (Plantower and Sensirion sensors) Added support for BMP280 sensor Changes version 1.1 (31th Januari 2021) Added support for Plantower Air Quality Sensor (for now without PM1.0) Added Airpressuretext to log of Child Device Airpressure Added Quickapp variable for debug level (1=some, 2=few, 3=all). Recommended default value is 1. Removed QuickApp Variable bme280Sensor (no need for that anymore, works without it) Removed QuickApp Variable path (is now fixed) Changes version 1.0 (23rd January 2021) Added Child Device for Absolute Humidity Added "Refresh" button Changes version 0.5 (23rd October) With the new firmware and API function, solved a small bug in presenting WiFi dBm Changed humidity and air pressure values to zero decimals Added air pressure unit text "hPa" Changed the master device to "Generic Device" Added QuickApp Variable for user defined icon master device Solved a bug preventing creation of QuickApp Variable bme280Sensor Changes version 0.4 (17th October 2020) Added support for BME280 sensor (temperature, humidity and air pressure) Added QuickApp Variable bme280Sensor (true or false) to indicate the presence of a BME280 sensor otherwise a DHT22 sensor is assumed Reduced the amount of labels, now only one label Removed the firmware version from the log under the icon Changes version 0.3 Error message instead of debug message in case of an error Changed method of adding QuickApp variables, so they can be edited Added network error to log (under icon) Changes version 0.2 Changed label6 from "age" to time of the measurement Added automatic creation of child devices for Temperature, Humidity, PM2.5 and PM10 (with great help from @jgab from forum.fibaro.com) Added the value (Temperature, Humidity, PM2.5 and PM10) to the child devices, This can be used in, for instance, extra scenes and shows in the mobile app and dashboard. Added a short text of the air quality (GOOD, SATISFACTORY, etc.) to the icons in the dashboard (with great help of @petergebruers and @10der from forum.fibaro.com) Added the trend (up, down, equal) to the sort text of the air quality My configuration of the DIY air quality sensor: Nova SDS011 air quality sensor NodeMCU ESP8266 V2 opensource WiFi board BME280 temperature, humidity and air pressure sensor See how to simply assemble the air quality sensor yourself: https://sensor.community/en/sensors/airrohr/ See for general informatie about the Air Quality Sensor: https://luftdaten.info See for a map of measurements: https://sensor.community/en/ See for CVS files: https://archive.luftdaten.info See for sources: https://github.com/opendata-stuttgart/ QuickApp variables (mandatory, they will be automatically added with the default values): IPaddress = IP address of your sensor Path = Path behind the IP address, normally /data.json Interval = Number in seconds, the sensor normally is updated every 145 seconds UserID = User id to notify of PM2.5 / PM10 breakpoints bme280Sensor = Use of BME280 temperature, humidity and air pressure sensor, true or false PM2.5 breakpoints 0 - 30 GOOD (Minimal) 31 - 60 SATISFACTORY (Minor breathing discomfort to sensitive people) 61 - 90 MODERATELY POLLUTED Breathing discomfort to asthma patients, elderly and children 91 - 120 POOR (Breathing discomfort to all) 121 - 250 VERY POOR (Respiratory illness on prolonged exposure) 250+ SEVERE (Health impact even on light physical work. Serious impact on people with heart/lung disease) PM10 breakpoints 0 - 50 GOOD (Minimal) 51 - 100 SATISFACTORY (Minor breathing discomport to sensitive people) 101 - 250 MODERATELY POLLUTED Breathing discomfoort to asthma patients, elderly and children 251 - 350 POOR (Breathing discomfort to all) 351 - 430 VERY POOR (Respiratory illness on prolonged exposure) 430+ SEVERE (Health impact even on light physical work. Serious impact on people with heart/lung disease) Download the QuickApp here (download the file and un-zip): https://github.com/GitHub4Eddy/air_quality_sensor/archive/refs/tags/Air_Quality_Sensor_12.zip Or Fibaro Marketplace: https://marketplace.fibaro.com/items/air-quality-sensor How to install: Open the Configuration Interface Go to Settings > Devices Click + Choose Other Device Choose Upload File Choose file from your computer with .fqa
  2. This QuickApp reads the PM2.5, PM10, Temperature, Humidity and Airpressure values directly from a sensor somewhere in this world That sensor doesn't have to be your own sensor, any sensor can be used, just find one in your neighborhood For locating the sensor(ID's) in your neighborhood see: https://sensor.community/en/ Select two (!) SensorID's, one for PM2.5 and PM10 values and one for Temperature, Humidity and Airpressure values The PM2.5, PM10, Temperature, Humidity, Absolute Humidity and Airpressure readings are stored in the value of six (child) devices, so you can read the value from your own scenes This QuickApp will send notifications when PM2.5 or PM10 readings reach a breakpoint (if userID ~= 0) Absolute humidity is the measure of water vapor (moisture) in the air, regardless of temperature. It is expressed as grams of moisture per cubic meter of air (g/m3) See also https://luftdaten.info See also for CVS files: https://archive.luftdaten.info See also https://github.com/opendata-stuttgart/ API documentation: https://github.com/opendata-stuttgart/meta/wiki/EN-APIs QuickApp variables (mandatory, they will be automatically added with the default values): sensorID1 = [number] SensorID for PM2.5 and PM10 values, your own sensor or from someone else, 13463 is an example sensorID2 = [number] SensorID for Temperature, Humidity and Airpressure values, your own sensor or from someone else, 13464 is an example interval = [number] in seconds time to get the sensor data from sensor.community timeout = [number] in seconds for http timeout userID = [number] userID to notify of PM2.5 / PM10 breakpoints debugLevel = [number] Debug logging (1=some, 2=few, 3=all) (default = 1) icon = [numbber] User defined icon number (add the icon via an other device and lookup the number) Version 1.0 (7th February 2021) Added Child Devices for Temperature, Humidity, Absolute Humidity and Airpressure Changed the quickapp variable SensorID to two variables, one for PM values and one for Temperature, Humidity and Airpressure values Added Quickapp variable for debug level (1=some, 2=few, 3=all). Recommended default value is 1. Added QuickApp Variable for user defined icon master device-- Added Airpressure Text in log of Airpressure Child Device Removed QuickApp Variable address, there was no need to change it by user Added values for Temperature, Humidity, Absolute Humidity and Airpressure to the lables Added values for Country, Latitude and Longitude to the labels Added Sensor ID to the log below the value Added "Refresh" button Added extra check for empty data return from Sensor Community Version 0.4 (19th August 2020] Added child devices for PM2.5 and PM10 Added time of measurement, adjusted to your timezone Added Timeout QuickApp variable with high http timeout value to prevent errors Error message instead off debug message in case of an error Changed method of adding QuickApp variables, so they can be edited Version 0.3 (15th June 2020) Link to CVS files added in comment Fixed some typos Fixed breakpoint check 0 - 30 and 0 - 50 notifications Fixed retrieve of json data Version 0.2 (14th June 2020) Link to API documentation added Solved bug / crash: Better selection of the first part of the apiResult Changed some debugging logica Added UserID (mandatory) for sending push notifications Added push notifications based on the PM2.5 and PM10 breakpoints Solved bud / crash if there only was one reading from the api, most of the time there are two readings (last 5 minutes) Version 0.1 (13th June 2020) Initial version Suggestions are welcome. If someone feels the need to improve the QuickApp, you are very welcome. Download the QuickApp here (download the file and un-zip): https://github.com/GitHub4Eddy/sensor_community/archive/sensor_community_1.zip or Fibaro Marketplace: https://marketplace.fibaro.com/items/sensor-community How to install: Open the Configuration Interface Go to Settings > Devices Click + Choose Other Device Choose Upload File Choose file from your computer with .fqa
  3. Witam, Nadchodzi okres grzewczy a tym samym spadnie nam niestety jakość powietrza. Chciałbym mieć możliwość wyświetania danych z najbliższego czujnika Airly: https://map.airly.eu/pl/#latitude=49.95096&longitude=20.03479&id=473 API jest fajnie rozpisane: https://airly.eu/en/api/ Ale Airly używa HTTPS i nie bardzo wiem czy i jak można ściągać dane z API do Urządzenia Virtualnego. Wymyśliłem sobie to tak: local apihost = "airapi.airly.eu" local port = 443 local deviceID = "473" local token = "XXXX" diag = Net.FHttp(apihost, port); response = diag:GET("/v1/sensors/" ..deviceID.. "?apikey=" ..token) result = json.decode(response); fibaro:debug("name: "..result.name) ale nie działa... Jakaś podpowiedź? Jak wyciągnąć takie dane z API po HTTPS? Dzięki z góry za wszelkie podpowiedzi.
  4. Witajcie, Ostatnio dużo mówi się o jakości powietrza, dużo osób interesuje się tematem w swojej okolicy. Widać to choćby poprzez wzrost popularności aplikacji, które pozwalają monitorować powietrze w oparciu o zdefiniowane punkty pomiarowe. Czy jest jakaś szansa żeby przy pomocy Fibaro monitorować jakość powietrza we własnym domu np. w oparciu o czujnik pms5003 lub pms7003? Niestety Netatmo nie pzowala na pomiar tych parametrów. Docelowo można by też prezentować wyniki na wykresach analogicznie do temperatury i zużycia energii.
×
×
  • Create New...