that is somewhat like in the past we did create a virtual harddrive or cdromplayer.
it wasnt a real harddrive, but a dir we could use the same way as a harddrive.
everything you do when you are in a virtual enviroment wont effect other enviroments.
so if you install dashboard when your hass enviroment is activated you could afterwards delete everything related to hass at once.
i am not a fan off virtualenv, but i think if you use it, probably the preffered way would be to create a new enviroment for dashboard.
but i am not sure if there would be any fileright problems (i cant think of any at this moment, but it could be)
Just to be clear - you don;t have to use Docker on Raspbian, you can also use the manual install instructions. Id you do decide to go down the docker route, you need to use the Raspbian specific docker image - thatâs what the instructions were trying to convey.
So then, if I did that (and would probably take that route due to limited knowledge of docker), would I then want to be working within my virtualenv I have Home Assistant installed in, or does that not really matter?
Also, looking at those directions, how does one go about install Ruby? Is it just:
The Virtual Env is optional, and only applies to ther HAPush piece - Virtualenv is a Python thing. You don;t have to use a Virtualenv if you don;t want to - I donât.
My PI came with Ruby already installed, if you donât have it, I would first try something like:
pi@raspberrypi:~/hadashboard $ dashing start
Thin web server (v1.6.4 codename Gob Bluth)
Maximum connections set to 1024
Listening on 0.0.0.0:3030, CTRL+C to stop
scheduler caught exception:
Connection reset by peer
/usr/lib/ruby/2.1.0/net/protocol.rb:153:in read_nonblock' /usr/lib/ruby/2.1.0/net/protocol.rb:153:in rbuf_fillâ
/usr/lib/ruby/2.1.0/net/protocol.rb:134:in readuntil' /usr/lib/ruby/2.1.0/net/protocol.rb:144:in readlineâ
/usr/lib/ruby/2.1.0/net/http/response.rb:39:in read_status_line' /usr/lib/ruby/2.1.0/net/http/response.rb:28:in read_newâ
/usr/lib/ruby/2.1.0/net/http.rb:1408:in block in transport_request' /usr/lib/ruby/2.1.0/net/http.rb:1405:in catchâ
/usr/lib/ruby/2.1.0/net/http.rb:1405:in transport_request' /usr/lib/ruby/2.1.0/net/http.rb:1378:in requestâ
/usr/lib/ruby/2.1.0/net/http.rb:1371:in block in request' /usr/lib/ruby/2.1.0/net/http.rb:853:in startâ
/usr/lib/ruby/2.1.0/net/http.rb:1369:in request' /home/pi/hadashboard/jobs/homeassistant.rb:23:in ha_apiâ
/home/pi/hadashboard/jobs/homeassistant.rb:282:in block in <top (required)>' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in callâ
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in trigger_block' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in block in triggerâ
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in call' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in block in trigger_jobâ
================================================================================
scheduler caught exception:
Connection refused - connect(2) for âtrafiknyt.smartlog.dkâ port 80
/usr/lib/ruby/2.1.0/net/http.rb:879:in initialize' /usr/lib/ruby/2.1.0/net/http.rb:879:in openâ
/usr/lib/ruby/2.1.0/net/http.rb:879:in block in connect' /usr/lib/ruby/2.1.0/timeout.rb:76:in timeoutâ
/usr/lib/ruby/2.1.0/net/http.rb:878:in connect' /usr/lib/ruby/2.1.0/net/http.rb:863:in do_startâ
/usr/lib/ruby/2.1.0/net/http.rb:852:in start' /usr/lib/ruby/2.1.0/open-uri.rb:313:in open_httpâ
/usr/lib/ruby/2.1.0/open-uri.rb:724:in buffer_open' /usr/lib/ruby/2.1.0/open-uri.rb:210:in block in open_loopâ
/usr/lib/ruby/2.1.0/open-uri.rb:208:in catch' /usr/lib/ruby/2.1.0/open-uri.rb:208:in open_loopâ
/usr/lib/ruby/2.1.0/open-uri.rb:149:in open_uri' /usr/lib/ruby/2.1.0/open-uri.rb:704:in openâ
/usr/lib/ruby/2.1.0/open-uri.rb:34:in open' /home/pi/hadashboard/jobs/news.rb:31:in latest_headlinesâ
/home/pi/hadashboard/jobs/news.rb:66:in block (2 levels) in <top (required)>' /home/pi/hadashboard/jobs/news.rb:65:in eachâ
/home/pi/hadashboard/jobs/news.rb:65:in block in <top (required)>' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in callâ
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in trigger_block' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in block in triggerâ
/var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in call' /var/lib/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in block in trigger_jobâ
Looks like you have the settings for your home assistant instance url incorrect in ha_conf.rb - that is the piece of code where it tries to contact Home Assistant and it is getting a connection refused.
Make sure you are using the right scheme (https vs http) and that the IP address is correct.
okay. have tried with both https and http.
my rpi are on internal ip address 192.168.0.32, but when i try to connect to my HA install via internal ip address (192.168.0.32:8123) i cant connect to HA, only if i use https infront of the ip address and then its telling me its not a secure connection.
I have set up encryption with duckdns and letsencrypt, so i think that i need some sort of portforwarding. Could it be the problem?
just logged in to HA via my duckdns address and now it tells me: Login attempt failed, Invalid password used from 192.168.0.32, which is my rpi and where HADashboard is installed, is it possible to add my HA password in the ha_conf.rb file?
i have mistakenly deleted my example.erb file, and can read that i shouldnât have done that to avoid problems when ugrading. is it possible to get that file again?
I would guess so - looks like a bunch of basics arenât there - it should still be possible you will just need to do a few extra steps as we are finding out.
I think because of that, Iâm going to redo the SD Card with the full Raspian to see if that helps. I donât really care, I just like working from terminal instead of loading up the Graphical UI, but I can change those settings in the raspi-conf settings. For what itâs worth, i just had to use:
sudo gem install dashing
This got it going, but then I got this error at the end: