Beta 2020.3
Raspberry 3B+
After adding the Accuweather service "hardware", no device appears. The only thing relevant in the logs is: "AccuWeather: Worker stopped..." and no evidence that it tried to start. Where to from here?
EDIT: After some time, this appears in the error log: "Error: AccuWeather: Error getting http data!"
Accuweather configuration
Moderator: leecollings
-
- Posts: 32
- Joined: Saturday 03 August 2019 7:32
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.2
- Location: Netherlands, Heiloo
- Contact:
Re: Accuweather configuration
Hi, you have to make a API key on de developers site from Accuweather.
Also the longitude, latitude must be reversed from the description next to it.
Than you will see directly on devices the new devices.
Also the longitude, latitude must be reversed from the description next to it.
Than you will see directly on devices the new devices.
Starter RPi3B, Domoticz Stable 2020.2, 10x Qubino Mini Dimmer, 1x Qubino shutter
Plugwise Anna + Adam + 2x Koen-4 & 1x Floor; SolarEdge SE3000H
Dashticz v3
Plugwise Anna + Adam + 2x Koen-4 & 1x Floor; SolarEdge SE3000H
Dashticz v3
-
- Posts: 2
- Joined: Tuesday 19 January 2021 9:18
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Accuweather configuration
Well, same problem here.
The API key is correct, I tested it on accuweather website
The location is 962177 and is also correct, as tested on accuweather website.
The location in setup screen has been set as follows:
962177
50.475,3.907 (doesn't work), although it's the Long LAt given by accuweather itself in the response to the queries
3.907,50.475 (doesn't work), reversed as indicated
There must be something wrong elsewhere because nothing works
Is there a way to check the code that is run by Domoticz somewhere in the logs?
NRJ
The API key is correct, I tested it on accuweather website
The location is 962177 and is also correct, as tested on accuweather website.
The location in setup screen has been set as follows:
962177
50.475,3.907 (doesn't work), although it's the Long LAt given by accuweather itself in the response to the queries
3.907,50.475 (doesn't work), reversed as indicated
There must be something wrong elsewhere because nothing works
Is there a way to check the code that is run by Domoticz somewhere in the logs?
NRJ
-
- Posts: 2
- Joined: Tuesday 19 January 2021 9:18
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Accuweather configuration
Some additionnal info:
the link: https://dataservice.accuweather.com/cur ... tails=true
(I changed some characters in the API key => the link above will not work as such)
But the link does work with the right key and proves that the APi and location are correct. These are the only parameters you can enter in the Hardware definition.
I also checked the code in https://github.com/domoticz/domoticz/bl ... eather.cpp
The code looks ok although there are multiple places that can return "Error: Error parsing http request" that I get repeatedly in my log.
What's wrong then? I don't know. Hard to say without debug.
There is a debug mode foreseen in the code that refers to loading the data from a local file "E:\\AccuWeather_LocationSearch.json", but it seems to be for Windows users, which I'm not. Strange indeed that it's hardcoded like that.
So, I'm stuck, the only other option I have is OpenWeather or develop the lua scripts myself and provide the json-decoded data to virtual sensors. But that's really a pity.
NRJ
the link: https://dataservice.accuweather.com/cur ... tails=true
(I changed some characters in the API key => the link above will not work as such)
But the link does work with the right key and proves that the APi and location are correct. These are the only parameters you can enter in the Hardware definition.
I also checked the code in https://github.com/domoticz/domoticz/bl ... eather.cpp
The code looks ok although there are multiple places that can return "Error: Error parsing http request" that I get repeatedly in my log.
What's wrong then? I don't know. Hard to say without debug.
There is a debug mode foreseen in the code that refers to loading the data from a local file "E:\\AccuWeather_LocationSearch.json", but it seems to be for Windows users, which I'm not. Strange indeed that it's hardcoded like that.
So, I'm stuck, the only other option I have is OpenWeather or develop the lua scripts myself and provide the json-decoded data to virtual sensors. But that's really a pity.
NRJ
-
- Posts: 56
- Joined: Friday 04 August 2017 16:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Accuweather configuration
I'm digging up this old topic because I get exactly the same behavior. I'm using locationkey instead of lat/long because accuwetaher API only refer to this and when using an http request taken from code (after replacing variable parts) it works flowlessly ...
-
- Posts: 84
- Joined: Sunday 14 August 2016 13:45
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2020.1
- Location: Netherlands
- Contact:
Re: Accuweather configuration
Same here, I have tried with locationkey and lat,long, but when adding the hardware, no devices appear. Nor do I get an error in the log. Anyone got this working?
- epierre
- Posts: 522
- Joined: Wednesday 05 March 2014 13:16
- Target OS: Linux
- Domoticz version:
- Location: France
- Contact:
Re: Accuweather configuration
same here, seems an issue from domoiticz since api is correct and valid
ImperiHome & MyDomoAtHome on top of:
868.42Mhz - Vera Lite - Fibaro SS-101, S-211, K-101, FWP - Fortress SSA2
433Mhz - Cubie Domoticz + RFXtrx + Oregon || Foscam 9821W
2,4Ghz - Cubie MySensors Gateway + COV + TempHumidity + Pressure + WaterMeter
868.42Mhz - Vera Lite - Fibaro SS-101, S-211, K-101, FWP - Fortress SSA2
433Mhz - Cubie Domoticz + RFXtrx + Oregon || Foscam 9821W
2,4Ghz - Cubie MySensors Gateway + COV + TempHumidity + Pressure + WaterMeter
Who is online
Users browsing this forum: No registered users and 1 guest