netatmo error "Error: parser returned no values"
I am having errors, i think it may because my modules are out of battery.
Please amend firmware to cope with out of range reports that are due to batter failure / suggest in UI that batter may have gone out on a netatmo module
2018-06-13 12:04:14,278 - ERROR - netatmo-parser:152 - Error reading wind module: list index out of range 2018-06-13 12:09:16,384 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2018-06-13 12:09:17,274 - ERROR - netatmo-parser:142 - Error reading rain gauge module: list index out of range 2018-06-13 12:09:18,149 - ERROR - netatmo-parser:152 - Error reading wind module: list index out of range 2018-06-13 12:14:20,338 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2018-06-13 12:14:21,300 - ERROR - netatmo-parser:142 - Error reading rain gauge module: list index out of range 2018-06-13 12:14:22,183 - ERROR - netatmo-parser:152 - Error reading wind module: list index out of range 2018-06-13 12:15:22,217 - WARNING - rmParserManager:130 - * Parser: (10, 'netatmo-parser.pyc', 'Netatmo Parser', 1, []) - ignored because of lack of data (failCounter=100, lastFail=2018-06-13 12:14:18)! 2018-06-13 13:30:27,957 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2018-06-13 13:30:28,809 - ERROR - netatmo-parser:142 - Error reading rain gauge module: list index out of range 2018-06-13 13:30:29,683 - ERROR - netatmo-parser:152 - Error reading wind module: list index out of range
-
Hi Dewey.
Either press DEFAULT from the web interface Setting > Weather > NetAtmo or change the username to something invalid, hit SAVE, then REFRESH ALL.
Then go to NetAtmo settings again, put your correct username, hit SAVE and REFRESH ALL.
This will initiate a auth reset for NetAtmo service and should work fine afterwards.
Warning: Pressing DEFAULT will reset all NetAtmo parser data and settings.
The beta update fixes this issue with NetAtmo.
-
I'm getting netatmo-parser errors with my newly installed Netatmo. I've tried the Default and have tried to set up multiple time .... The RainMachine can see both of my Netatmo Modules, but it cannot pull any data. What is the fix?
2019-07-05 17:53:19,448 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2019-07-05 17:53:19,976 - ERROR - netatmo-parser:142 - Error reading rain gauge module: list index out of range
-
I have the same Problem
2019-09-02 20:11:22,395 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2019-09-02 20:11:22,697 - ERROR - netatmo-parser:142 - Error reading rain gauge module: list index out of range 2019-09-02 20:11:23,012 - ERROR - netatmo-parser:152 - Error reading wind module: list index out of range 2019-09-02 20:12:48,744 - INFO - rmMainManager:239 - Upgrade checked.
-
Has anyone had luck with this? I just got a Netatmo weather station hoping to link it with my RainMachine but it only ever says "Retrying: No data returned" in the status of the weather settings. And in the log its the same as the previous people have mentioned. I notice I got a HTTP Error 400 too.
2019-11-15 22:54:01,345 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2019-11-15 22:54:01,371 - WARNING - rmParserManager:181 - * Parser Netatmo Parser returned no values 2019-11-15 22:56:41,265 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2019-11-15 22:59:44,362 - ERROR - netatmo-parser:261 - HTTP Error 400: Traceback (most recent call last): File "./RMParserFramework/parsers/netatmo-parser.py", line 258, in postRequest File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen File "/usr/lib/python2.7/urllib2.py", line 435, in open File "/usr/lib/python2.7/urllib2.py", line 548, in http_response File "/usr/lib/python2.7/urllib2.py", line 473, in error File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default HTTPError: HTTP Error 400: 2019-11-15 22:59:44,390 - ERROR - netatmo-parser:222 - Failed to get oauth token 2019-11-15 22:59:47,278 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range 2019-11-15 23:02:57,530 - ERROR - netatmo-parser:172 - Error reading temperature module: list index out of range
Any help would be great. Thanks
-
Make sure you have the latest version of RainMachine firmware.
Try to reset NetAtmo to DEFAULTS (by pressing the button from Web Interface), enable and enter your credentials again without selecting any modules (uncheck useSpecificModules). SAVE and REFRESH NOW for all weather services. Check the log/UI if it worked.
I just tried my personal NetAtmo now and it works fine.
-
Retrying: No data returned
I tried all the options, deleted / added 10 times, but this does not help. Login Password = Passed.
I have Homey, it receives data from NETATMO without problems, but Rainmachin does not want to receive it at all.2020-06-27 12:52:27,054 - INFO - rmUserSettings:174 - --------------------------------------------------------------------------------------------- 2020-06-27 12:52:27,073 - INFO - rmThreadWatcher:143 - ThreadWatcher running True 2020-06-27 12:52:27,085 - INFO - rmLocalNetworkAdvertise:115 - Local Network Advertiser starting 2020-06-27 12:52:27,147 - INFO - rmParserManager:228 - *** BEGIN Loading parsers from './RMParserFramework/parsers' 2020-06-27 12:52:27,192 - INFO - rmParser:71 - *** Registering parser OpenWeatherMap Parser with interval 21600 2020-06-27 12:52:27,408 - INFO - rmParser:71 - *** Registering parser Netatmo Parser with interval 21600 2020-06-27 12:52:27,615 - INFO - rmParser:71 - *** Registering parser WUnderground Parser with interval 21600 2020-06-27 12:52:27,814 - INFO - rmParser:71 - *** Registering parser CIMIS Parser with interval 21600 2020-06-27 12:52:28,009 - INFO - rmParser:71 - *** Registering parser ForecastIO Parser with interval 21600 2020-06-27 12:52:28,215 - INFO - rmParser:71 - *** Registering parser Weather Rules Parser with interval 3600 2020-06-27 12:52:28,508 - INFO - rmParser:71 - *** Registering parser NOAA Parser with interval 21600 2020-06-27 12:52:28,600 - INFO - rmParser:71 - *** Registering parser FAWN Parser with interval 21600 2020-06-27 12:52:28,792 - INFO - rmParser:71 - *** Registering parser WeatherDisplay Parser with interval 21600 2020-06-27 12:52:28,992 - INFO - rmParser:71 - *** Registering parser METNO Parser with interval 21600 2020-06-27 12:52:29,039 - INFO - rmParserManager:313 - *** END Loading parsers 2020-06-27 12:52:29,113 - INFO - rmSimulator:1086 - Loading last weather simulation data for today programs 2020-06-27 12:52:30,468 - INFO - rmFlowSensor:44 - Initialised Flow Sensor with path /sys/devices/platform/rmsensor/flowcounter 2020-06-27 12:52:30,540 - INFO - rmAcquireData:46 - Init RMAcquireData 2020-06-27 12:52:30,773 - INFO - rmAPIClientREST:93 - REST: GET : http://127.0.0.1:18080/api//apiVer 2020-06-27 12:52:30,850 - INFO - rmTouchManagerRainMachine5:937 - Closing boot animation 2020-06-27 12:52:30,963 - INFO - rmTouchManagerRainMachine5:267 - Touch Manager is starting up ... 2020-06-27 12:52:31,206 - INFO - rmMainManager:139 - Starting bonjour service 2020-06-27 12:55:45,506 - WARNING - rmParserManager:181 - * Parser Netatmo Parser returned no values 2020-06-27 12:56:55,904 - INFO - rmMainManager:239 - Upgrade checked. 2020-06-27 13:10:29,351 - INFO - rmMainManager:239 - Upgrade checked. ---------------------------- PROGRAM SIMULATION LOG -----------------------------
-
Hi everyone,
i purchased my Netatmo today and stumbled into the same error. After looking at the logs and the API specification i realised that if you do not pass an end date into the call, you do of course receive results back.
"body": { "1600034400": [ 0 ] },
"time_server": 1600113785These times are 1600034400 = 14.09.2020 00:00:00 and 1600113785 = 14.09.2020 22:03:05
But the request that is sent out asks for the data from one day earlier (begin 1599948000 = 13.09.2020 00:00:00, and end 1600034399 = 13.09.2020 - 23:59:59):
https://api.netatmo.com/api/getmeasure?scale=1day&date_begin=1599948000&real_time=True&access_token=xxxxx&module_id=xxxx&date_end=1600034399&type=sum_rain&device_id=xxxxx
Based on that observation, i would assume that i will see data showing up in RainMachine tomorrow. However, i would expect that it will request live data?! Eventually its also a matter of not using UTC time to determine the date range to request?
-
I am also getting this error Retrying: No Data Returned from my Netatmo PWS.
Need assistance getting this connected with Netatmo, please.



