homemade-disaster/iobroker.netatmo-energy

Netatmo Energy API connection

ioBroker.netatmo-energy

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

netatmo-energy adapter for ioBroker

Get and set data using Netatmo-Energy API. This adapter uses the fetch command to execute http requests to Netatmo Energy API. The official documentation of this API: https://dev.netatmo.com/apidocumentation/energy.

Detailed description of Netatmo Energy Adapter in english

netatmo-energy Adapter für ioBroker

Mittels der Netatmo-Energy API werden die aktuellen Einstellungen abgeholt bzw. geändert. Der Adapter verwendet den fetch Request für den Datentransfer zur Netatmo Energy API. Offizielle Dokumentation der API: https://dev.netatmo.com/apidocumentation/energy.

Detailbeschreibung des Netatmo Energy Adapter in deutsch

If you like it, please consider a donation:

Changelog

Older changes

2.7.3 (2024-01-27)

• (ioKlausi) Option 'Only update datapoints if changes are detected' corrected

2.7.2 (2024-01-18)

• (ioKlausi) Adjust attributes of the adapter

2.7.1 (2023-12-10)

• (ioKlausi) Remove GULP support
• (ioKlausi) Support dark mode

2.7.0 (2023-11-19)

• (ioKlausi) Adjust default value for parameters

2.6.5 (2023-11-05)

• (ioKlausi) New options in the adapter configuration for updating datapoints

2.6.4 (2023-10-25)

• (ioKlausi) Change value only if changes are detected

2.6.3 (2023-10-14)

• (ioKlausi) Adapt GULP

2.6.2 (2023-10-13)

• (ioKlausi) Bug fix of 'Sentry errors'

2.6.1 (2023-06-01)

• (ioKlausi) Correct some adapter check issues

2.6.0 (2023-05-01)

• (ioKlausi) Enable / Disable sensor actions

2.5.8 (2023-04-16)

• (ioKlausi) Bug fix of translations

2.5.7 (2023-04-16)

• (ioKlausi) Bug fix of sensor actions

2.5.6 (2023-04-15)

• (ioKlausi) Bug fix of Sentry errors
• (ioKlausi) Home mode for individual rooms in admin tab established
• (ioKlausi) Bug fix of translations

2.5.5 (2023-04-11)

• (ioKlausi) Bug fix of Sentry errors

2.5.4 (2023-04-10)

• (ioKlausi) Bug fix of Sentry errors

2.5.3 (2023-04-10)

• (ioKlausi) Added data point for messages

2.5.2 (2023-04-09)

• (ioKlausi) Made some adjustments in the admin config

2.5.1 (2023-04-09)

• (ioKlausi) Test message in config added
• (ioKlausi) Revise ioBroker Netatmo-Energy APP

2.5.0 (2023-04-07)

• (ioKlausi) Sensor changed to object ID type boolean

License

MIT License

