Yes they are the same in HA for darksky
do other parts get updated?
if i read the “job” well they should be updated every 15 minutes.
I tried using darksky weather id in different column and it works but how to update the default weather options. Do i use all different id for it.
the weather widget is like it is.
but you can use the sensor widget also for every element you want to see seperatly.
edit: you could also make changes to the haweather.html part from the widget.
Thank you for you answer. When typing:
sudo update-rc.d dashboard defaults
I get the following errors:
pi@raspberrypi:~/hadashboard $ sudo update-rc.d dashboard defaults
insserv: warning: script ‘K01dashboard’ missing LSB tags and overrides
insserv: warning: script ‘dashboard’ missing LSB tags and overrides
insserv: script dashing: service dashboard already provided!
Any help would be nice 
@vageesh79 I had this exact same issue when setting up HADashboard. I added all of the dark sky sensors to my sensors.yaml
# Weather
- platform: darksky
api_key: API-KEY-HERE
monitored_conditions:
- summary
- icon
- nearest_storm_distance
- nearest_storm_bearing
- precip_type
- precip_intensity
- precip_probability
- temperature
- apparent_temperature
- dew_point
- wind_speed
- wind_bearing
- cloud_cover
- humidity
- pressure
- visibility
- ozone
- minutely_summary
- hourly_summary
- daily_summary
- temperature_max
- temperature_min
- apparent_temperature_max
- apparent_temperature_min
- precip_intensity_max
You could go through each one and figure out which one is required, however I just hid all the ones I didn’t want from the HA UI.
1 Like
Following on from my previous issue I have done a bit more troubleshooting and this is the error I get when I make a change on HADash,
2016-12-12 19:26:22,932 INFO switch.bedroom -> state = off, brightness = 30
2016-12-12 19:26:22,946 WARNING Unexpected error calling Dashing: HTTPConnectionPool(host='http', port=80): Max retries exceeded with url: //10.3.6.250:3030/widgets/bedroom (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x762d0710>: Failed to establish a new connection: [Errno -2] Name or service not known',))
When I make a change on the HASS web UI I get the following error:
2016-12-12 19:28:38,073 INFO switch.bedroom -> state = on, brightness = 100
2016-12-12 19:28:38,090 WARNING Unexpected error calling Dashing: HTTPConnectionPool(host='http', port=80): Max retries exceeded with url: //10.3.6.250:3030/widgets/bedroom (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x762d08f0>: Failed to establish a new connection: [Errno -2] Name or service not known',))
The errors appear to be the same apart from this value 0x762d0710 in the HAS web UI change and this value 0x762d08f0 in the HADash change. I’m not sure if this is a red herring as this 0x value changes each time you toggled a light switch on or off on either the HADash or the HASS web UI.
Here is another error output when you CTRL+C out of hapush:
> 2016-12-12 21:01:45,142 CRITICAL Traceback (most recent call last):
> File “./hapush.py”, line 265, in run
> for msg in messages:
> File “/usr/local/lib/python3.4/dist-packages/sseclient.py”, line 64, in next
> nextline = self.resp_file.readline()
> File “/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/response.py”, line 380, in read
> data = self._fp.read(amt)
> File “/usr/lib/python3.4/http/client.py”, line 500, in read
> return super(HTTPResponse, self).read(amt)
> File “/usr/lib/python3.4/http/client.py”, line 529, in readinto
> return self._readinto_chunked(b)
> File “/usr/lib/python3.4/http/client.py”, line 614, in _readinto_chunked
> chunk_left = self._read_next_chunk_size()
> File “/usr/lib/python3.4/http/client.py”, line 552, in _read_next_chunk_size
> line = self.fp.readline(_MAXLINE + 1)
> File “/usr/lib/python3.4/socket.py”, line 371, in readinto
> return self._sock.recv_into(b)
> File “/usr/lib/python3.4/ssl.py”, line 745, in recv_into
> return self.read(nbytes, buffer)
> File “/usr/lib/python3.4/ssl.py”, line 617, in read
> v = self._sslobj.read(len, buffer)
Regardless of the error if I make a change and toggle a light on/off on the HASS web UI or I repeat the process on the HADash the changes are synced between each other, although you have to refresh the HADash webpage to see each change made from the HASS web UI.
@ReneTode I have tested removing every widget in main.erb except for 1 light switch (switch,bedroom) and I still get the above error on any light widget. This is how my widget is configured:
<ul>
<li data-row="1" data-col="1" data-sizex="2" data-sizey="1">
<div data-id="bedroom" data-view="Hadimmer" data-title="Bedroom" data-color="255,255,255"></div>
</li>
I have also tried this as the widget, but get same issue
<ul>
<li data-row="1" data-col="1" data-sizex="2" data-sizey="1">
<div data-id="bedroom" data-view="Hadimmer" data-title="Bedroom" data-color="#FF0000"></div>
</li>
The entity_id in HASS is light.bedroom, I read in the wiki that it is not possible to add the full entity_id such as light.bedroom into the widget. the “data-id” must be everything after the dot of the first part of the “entity_id” so “light.bedroom” would become “bedroom”. However this didn’t stop me from testing it with the full “entity_id” in “data-id” this didn’t work as expected
I’ve now also tested this with and without a HASS API-Key, with HASS on HTTPS and HTTP -no change in error
Any insight would be great
its not the connection to your hass server, but the connection to your dashboard server which gives the trouble.
but at this time i am at the end off my knowledge to where something could be wrong.
what i would like to see is what happens if you use just 1 sensor. does that update without errors?
and does it keep up to date?
going out off hapush always gives an error.
you only look at hapush, but what is in the logs from dashing?
just now my dashboard collapsed and then i get the same error in hapush.
so i get the idea that your dashboard isnt running correct.
I added a test.erb with 1 light only (bedroom) using the widget code above hapush errors the same.
i said sensor 
so a temperature, humidity, weather or any other sensor.
something which isnt interactive.
Sorry my bad… The only sensor I have is the weather, still waiting for some z wave stuff to arrive 
Although I dont see any errors on the the sensor I only get the error when switching lights on and off… Having said that I’ve not really checked the output monitoring only the weather. I’ll test it over night and see if I get any errors. 
Edit: having said that I have a Sonarr sensor, I could try and add that… When I switch on my home server the sensor will update and I can see if I get an error.
but what is in the log from dashing?
I don’t have anything to offer sorry, - does it work? The google tells me that the error is related to the # Provides bits of the two scripts but should be harmless.
### BEGIN INIT INFO
# Provides: dashboard
### BEGIN INIT INFO
# Provides: hapush
This is what I get in the Dashing log file
scheduler caught exception:
Connection refused - connect(2) for “10.3.6.250” port 8123
/usr/lib/ruby/2.1.0/net/http.rb:879:ininitialize' /usr/lib/ruby/2.1.0/net/http.rb:879:inopen’
/usr/lib/ruby/2.1.0/net/http.rb:879:inblock in connect' /usr/lib/ruby/2.1.0/timeout.rb:76:intimeout’
/usr/lib/ruby/2.1.0/net/http.rb:878:inconnect' /usr/lib/ruby/2.1.0/net/http.rb:863:indo_start’
/usr/lib/ruby/2.1.0/net/http.rb:852:instart' /usr/lib/ruby/2.1.0/net/http.rb:1369:inrequest’
/home/pi/hadashboard/jobs/homeassistant.rb:23:inha_api' /home/pi/hadashboard/jobs/homeassistant.rb:282:inblock in <top (required)>’
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:incall' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:intrigger_block’
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:inblock in trigger' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:incall’
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `block in trigger_job’
Maybe I should clarify the above error more clearly. I get this error when Dashing starts however it continues on and when I am making requests I can see those requests being actioned in the log as below
10.3.6.106 - - [12/Dec/2016 22:27:52] "POST /homeassistant/switch HTTP/1.1" 200 11 1.7172 10.3.6.106 - - [12/Dec/2016 22:27:59] "POST /homeassistant/switch HTTP/1.1" 200 11 1.3260 10.3.6.106 - - [12/Dec/2016 22:28:00] "POST /homeassistant/switch HTTP/1.1" 200 11 1.5390 10.3.6.106 - - [12/Dec/2016 22:28:32] "POST /homeassistant/switch HTTP/1.1" 200 11 1.4848 10.3.6.106 - - [12/Dec/2016 22:28:33] "POST /homeassistant/switch HTTP/1.1" 200 11 0.7478 10.3.6.106 - - [12/Dec/2016 22:29:21] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.5147 10.3.6.106 - - [12/Dec/2016 22:29:38] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.3139 10.3.6.106 - - [12/Dec/2016 22:29:41] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.4995 10.3.6.106 - - [12/Dec/2016 22:29:49] "POST /homeassistant/dimmerLevel HTTP/1.1" 200 11 0.4331 10.3.6.106 - - [12/Dec/2016 22:29:53] "POST /homeassistant/dimmerLevel HTTP/1.1" 200 11 0.3037 10.3.6.106 - - [12/Dec/2016 22:29:57] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.4084 10.3.6.106 - - [12/Dec/2016 22:30:00] "POST /homeassistant/dimmerLevel HTTP/1.1" 200 11 0.4699 10.3.6.106 - - [12/Dec/2016 22:30:06] "POST /homeassistant/dimmerLevel HTTP/1.1" 200 11 0.3022 10.3.6.106 - - [12/Dec/2016 22:30:11] "POST /homeassistant/dimmerLevel HTTP/1.1" 200 11 0.2705 10.3.6.106 - - [12/Dec/2016 22:31:51] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.7327 10.3.6.106 - - [12/Dec/2016 22:31:53] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.4799 10.3.6.106 - - [12/Dec/2016 22:31:57] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.3056
and the above actions are syncing on the HAS web UI when changed on Dashing. Also when I turn the lights on/off via Dashing they turn on/off in RL 
I’m sure I’ve seen a similar issue further up the thread although I’m not sure if there was a resolution…
your dashboard isnt connecting to hass.
now you have to check this out with all the settings you tried before. (http, https, the right password, etc)
i think its a problem in your config.
guess you have to read back then.
i am quite sure that there was a solution if it was the same problem.
i cant recall any problem that andrew didnt resolve
@ReneTode
Having just stepped through the log with your comments in mind I was trying to think what it could be… 
I’m pretty sure the error in the log is actually caused as you say by not being able to connect to HASS. To test this I rebooted the PI and upon reboot Dashing initialises quicker than HASS and polls HASS continuously with errors until HASS has booted and Dashing connects. I’m pretty sure that’s what is causing the above error in the log
Further down the log you can see Dashing connect to HASS and then everything works and logs as expected and as already posted above.
not all is working as expected.
you shouldnt get connection errors in hapush when dasboard is running correctly.
and your dashboards should be automaticly updated if you have hapush running.
@ReneTode
Yes your right not all is as expected with hapush, but I’m also not really to sure how to progress with that. Other sensors give no errors it would seem the weather has changed by 1 degree and no error. Its down to the lights I’m not sure what is causing it though…