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…
That worked great 
Yay I’m glad you got it working 
I think I’ve narrowed down this error to be hapush updating the state on the dashboard and I am basing this on powers of deduction and the sequence of how the error is produced in the hapush output
2016-12-12 23:53:41,106 INFO switch.bedroom -> state = on, brightness = 20
2016-12-12 23:53:41,118 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 0x7625e790>: Failed to establish a new connection: [Errno -2] Name or service not known',))
The error is produced when the light state changes and you make the change on the HASS web UI. the change is not reflected on the dashboard.
Another way to recreate the error is to use the dimmer widget and click the + the light switches on but the state change on the dimmer widget does not activate and the error in hapush is written to the output.
I also expect that even though the dashboard earlier appeared (at least to me) to be functioning correctly, the light.bedroom state change would have been toggled because it was clicked. hapush produced an error in the output as it could not update the state change to the dashboard, however the state change appeared to be active as the mouse click had activated the change on the dashboard.
It dosn’t work. I think a complete reinstall and setup of Hass and HADashboard is the next thing to try 
But thank you for your help
I’ve had Hadashboard up and running for a few weeks now without any issues. I had to reboot my system this morning and when I tried to do dashing start I got the below error. Has anyone seen this?
pi@raspberrypi:~/hadashboard $ dashing start
bundler: failed to load command: thin (/usr/local/bin/thin)
SyntaxError: /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1/file/exists.rb:1: Invalid char \x02' in expression /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1/file/exists.rb:4: syntax error, unexpected tCONSTANT, expecting keyword_end 0 Backports.convert_first_aZgument_to_path File, :exists? ^ /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1/file/exists.rb:5: invalid multibyte char (UTF-8) /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1/file/exists.rb:5: syntax error, unexpected end-of-input, expecting keyword_end /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require_with_backports' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:10:in block in require_relative_dir’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:9:in each' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:9:in require_relative_dir’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1/file.rb:3:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require_with_backports' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:10:in block in require_relative_dir’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:9:in each' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/tools/require_relative_dir.rb:9:in require_relative_dir’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.1.rb:3:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.2.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.2.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.3.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.3.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/1.9.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.0.0.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.0.0.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.0.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.0.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.1.0.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.1.0.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.1.rb:2:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports/2.1.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports.rb:3:in require’
/var/lib/gems/2.1.0/gems/backports-3.6.8/lib/backports.rb:3:in <top (required)>' /var/lib/gems/2.1.0/gems/sinatra-contrib-1.4.7/lib/sinatra/capture.rb:3:in require’
/var/lib/gems/2.1.0/gems/sinatra-contrib-1.4.7/lib/sinatra/capture.rb:3:in <top (required)>' /var/lib/gems/2.1.0/gems/sinatra-contrib-1.4.7/lib/sinatra/content_for.rb:2:in require’
/var/lib/gems/2.1.0/gems/sinatra-contrib-1.4.7/lib/sinatra/content_for.rb:2:in <top (required)>' /var/lib/gems/2.1.0/gems/dashing-1.3.7/lib/dashing/app.rb:3:in require’
/var/lib/gems/2.1.0/gems/dashing-1.3.7/lib/dashing/app.rb:3:in <top (required)>' /var/lib/gems/2.1.0/gems/dashing-1.3.7/lib/dashing.rb:3:in require’
/var/lib/gems/2.1.0/gems/dashing-1.3.7/lib/dashing.rb:3:in <top (required)>' config.ru:1:in require’
config.ru:1:in block in <main>' /var/lib/gems/2.1.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval’
/var/lib/gems/2.1.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize' config.ru:1:in new’
config.ru:1:in <main>' /var/lib/gems/2.1.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in eval’
/var/lib/gems/2.1.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in load' /var/lib/gems/2.1.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:182:in load_rackup_config’
/var/lib/gems/2.1.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:72:in start' /var/lib/gems/2.1.0/gems/thin-1.6.4/lib/thin/runner.rb:200:in run_command’
/var/lib/gems/2.1.0/gems/thin-1.6.4/lib/thin/runner.rb:156:in run!' /var/lib/gems/2.1.0/gems/thin-1.6.4/bin/thin:6:in <top (required)>’
/usr/local/bin/thin:23:in load' /usr/local/bin/thin:23:in <top (required)>’
could it be that you changed something since you last restarted the dashboard?
if not i am afraid that 1 or more files are corrupted.
I don’t think so. I’ve haven’t really had a chance to make any changes. But I agree with some file corruption because I tried updating to the newest version of HASS and received an error.
then i hope you have a backup.
if not then this is a lesson.
i have a sdcard ready with an image from a fully functional pi with hass, dashboard and appdaemon.
i make a regular data backup over the network to my pc. so if the sdcard get corrupted (and now i know that that isnt rare) i can get it back working in minutes.
I learned my lesson a few months ago when the SD card become corrupt. This seems to be more frequent than I realized.
This corruption isn’t as bad as my last. The last time the system wouldn’t even boot up. Do I need to reformat the SD card or can I just replace the current files with my back up files?
i would try to replace first.
when after that everything is working again i would let it be that way after a diskcheck.
if you want to be sure you could reformat.
but then you need a complete image and lose all sensordata if you dont save that before.
This is a little off subject here, but this whole conversation is wandering around a good bit so here goes.
I do my nightly backup to a usb stick attached to my PI. What type of performance hit do you think I would take if I ran HA and AppDaemon off of that drive? It mounts every time I boot so it would be there…
i dont think there would be a big performance difference between an external sd or an internal sd.
but thats just my gut talking.
but i dont think it would bring a lot. you still wouldnt have a backup.
and if things get corrupted you could endup with 2 things to replace.
Yes you need the full scheme (http or https)
In the hapush.cfg file - can you post what you have for us?
hapush.cfg
ha_url = "https://10.3.6.250:8123" ha_key = API-Key-Here dash_host = "http://10.3.6.250:3030" dash_dir = "/home/pi/hadashboard/dashboards" logfile = "/etc/hapush/hapush.log"
ha_confi.rb
$ha_url = "https://10.3.6.250:8123" $ha_apikey = "API-Key-Here"
$news_feeds = { "Traffic" => "http://api.sr.se/api/rss/traffic/2863", "News" => "http://feeds.bbci.co.uk/news/rss.xml", }
Edit: corrected a typo in http