• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


OpenWeatherMap
#11
i have upgrade to the new nightly
now i hav the volow error:

Code:
[....] Starting : pilight[Jan 09 18:14:16:555685] pilight-daemon: ERROR: config device setting "update" of "tempaussen", missing
failed!
is this the "gui-show-update"?
 
Reply
#12
Just "update".
 
Reply
#13
Thank You it works.
can i make a rule like this?
Code:
IF openweathermap.sunset THEN switch DEVICE switch1 TO on
 
Reply
#14
Yes, there are several examples about this already on the forum.
 
Reply
#15
Hi,
I have created a new openweathermap device.

Code:
        "outside": {
            "protocol": [ "openweathermap" ],
            "id": [{
                "country": "de",
                "location": "wadersloh"
            }],
            "humidity": 70.00,
            "temperature": 7.80,
            "sunrise": 7.00,
            "sunset": 18.15,
            "sun": "rise",
            "poll-interval": 3600,
            "update": 0
        }

However when I do not have line
"poll-interval": 3600,
in my config, CPU rises to 100% and
service pilight stop
will say OK but leave a pilight-daemon in the backgrund, that still uses the whole CPU.
Code:
pilight-daemon -V
pilight-daemon version 6.0, commit v6.0-19-gafe5473
 
Reply
#16
I can't confirm :S
 
Reply
#17
Hardware is Raspi 2
Raspbian is up to date.
Even after several reboots the same.
 
Reply
#18
Can you try the latest nightly from github? I'm on the same hardware.
 
Reply
#19
pilight-daemon version 6.0, commit 13854fa
it is fine.. no trouble yet
 
Reply
#20
Running commit 92b8d15 of the development branch I now see an error in the openweathermap data.
The values of sunrise and sunset are always the same, both with the sunrise time.

I think one statement
Code:
time_t a = (time_t)sunset;
is missing in the protocol after line 222
 
Reply
  


Forum Jump:


Browsing: 2 Guest(s)