Domoticz Community Forum - Support & Discussion

Thread 40 (Thread 0x60fe9200 (LWP 20719) "Netatmo Weersta"):
#0 0x7691f034 in __GI___wait4 (pid=25931, stat_loc=0x60fe7bb8, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x0076a13a in dumpstack_gdb(bool) ()
#2 0x0076a590 in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 <signal handler called>
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x76893364 in __GI_abort () at abort.c:79
#8 0x00c22060 in __gnu_cxx::__verbose_terminate_handler() ()
#9 0x00bc81e0 in __cxxabiv1::__terminate(void (*)()) ()
#10 0x00bc8236 in std::terminate() ()
#11 0x00bc815c in __cxa_throw ()
#12 0x00af1bac in Json::throwLogicError(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#13 0x00af3282 in Json::Value::asString[abi:cxx11]() const ()
#14 0x00963824 in CNetatmo::RefreshToken(bool) ()
#15 0x00971640 in CNetatmo::Do_Work() ()
#16 0x00c1dd42 in execute_native_thread_routine ()
#17 0x76a96310 in start_thread (arg=0x60fe9200) at pthread_create.c:477
#18 0x76957da8 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Netatmo API - API Domain Name Change

Dear Netatmo developer,
We hope this message finds you well.

We are writing to inform you of an upcoming change to our API domain configuration. As part of our ongoing efforts to streamline and improve our services, we will be retiring the domain api.netatmo.net and consolidating all API traffic under the existing domain api.netatmo.com.

Effective Date:September 8, 2025

To ensure uninterrupted service, we kindly ask you to update your applications to use api.netatmo.com exclusively before the above date. The structure and functionality of the API remain unchanged — only the domain name is affected.

Sincerely,

Legrand - Netatmo - Bticino

dgilbert2 wrote: Sunday 31 August 2025 21:29 Yes, barometer. No, its not a problem, just an observation. Here is my daily chart and you can tell when I updated to the 2025.1 after around 9am

Screenshot 2025-08-31 202339.png

waltervl wrote: Wednesday 02 April 2025 14:34 See also the wiki https://wiki.domoticz.com/Netatmo The instructions should be up to date.

At the moment, the supported Devices are;

Weather station,
Netatmo thermostat,
Netatmo Valves,
Homecoach,
CO2detector,
Smokedetector,
Presence camera (Only Events),
Presence Floodlight State,
Welkom camera (Only Events),
Door Tag,
Lights,
Power Switch (On/Off),
Blinds,
Fan with 2 speeds,
Scenarios,
Power-sensor (Watt)

homeJLB wrote: Saturday 04 April 2026 15:43

waltervl wrote: Wednesday 02 April 2025 14:34 See also the wiki https://wiki.domoticz.com/Netatmo The instructions should be up to date.

Can you update the Supported Devices ?

Kind Regards

waltervl wrote: Saturday 04 April 2026 16:22 Thanks for reporting, done.

Advance camera (Only Events),

Welkom camera (Only Events),

CNetatmo::RefreshToken()
→ Json::Value::asString()
→ exception
→ abort()

• Domoticz requested token refresh

• Netatmo returned HTML / 504 page instead of JSON

• Domoticz tried to parse missing JSON fields as strings

• Uncaught exception crashed Domoticz

sqlite3 domoticz.db "SELECT ID,Name,Enabled FROM Hardware;"

sqlite3 domoticz.db "UPDATE Hardware SET Enabled=0 WHERE ID=12;"

Huupke wrote: Sunday 03 May 2026 15:10 It seems that the earlier mentioned unhandled exception when parsing JSON is happening in case the Netatmo API returns a 504 page instead of proper JSON. This results in a full crash because it's not catched in a case the OAuth/token endpoint is down.

This is the cleaned-up stacktrace I got:

Code: Select all

CNetatmo::RefreshToken()
→ Json::Value::asString()
→ exception
→ abort()

So what likely happened in my case was:

• Domoticz requested token refresh

• Netatmo returned HTML / 504 page instead of JSON

• Domoticz tried to parse missing JSON fields as strings

• Uncaught exception crashed Domoticz

To be able to restore from this you can disable the domoticz service and disable the netatmo hardware by using the sqlite3 on the commandline if you know the hardware ID of Netatmo. To find the hardware ID of Netatmo you can use:

sqlite3 domoticz.db "SELECT ID,Name,Enabled FROM Hardware;"

Then disable like this when the ID is 12 (replace if it is different):

sqlite3 domoticz.db "UPDATE Hardware SET Enabled=0 WHERE ID=12;"

In my case I also had to revert to a database backup as it got corep[ted so I used the last hourly backup. For now I leave Netatmo disabled until the Netatmo API is back up in the air.

2026-05-03 00:00:32.551  Error: Netatmo  : Refresh token false 0
2026-05-03 00:00:33.552  Status: Netatmo : Requesting new access_token
2026-05-03 00:00:41.844  Debug: Netatmo  : HttpUrl: https://api.netatmo.com/oauth2/token?
2026-05-03 00:00:41.844  Debug: Netatmo  : HttpData: grant_type=refresh_token&…………
2026-05-03 00:00:41.844  Debug: Netatmo  : ExtraHeaders: User-Agent: Domoticz/Version 1.10
2026-05-03 00:00:41.844  Debug: Netatmo  : ExtraHeaders: Content-Type: application/x-www-form-urlencoded;charset=UTF-8
2026-05-03 00:00:41.844  Debug: Netatmo  : returnHeader: HTTP/2 504
2026-05-03 00:00:41.844  Debug: Netatmo  : returnHeader: date: Sat, 02 May 2026 22:00:41 GMT
2026-05-03 00:00:41.844  Debug: Netatmo  : returnHeader: content-type: text/html
2026-05-03 00:00:41.844  Debug: Netatmo  : returnHeader: content-length: 2061
2026-05-03 00:00:41.845  Debug: Netatmo  : returnHeader: cache-control: no-store
2026-05-03 00:00:41.845  Debug: Netatmo  : returnHeader: x-azure-ref: ……………
2026-05-03 00:00:41.845  Debug: Netatmo  : returnHeader: x-cache: CONFIG_NOCACHE
2026-05-03 00:00:41.845  Debug: Netatmo  : returnHeader:
2026-05-03 00:00:41.845  Debug: Netatmo  : Netatmo Invalid ...
2026-05-03 00:00:41.845  Error: Netatmo  : Invalid/no data received (refresh tokens)... HTTP/2 504
2026-05-03 00:00:41.846  Status: Netatmo : Retry LOGIN within 45 min.
2026-05-03 00:00:41.846  Debug: Netatmo  : Next RefreshToken time Block Sat May  2 23:28:42 2026

Error: Netatmo hardware (2) thread seems to have ended unexpectedly