2021-05-16 20:31:17,052 - INFO - user-netatmo-parser:72 - Doing full auth
2021-05-16 20:31:19,419 - ERROR - user-netatmo-parser:210 - Error reading temperature module: list index out of range
2021-05-16 20:31:20,158 - ERROR - user-netatmo-parser:180 - Error reading rain gauge module: list index out of range
2021-05-16 20:31:20,758 - ERROR - user-netatmo-parser:190 - Error reading wind module: list index out of range
2021-05-16 20:31:20,807 - WARNING - rmParserManager:181 - * Parser Netatmo Parser returned no values
2021-05-16 20:32:08,772 - INFO - rmMainManager:239 - Upgrade checked.
2021-05-16 20:33:35,531 - ERROR - user-netatmo-parser:210 - Error reading temperature module: list index out of range
2021-05-16 20:33:36,066 - ERROR - user-netatmo-parser:180 - Error reading rain gauge module: list index out of range
2021-05-16 20:33:36,645 - ERROR - user-netatmo-parser:190 - Error reading wind module: list index out of range
2021-05-16 20:34:52,780 - INFO - rmMainManager:239 - Upgrade checked.
2021-05-16 20:36:15,010 - ERROR - user-netatmo-parser:210 - Error reading temperature module: list index out of range
2021-05-16 20:36:15,541 - ERROR - user-netatmo-parser:180 - Error reading rain gauge module: list index out of range
2021-05-16 20:36:16,225 - ERROR - user-netatmo-parser:190 - Error reading wind module: list index out of range
2021-05-16 20:39:17,561 - ERROR - user-netatmo-parser:210 - Error reading temperature module: list index out of range
2021-05-16 20:39:18,093 - ERROR - user-netatmo-parser:180 - Error reading rain gauge module: list index out of range
2021-05-16 20:39:18,625 - ERROR - user-netatmo-parser:190 - Error reading wind module: list index out of range
2021-05-16 20:43:19,766 - ERROR - user-netatmo-parser:210 - Error reading temperature module: list index out of range
2021-05-16 20:43:20,314 - ERROR - user-netatmo-parser:180 - Error reading rain gauge module: list index out of range
2021-05-16 20:43:20,881 - ERROR - user-netatmo-parser:190 - Error reading wind module: list index out of range
2021-05-16 20:44:31,720 - ERROR - netatmo-parser:209 - Error reading temperature module: list index out of range
2021-05-16 20:44:32,414 - ERROR - netatmo-parser:179 - Error reading rain gauge module: list index out of range
2021-05-16 20:44:32,961 - ERROR - netatmo-parser:189 - Error reading wind module: list index out of range
2021-05-16 20:44:32,963 - WARNING - rmParserManager:181 - * Parser Netatmo Parser returned no values -
I ultimately sent a support email, waited, and lo and behold, the next morning I received a response saying it appears to be working now. I don't know if they did something or it just magically started working. But I am now getting emails from my Rain Machine that inform me when periodic updates occur with my weather station...
-
"Necro-bumping" this post as I ran into the same issue today setting up a Netatmo for the first time.
Thanks to Mathias Kühn for the help as his post above very much identifies the "issue". (or being kind could be classified an undocumented feature vs an issue)
Basically, the parser is coded to retrieve "yesterday's" data from the Netatmo (in the local timezone of your RM). The date_begin and date_end arguments passed via the API are set for yesterday 00:00 to yesterday 23:59. As such if you setup a netatmo for the first time on a given day the parser will return the API error "list index out of range" as there is no data for "yesterday" yet. So, this means that the parser will continue to fail until midnight is crossed in your local timezone.
This is exactly what happened in my case, and after midnight the parser immediately began working properly.
Hopefully this saves someone else a few hours of debugging in the future :)
Please sign in to leave a comment.
Comments
16 comments