Copyright (c) 2021-2024 ioKlausi [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.netatmo-energy's Issues

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/Homemade-Disaster/ioBroker.netatmo-energy

• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 ioKlausi [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 ioKlausi [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W400] Cannot find "netatmo-energy" in latest repository

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Please consider fixing errors reported by adapter checker

Adapter CHecker reported the following erros / warning for 2.6.0.
Please consider fixing them for the next release:

[E518] "@alcalzone/release-script" is used, but ".releaseconfig.json" not found
[W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
[W505] setTimeout found in "main.js", but no clearTimeout detected

After Node 16.x update to 18.17.1 - API Warning: Authenticate refresh error: invalid_grant

Describe the bug
After i updated to Node 18.17.1 it seemed that the login didn't work anymore
I generated the token by the button but i asked several times and in the log you see the message

"API Warning: Authenticate refresh error: invalid_grant"

`

netatmo.0	2023-11-12 03:57:01.689	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.665	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.568	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.552	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.386	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.374	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.364	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.358	info	API Warning: Authenticate refresh error: invalid_client
netatmo.0	2023-11-12 03:57:01.344	info	API Warning: Authenticate refresh error: invalid_client

`

To Reproduce
Steps to reproduce the behavior:

installed node 18.17.1 then 16.x before

Versions:

• Adapter version: 2.61 & tried 2.65
• JS-Controller version: 5.0.12
• Node version: 18.17.1
• Operating system: Rasperry PI (linux)

HomeID from netatmo did not change, i tried to generate new api keys but still stuck in same problem.

Get no Data, Token is missing

Hi Homemade-Disaster,

i started with an new Installation of iobroker an with your Adapter.
Unfortunately the adapter didn´t get any Token´s from Netatmo.

I verifiyed the credentials with a Blocky i found in the forum.

Steps to reproduce the behavior:

1. Start with an new installation of the Adapter
2. Add Creditentials in Settings
3. See error

Screenshots & Logfiles
Log are taken with adapter in silly mode.

Versions:

• Adapter version: 1.3.1
• JS-Controller version: 4.0.23
• Node version: 16.15.1
• Operating system: Synology DS920+ DSM7.2 with Docker (offical Image from iobroker)

kind regards
André

edit: removed home-ID from log

"Ich habe keinen Token erhalten" + "Api-Anfrage nicht ok"

Hallo Zusammen,
meine home_id, client_id und client_secret sind korrekt eingetragen. Dennoch bekomme ich die Meldung "Ich habe keinen Token erhalten" und "Api-Anfrage nicht ok". Habe Testweise einen neuen Netatmo Account angelegt und dort eine weitere App erzeugt (andere home_id, client_id und andere client_secret) - Leider mit gleichen Ergebnis: "Ich habe keinen Token erhalten" + "Api-Anfrage nicht ok".

Wenn ich den Adapter dann so laufen lasse kommt promt eine Mail: Nach mehreren fehlgeschlagenen Anmeldeversuchen wurde Ihr Konto für die nächsten 10 Minuten gesperrt. Die letzte Anmeldung in Ihrem Konto [email protected] wurde am 29.08.22, 14:20 in Leipzig, Germany* (ungefährer Standort, abgeleitet von der IP-Adresse: xx.xxx.xx.xxx) über die Drittanbieter-App ioBroker_Energy mit Ihrem Passwort vorgenommen.
New Connection
ioBroker_Energy
28.08.22, 04:50
xx.xxx.xx.xxx
Leipzig, Germany*

Die Abfragen über dev.netatmo.com funktionieren. Wenn ich mit get /homesdata meine Home-ID erhalte und diese dann mit get /homestatus benutze um die Home-ID abzufragen kommt der Response korrekt zurück und ich sehe darin alle meine eigerichteten Thermostate.

Einen Copy-Paste-Fehler kann ich nach mehrmaliger Kontrolle mit Sicherheit ausschließen.
home_id, client_id und client_secret funktionieren über mit dem mittlerweile weitverbreiteten Netatmo Thermostat Blockly Skript von Newpicsel einwandfrei. Ein Fehler in meinen Anmeldedaten oder eine Sperre seitens Netatmo kann also auch grundsätzlich werden.

Gibt es zu dieser Problematik schon Ansätze oder gar eine Lösung?

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Update stable version in repo from 1.3.1 to 2.0.2

Think about update stable version to 2.0.2

Version: stable=1.3.1 (280 days old) => latest=2.0.2 (16 days old)
Installs: stable=107 (86.99%), latest=11 (8.94%), total=123
Click to edit

Values are not beeing updated (sync only works in one direction)

When I change the temperature within the Netatmo Energy "tab" website... it works. The Relais receives the value after ~5 seconds.
But when changing the temperature at the Netatmo Relais itselfs, these changes are not beeing sent to iobroker. No setpoint temperatur, no measured temperatures...

What can I do?

Update stable version in repo from 2.0.2 to 2.3.1

Think about update stable version to 2.3.1

Version: stable=2.0.2 (51 days old) => latest=2.3.1 (15 days old)
Installs: stable=40 (33.33%), latest=10 (8.33%), total=120
Click to edit

Update stable version in repo from 1.3.1 to 2.0.2

Think about update stable version to 2.0.2

Version: stable=1.3.1 (279 days old) => latest=2.0.2 (15 days old)
Installs: stable=108 (87.8%), latest=10 (8.13%), total=123
Click to edit

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Update stable version in repo from 2.6.1 to 2.7.0

Think about update stable version to 2.7.0

Version: stable=2.6.1 (184 days old) => latest=2.7.0 (15 days old)
Installs: stable=91 (65.47%), latest=14 (10.07%), total=139

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

invalid jsonConfig in console

Describe the bug
The netatmo-energy Plugin isn't working. I don't have my smart thermostat in the Overview.
I have a warning in the console

To Reproduce
Just start the Plugin

Expected behavior
See my smart thermostat in the Admin-Tab.

Screenshots & Logfiles
Console warning:
netatmo-energy has an invalid jsonConfig: [{"instancePath":"/items/tabLogon/items/authenticate","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"window"},"message":"must NOT have additional properties"},{"instancePath":"/items/tabLogon","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]

Screenshot:

Versions:

• Adapter version: 2.7.0
• JS-Controller version: 5.0.17
• Node version: v18.13.0
• Operating system: ubuntu 23.10 in proxmox 8.1.3

Externe Sensoren

Hallo Ioklausi,
es wäre sehr schön, wenn du externe Sensoren in deinen Adapter einbinden könntest. Ich habe welche von aquara, die Fenstersensoren.
Wäre schön, wenn die im Adapter eintragbar wären und die Thermostate runter regeln, wenn ein Fenster geöffnet wird. Sonst sieht alles sehr schön aus!

Update stable version in repo from 2.6.0 to 2.6.1

Think about update stable version to 2.6.1

Version: stable=2.6.0 (48 days old) => latest=2.6.1 (15 days old)
Installs: stable=48 (37.8%), latest=11 (8.66%), total=127
Click to edit

Update stable version in repo from 0.2.4 to 1.3.1

Think about update stable version to 1.3.1

Version: stable=0.2.4 (79 days old) => latest=1.3.1 (15 days old)
Installs: stable=44 (65.67%), latest=12 (17.91%), total=67
Click to edit

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/Homemade-Disaster/ioBroker.netatmo-energy

I have also found warnings that may be fixed if possible.

• [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis-2, you might want to add “vis-2” to the list too.

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

password token flow will be disabled by Netatmo nd of September 2022!

You ned to use the "Authorization code" grant type ... I'm currently adjusting ioBroker-netatmo for it ... maybe you can do the same logic