FIBARO Choice

Created At

Apr 26, 2020

Last Update

Sep 30, 2022

Platforms

HC 3 Lite, Z-box Hub, Yubii Home, Venture WISE, HC 3

Views

17827

Download

2882

Type Quick App

QuickApp module to integrate of Netatmo climate devices.

It has support for Main module, Outdoor modules and Indoor modules, Rain gauge and Smart anemometer. It creates child devices (Temperature Sensors, Humidity Sensors, CO2 Sensors, Pressure Sensors, Noise sensors, Rain and Wind sensors) automatically based on information gathered from Netatmo API.

To use it you need to import attached .fqa file into HC3 and provide tokens (access_token and refresh_token) from Netatmo API. To generate these tokens please visit site https://gsmart.pl/netatmo/ and follow instructions.

Other variables:

  • battery_allone - can be "true" or "false" - to choose between battery interface on dedicated child devices or directly on child devices

These values are in "Variables" tab on imported device. Click on Pencil, fill data for corresponding variables and click "Save". After that you need to create child devices. To do that you have to go to the "Edit & Preview" tab and click on "Get Devices" button.

If tokens are ok after few seconds you should have created all linked devices for found Netatmo modules. Values for these devices are refreshed every 10s after values updated in Netatmo cloud (more or less at 10min period). QA also has a "Get Measurements" button to manually refresh data.

Important note: 5.030 or newer firmware version on HC3 is needed.

Changelog:

v2.6 - 09/2022 (GSmart)

  • changed authorization method with Netatmo API (required by Netatmo servers)

v2.5.1 - 03/2021 (GSmart+Lazer)

  • FIX QuickApp hang after HC3's upgrade to 5.063 firmware
  • Added Czech translation (thanks to petrkl12)
  • Minor fixes & enhancements

v2.5 - 07/2020 (Lazer)

  • Fix QuickApp crash in case weather station has no additional module

v2.4 - 07/2020 (Lazer)

  • Add variable to choose between battery interface on dedicated child devices or directly on child devices

v2.3 - 06/2020 (Lazer)

  • New device types (Rain, Wind, Gust)
  • Add battery levels monitoring (use dedicated child devices)
  • Add alive module monitoring (use Netatmo reachable property to make Fibaro devices appearing dead in the interface)
  • Optimized 10 minutes query interval 10s after Netatmo cloud update
  • Minor fixes & enhancements

v2.2 - 06/2020 (GSmart)

  • FIX: prevent crash when we doesn't get any data from Netatmo API
  • Added status info on main QA device

v2.1 - 05/2020 (GSmart)

  • Added support for unit conversion, eg. km/h to m/s
  • Further enhancements in code

v2.0 - 04/2020 (GSmart)

  • Completely redesigned
  • Getting all data in one request to Netatmo API

v1.1 - 04/2020 (GSmart)

  • Added support for Wind and Rain modules

v1.0 - 04/2020 (GSmart)

  • Initial release
  • Supported devices: Base station, Outdoor module, Indoor module

 

54 Comments,  Want to add comment please login
E05653f3e9227a9d6a082f75cfa6b897

Question for Fibaro developers: Will NETAMO temperature sensors be able to be used as the main ones and assigned to rooms (similarly as it was in HC2)?

5d2c7b962f1e99a91d9dce42c7ff026b

Hi, how to update from 2.5.1 to 2.6 is there a tutorial available ? Thanks

87ccb923721c1b95e74efe10467931db

Please help. I installed QA, generated codes, copied. I get an error: QuickApp crashed main.lua:303: attempt to compare number with nil

0b5103499084273c5441d33776ce28c1

Right approach to OAuth2 is to use developer's ids of app to connect to service provider - in this case Netatmo. And the end user "authorize" that application to get data on his behalf. The intend of OAuth2 is to not send any credentials data (user, password) throug the web to get data through API. And even developer shouldn't have access to these data. Whole authorization process is made on Netatmo's servers. Now end user doesn't need to create an app on dev.netatmo.com So, from this point of view, it's simpler.

B1089e92fccb32bfc84adb03e0c015dc

Hello, I'd like to ask, why new version 2.6 of this app has removed "client_id" and "client_secret" parameters and now these values are hardcoded in quickapp. I believe the right approach is to keep these parameters as they are mandatory in OAuth protocol and therefore queries from QuickApp to Netatmo devices of each user are done not through Netatmo account owned by each user, but using account hardcoded in QuickApp.