I no longer have error messages but the temperature values are still not updated. And my thermostat doesn't work!!Thuis wrote: ↑Sunday 08 September 2024 15:28 Yes it does, thanks
Code: Select all
2024-09-08 15:27:35.670 Status: Netatmo: Use refresh token from database... 2024-09-08 15:27:35.671 Status: Netatmo: Requesting refreshed tokens 2024-09-08 15:27:36.000 Status: Netatmo: Station Data parsed 2024-09-08 15:27:36.000 Status: Netatmo: Weather 1 2024-09-08 15:27:36.000 Status: Netatmo: Get HomesData Details 2024-09-08 15:27:36.138 Status: Netatmo: Home id Onshuis updated. 2024-09-08 15:27:36.299 Status: Netatmo: cloud data for module [Buiten] is now updated again 2024-09-08 15:27:36.311 Status: Netatmo: cloud data for module [Slaapkamer Zoë] is now updated again 2024-09-08 15:27:36.322 Status: Netatmo: cloud data for module [Slaapkamer Lara] is now updated again 2024-09-08 15:27:36.335 Status: Netatmo: HomeStatus parsed 2024-09-08 15:27:36.460 Status: Netatmo: Events Data parsed 2024-09-08 15:27:36.460 Status: Netatmo: Status 1
Netatmo authentication changes Oct 2022
Moderator: leecollings
-
- Posts: 13
- Joined: Monday 14 March 2022 15:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Netatmo authentication changes Oct 2022
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
Yes i see, my old devices are not updated, but there are new temp devices with newer idx they are updated. So i guess change all scripts and blocklys to new idx and name?
I Love Domoticz ! And the community around it :-)
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
I now have 46 devices lol, for a weather station with 3 indoor and 1 outdoor unit. I guess i have some clean up to do
I Love Domoticz ! And the community around it :-)
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
with version 2024.7 (build 16242) the unwanted Error message is gone.
Normally all is working, but it creates new devices.
you can transfer manually the history of the sensor.
Normally all is working, but it creates new devices.
you can transfer manually the history of the sensor.
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
Yes, well i just deleted all the old netatmo devices and hardware and added the new hardware and works like a charm.
I don't mind changing all the scripts, i am very glad it works again. So thanks to all who put their spare time in to make this happen.
Thank you thank you thank you.
I don't mind changing all the scripts, i am very glad it works again. So thanks to all who put their spare time in to make this happen.
Thank you thank you thank you.
I Love Domoticz ! And the community around it :-)
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
@rob67ert
Can you share some details off your setup?
Witch devices do you have, witch scopes do you use?
And also the lines before the error can give insight to your problem.
But make sure your on;
Can you share some details off your setup?
Witch devices do you have, witch scopes do you use?
And also the lines before the error can give insight to your problem.
But make sure your on;
-
- Posts: 13
- Joined: Monday 14 March 2022 15:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Netatmo authentication changes Oct 2022
After updating yesterday there are 2 issues remaining. The rain gauge does not update and neither does the thermostat temperature
-
- Posts: 17
- Joined: Tuesday 24 December 2019 13:57
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Netatmo authentication changes Oct 2022
@homeJLB
I have 2024.7(build 16242)
I was able to remove my netatmo hardware after a sudo service domoticz.sh restart
Then the gui works for a short while (about 5 sec)
After I add de Netatmo hardware again with your steps I have the same problem again.
But not not able te remove the hardware anymore...
Is there anyway to get the log without the Domotics GUI working?
I have the Netatmo weather station, thermostat, co2 and smokedetector
Yes was able to get some more errors:
2024-09-09 17:11:43.934 MB: Temp (Internal Temp CPU)
2024-09-09 17:11:45.045 Status: iDetect: 192.168.178.2 ====> SSH connection established
2024-09-09 17:11:47.763 Status: Netatmo: Home id DELETE updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga Extra updated.
2024-09-09 17:11:47.952 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.076 Status: P1 meter: Meter reports as DSMR 4.2
2024-09-09 17:11:48.170 Status: P1 meter: Current electricity tariff: High
2024-09-09 17:11:48.201 Error: Domoticz(pid:13445, tid:13481('Netatmo')) received fatal signal 11 (Segmentation fault)
2024-09-09 17:11:48.201 Error: siginfo address=0x3485, address=(nil)
2024-09-09 17:11:48.249 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.538 Status: P1 meter: Found gas meter on M-Bus channel 2
2024-09-09 17:11:48.694 P1 meter: P1 Smart Meter (Power)
2024-09-09 17:11:48.701 P1 meter: Usage (Usage L1)
2024-09-09 17:11:48.705 P1 meter: Usage (Delivery L1)
2024-09-09 17:11:48.712 P1 meter: Usage (Usage L2)
2024-09-09 17:11:48.716 P1 meter: Usage (Delivery L2)
2024-09-09 17:11:48.727 P1 meter: Usage (Usage L3)
2024-09-09 17:11:48.731 P1 meter: Usage (Delivery L3)
2024-09-09 17:11:48.734 P1 meter: Usage (Actual Usage (L1 + L2 + L3))
2024-09-09 17:11:48.737 P1 meter: Usage (Actual Delivery (L1 + L2 + L3))
2024-09-09 17:11:48.744 P1 meter: P1 Smart Meter (Gas)
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [] is now updated again
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [Windmeter] is now updated again
2024-09-09 17:11:51.219 Status: Netatmo: cloud data for module [Regenmeter] is now updated again
2024-09-09 17:11:51.220 Status: Netatmo: HomeStatus parsed
2024-09-09 17:11:51.282 Error: Thread 26 (Thread 0xa7df6200 (LWP 13481)):
2024-09-09 17:11:51.282 Error: #0 __waitpid (options=0, stat_loc=0xa7df4670, pid=13573) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2024-09-09 17:11:51.282 Error: #1 __waitpid (pid=13573, stat_loc=0xa7df4670, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2024-09-09 17:11:51.282 Error: #2 0x0073adea in dumpstack_gdb(bool) ()
2024-09-09 17:11:51.282 Error: #3 0x0073b240 in signal_handler(int, siginfo_t*, void*) ()
2024-09-09 17:11:51.282 Error: #4 <signal handler called>
2024-09-09 17:11:51.283 Error: #5 raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2024-09-09 17:11:51.283 Error: #6 <signal handler called>
2024-09-09 17:11:51.283 Error: #7 0x00939a6e in CNetatmo::ParseHomeStatus(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Json::Value&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) ()
I have 2024.7(build 16242)
I was able to remove my netatmo hardware after a sudo service domoticz.sh restart
Then the gui works for a short while (about 5 sec)
After I add de Netatmo hardware again with your steps I have the same problem again.
But not not able te remove the hardware anymore...
Is there anyway to get the log without the Domotics GUI working?
I have the Netatmo weather station, thermostat, co2 and smokedetector
Yes was able to get some more errors:
2024-09-09 17:11:43.934 MB: Temp (Internal Temp CPU)
2024-09-09 17:11:45.045 Status: iDetect: 192.168.178.2 ====> SSH connection established
2024-09-09 17:11:47.763 Status: Netatmo: Home id DELETE updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga Extra updated.
2024-09-09 17:11:47.952 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.076 Status: P1 meter: Meter reports as DSMR 4.2
2024-09-09 17:11:48.170 Status: P1 meter: Current electricity tariff: High
2024-09-09 17:11:48.201 Error: Domoticz(pid:13445, tid:13481('Netatmo')) received fatal signal 11 (Segmentation fault)
2024-09-09 17:11:48.201 Error: siginfo address=0x3485, address=(nil)
2024-09-09 17:11:48.249 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.538 Status: P1 meter: Found gas meter on M-Bus channel 2
2024-09-09 17:11:48.694 P1 meter: P1 Smart Meter (Power)
2024-09-09 17:11:48.701 P1 meter: Usage (Usage L1)
2024-09-09 17:11:48.705 P1 meter: Usage (Delivery L1)
2024-09-09 17:11:48.712 P1 meter: Usage (Usage L2)
2024-09-09 17:11:48.716 P1 meter: Usage (Delivery L2)
2024-09-09 17:11:48.727 P1 meter: Usage (Usage L3)
2024-09-09 17:11:48.731 P1 meter: Usage (Delivery L3)
2024-09-09 17:11:48.734 P1 meter: Usage (Actual Usage (L1 + L2 + L3))
2024-09-09 17:11:48.737 P1 meter: Usage (Actual Delivery (L1 + L2 + L3))
2024-09-09 17:11:48.744 P1 meter: P1 Smart Meter (Gas)
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [] is now updated again
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [Windmeter] is now updated again
2024-09-09 17:11:51.219 Status: Netatmo: cloud data for module [Regenmeter] is now updated again
2024-09-09 17:11:51.220 Status: Netatmo: HomeStatus parsed
2024-09-09 17:11:51.282 Error: Thread 26 (Thread 0xa7df6200 (LWP 13481)):
2024-09-09 17:11:51.282 Error: #0 __waitpid (options=0, stat_loc=0xa7df4670, pid=13573) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2024-09-09 17:11:51.282 Error: #1 __waitpid (pid=13573, stat_loc=0xa7df4670, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2024-09-09 17:11:51.282 Error: #2 0x0073adea in dumpstack_gdb(bool) ()
2024-09-09 17:11:51.282 Error: #3 0x0073b240 in signal_handler(int, siginfo_t*, void*) ()
2024-09-09 17:11:51.282 Error: #4 <signal handler called>
2024-09-09 17:11:51.283 Error: #5 raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2024-09-09 17:11:51.283 Error: #6 <signal handler called>
2024-09-09 17:11:51.283 Error: #7 0x00939a6e in CNetatmo::ParseHomeStatus(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Json::Value&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) ()
-
- Posts: 13
- Joined: Monday 14 March 2022 15:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Netatmo authentication changes Oct 2022
Hi. With the last upadte 16249.
I no longer have access to my thermostat. What should be done ?
Netatmo: Error data ... {"error":{"code":26,"message":"User usage reached"}}
I no longer have access to my thermostat. What should be done ?
Netatmo: Error data ... {"error":{"code":26,"message":"User usage reached"}}
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
Rob67ert wrote: ↑Monday 09 September 2024 17:11 @homeJLB
I have 2024.7(build 16242)
I was able to remove my netatmo hardware after a sudo service domoticz.sh restart
Then the gui works for a short while (about 5 sec)
After I add de Netatmo hardware again with your steps I have the same problem again.
But not not able te remove the hardware anymore...
Is there anyway to get the log without the Domotics GUI working?
I have the Netatmo weather station, thermostat, co2 and smokedetector
Yes was able to get some more errors:
2024-09-09 17:11:43.934 MB: Temp (Internal Temp CPU)
2024-09-09 17:11:45.045 Status: iDetect: 192.168.178.2 ====> SSH connection established
2024-09-09 17:11:47.763 Status: Netatmo: Home id DELETE updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga updated.
2024-09-09 17:11:47.763 Status: Netatmo: Home id Kinga Extra updated.
2024-09-09 17:11:47.952 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.076 Status: P1 meter: Meter reports as DSMR 4.2
2024-09-09 17:11:48.170 Status: P1 meter: Current electricity tariff: High
2024-09-09 17:11:48.201 Error: Domoticz(pid:13445, tid:13481('Netatmo')) received fatal signal 11 (Segmentation fault)
2024-09-09 17:11:48.201 Error: siginfo address=0x3485, address=(nil)
2024-09-09 17:11:48.249 Status: Netatmo: Events Data parsed
2024-09-09 17:11:48.538 Status: P1 meter: Found gas meter on M-Bus channel 2
2024-09-09 17:11:48.694 P1 meter: P1 Smart Meter (Power)
2024-09-09 17:11:48.701 P1 meter: Usage (Usage L1)
2024-09-09 17:11:48.705 P1 meter: Usage (Delivery L1)
2024-09-09 17:11:48.712 P1 meter: Usage (Usage L2)
2024-09-09 17:11:48.716 P1 meter: Usage (Delivery L2)
2024-09-09 17:11:48.727 P1 meter: Usage (Usage L3)
2024-09-09 17:11:48.731 P1 meter: Usage (Delivery L3)
2024-09-09 17:11:48.734 P1 meter: Usage (Actual Usage (L1 + L2 + L3))
2024-09-09 17:11:48.737 P1 meter: Usage (Actual Delivery (L1 + L2 + L3))
2024-09-09 17:11:48.744 P1 meter: P1 Smart Meter (Gas)
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [] is now updated again
2024-09-09 17:11:51.218 Status: Netatmo: cloud data for module [Windmeter] is now updated again
2024-09-09 17:11:51.219 Status: Netatmo: cloud data for module [Regenmeter] is now updated again
2024-09-09 17:11:51.220 Status: Netatmo: HomeStatus parsed
2024-09-09 17:11:51.282 Error: Thread 26 (Thread 0xa7df6200 (LWP 13481)):
2024-09-09 17:11:51.282 Error: #0 __waitpid (options=0, stat_loc=0xa7df4670, pid=13573) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2024-09-09 17:11:51.282 Error: #1 __waitpid (pid=13573, stat_loc=0xa7df4670, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2024-09-09 17:11:51.282 Error: #2 0x0073adea in dumpstack_gdb(bool) ()
2024-09-09 17:11:51.282 Error: #3 0x0073b240 in signal_handler(int, siginfo_t*, void*) ()
2024-09-09 17:11:51.282 Error: #4 <signal handler called>
2024-09-09 17:11:51.283 Error: #5 raise (sig=11) at ../sysdeps/unix/sysv/linux/raise.c:50
2024-09-09 17:11:51.283 Error: #6 <signal handler called>
2024-09-09 17:11:51.283 Error: #7 0x00939a6e in CNetatmo::ParseHomeStatus(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Json::Value&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&) ()
When checking a Error I always use
Code: Select all
sudo tail -f /var/log/domoticz.log
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
From the documentation it states;
Per user limits
50 requests every 10 seconds
500 requests every hour
This is still in investigation but your thermostat should work
Please check your 'Not used Devices' because the new API gives a different ID
kind regards
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
Well, it worked for a while, but now, the log says all is good, but some sensors are not updated. Mainly all the CO2 sensors from the smart weather station. They stay at 0 ppm. And the sound sensor, stays at 0dB.
In the netatmo app it is 467 ppm and 28 dB as of the time of writing.
I do see the other sensors being updated correctly. Like temp. batt. level, sig. level
Oh also the humidity stays at 0%. And pressure also 0.0hPa
I have no clue why, how or when?
Thanks in advance.
Code: Select all
2024-09-12 20:46:14.803 Status: Netatmo: Use refresh token from database...
2024-09-12 20:46:14.804 Status: Netatmo: Requesting refreshed tokens
2024-09-12 20:46:15.201 Status: Netatmo: Station Data parsed
2024-09-12 20:46:15.201 Status: Netatmo: Weather 1
2024-09-12 20:46:15.201 Status: Netatmo: Get HomesData Details
2024-09-12 20:46:15.361 Status: Netatmo: Home id Onshuis updated.
2024-09-12 20:46:15.567 Status: Netatmo: cloud data for module [Netatmo Buiten] is now updated again
2024-09-12 20:46:15.583 Status: Netatmo: cloud data for module [Netatmo Slaapkamer Zoë] is now updated again
2024-09-12 20:46:15.604 Status: Netatmo: cloud data for module [Netatmo Slaapkamer Lara] is now updated again
2024-09-12 20:46:15.626 Status: Netatmo: HomeStatus parsed
2024-09-12 20:46:15.770 Status: Netatmo: Events Data parsed
2024-09-12 20:46:15.770 Status: Netatmo: Status 1
Code: Select all
Air Quality Voc 0 ppm 9 2024-09-12 20:46:15
General Sound Level 0 dB 10 2024-09-12 20:46:15
I do see the other sensors being updated correctly. Like temp. batt. level, sig. level
Oh also the humidity stays at 0%. And pressure also 0.0hPa
I have no clue why, how or when?
Thanks in advance.
I Love Domoticz ! And the community around it :-)
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
So i deleted the netatmo hardware again and put started over. I see something strange. If i am fast enough, just after adding the devices, i see the ppm and the dB data from the main unit in the device, but that takes about 5 seconds, and it goes back to 0.
I saw on github, there is a table and i see there the humidity and baro also stop, but its for a thermostat, so i guess i just have to sit tight and wait.
Thanks again for all the work.
I saw on github, there is a table and i see there the humidity and baro also stop, but its for a thermostat, so i guess i just have to sit tight and wait.
Thanks again for all the work.
I Love Domoticz ! And the community around it :-)
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
update 2024.7.16253 fixes problem.
Thank you.
Thank you.
I Love Domoticz ! And the community around it :-)
- Thuis
- Posts: 251
- Joined: Tuesday 11 September 2018 11:36
- Target OS: Linux
- Domoticz version: Beta
- Location: The Netherlands
- Contact:
Re: Netatmo authentication changes Oct 2022
After a while, all scripts stop working or they become very slow. Then when i deactivate the netatmo hardware, everything starts working again.
So i have a button which uses a blockly script to turn lights on. Also another button to turn them off thru another blockly.
When the blockly turn everything on, the button is reset by the same blockly.
I click the button then after 5 to 10 minutes, the lights come on. The same blockly was working for the last 6 years or so.
Now i disable the netatmo hardware, click the button and all lights come on directly, as it has always done.
I turn the netatmo hardware back on and it seems to work, but after an hour or so, the scripts stop or become very slow again.
First i thought it was some other script or device or not returning. But now i can repeat the behaviour by doing the lights with netatmo hardware on or off. And the netatmo hardware is the last thing that has changed. Domoticz just keeps running.
There is nothing in the logs. Any help on what i could do to fix this? Or insight why the netatmo hardware seems to be the cause of this effect?
So i have a button which uses a blockly script to turn lights on. Also another button to turn them off thru another blockly.
When the blockly turn everything on, the button is reset by the same blockly.
I click the button then after 5 to 10 minutes, the lights come on. The same blockly was working for the last 6 years or so.
Now i disable the netatmo hardware, click the button and all lights come on directly, as it has always done.
I turn the netatmo hardware back on and it seems to work, but after an hour or so, the scripts stop or become very slow again.
First i thought it was some other script or device or not returning. But now i can repeat the behaviour by doing the lights with netatmo hardware on or off. And the netatmo hardware is the last thing that has changed. Domoticz just keeps running.
There is nothing in the logs. Any help on what i could do to fix this? Or insight why the netatmo hardware seems to be the cause of this effect?
Code: Select all
./+o+-
yyyyy- -yyyyyy+ OS: Ubuntu 22.04 jammy
://+//////-yyyyyyo Kernel: x86_64 Linux 6.8.0-40-generic
.++ .:/++++++/-.+sss/` Uptime: 6h 59m
.:++o: /++++++++/:--:/- Packages: 2151
o:+o+:++.`..```.-/oo+++++/ Shell: bash 5.1.16
.:+o:+o/. `+sssoo+/ Disk: 41G / 117G (37%)
.++/+:+oo+o:` /sssooo. CPU: Intel Core i3-5020U @ 4x 2,1GHz [72.0°C]
/+++//+:`oo+o /::--:. RAM: 3575MiB / 7844MiB
\+/+o+++`o++o ++////.
.++.o+++oo+:` /dddhhh.
.+.o+oo:. `oddhhhh+
\+.++o+o``-````.:ohdhhhhh+
`:o+++ `ohhhhhhhhyo++os:
.o:`.syhhhhhhh/.oo++o`
/osyyyyyyo++ooo+++/
````` +oo+++o\:
`oo++.
I Love Domoticz ! And the community around it :-)
-
- Posts: 42
- Joined: Thursday 14 September 2023 19:32
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 16341
- Location: Stockholm
- Contact:
Re: Netatmo authentication changes Oct 2022
Today I updated to 16265. I deleted old Netatmo hardware/devices, then added the Netatmo Hardware again following the above description. Logged in with ID and Secret and selected Weather Station (I have no other Netatmo devices). A lot of new devices were created, some useful, some not, but thats OK. And I must say :
THANK YOU SO MUCH for the guy(s) who fixed this Netatmo issue which has bothered me for a long time.
/fjuppe
THANK YOU SO MUCH for the guy(s) who fixed this Netatmo issue which has bothered me for a long time.




/fjuppe
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
@fjuppe
can you check your version? I just dit a 'updatebeta' but today it's still 2024.7 (16259) for me.
Kind regards
can you check your version? I just dit a 'updatebeta' but today it's still 2024.7 (16259) for me.
Kind regards
-
- Posts: 42
- Joined: Thursday 14 September 2023 19:32
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 16341
- Location: Stockholm
- Contact:
Re: Netatmo authentication changes Oct 2022
@homeJLB
I confirm my version is 2024.7 (16265)
/fjuppe
I confirm my version is 2024.7 (16265)
/fjuppe
-
- Posts: 64
- Joined: Tuesday 16 October 2018 23:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: Belgium
- Contact:
Re: Netatmo authentication changes Oct 2022
@thuis
do you start domoticz with debug - hardware active ? If yes can you try without the Debug flag.
do you start domoticz with debug - hardware active ? If yes can you try without the Debug flag.
Who is online
Users browsing this forum: No registered users and 0 guests