You can’t make changes to the docker image easily so I would suggest the normal installation style if you want to customize.
1 Like
There are some very specific instructions about file locations for hapush if you are running docker - did you follow those?
In particular, from the docs:
logfile is the path to where you want hapush to keep its logs. When run from the command line this is not used - log messages come out on the terminal. When running as a daemon this is where the log information will go. In the example above I created a directory specifically for hapush to run from, although there is no reason you can’t keep it in the hapush subdirectory of the cloned repository. For Docker installs this should be set to /app/hapush/hapush.log
This looks like some kind of corruption in your dashboard.
Recommended course of action being to blow it away and start over? Keeping custom configs of course
if it is a problem in your dashboard then starting over wont make the problem go away if you reuse those after reinstalling.
i think you better open the dashboard in an editor, save it with a new name and make sure its saved as ascii
I don’t think the problem is in the dashboard. I’ve tried removing all my custom dashboards and just having the default one in place, and docker still won’t start.
I was able to get it running by starting over and not using docker this time, however I’m struggling to get the service working right to have it run in the background. Right now, I can only start by running “dashing start”, but I’d like it to run as a service in the background instead.
with that part i cant help. i never use daemons.
i have done extra work to get it started at startup in a terminal.
Has anyone gotten dasher/hapush running at startup as a daemon on a CentOS box (systemd)?
There are sample systemd scripts in the init directory called dashing.service and hapush.service - they rely on the other scripts in there, which are standard init scripts.
Yeah, I’ve been trying to work with those, but have had no luck getting anything working yet
Any Help I can’t find the solution for the Grey Screen, I get it all running no errors in log but screen is just grey. Removed the Weather widgets to see if that was the problem still grey. Stock example or other dashboard I was using before still grey.
192.168.0.203 - - [20/Jan/2017 11:19:02] "GET /events?lastEventId=&r=9849932772759122 HTTP/1.1" 200 - 4.9933
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
192.168.0.203 - - [20/Jan/2017 11:19:02] "GET /example HTTP/1.1" 200 12320 0.0080
192.168.0.203 - - [20/Jan/2017 11:19:02] "GET /events?lastEventId=&r=9849932772759122 HTTP/1.1" 200 - 4.9933
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
192.168.0.203 - - [20/Jan/2017 11:19:12] "GET /main HTTP/1.1" 200 3640 0.0032
192.168.0.203 - - [20/Jan/2017 11:19:12] "GET /events?lastEventId=&r=5216548200456779 HTTP/1.1" 200 - 8.7441`
I Lied there is an error:
```2017-01-20 11:28:16,182 CRITICAL ------------------------------------------------------------
2017-01-20 11:28:21,187 CRITICAL Unexpected error:
2017-01-20 11:28:21,188 CRITICAL ------------------------------------------------------------
2017-01-20 11:28:21,188 CRITICAL Traceback (most recent call last):
File "/usr/src/app/hapush/hapush.py", line 265, in run
for msg in messages:
File "/usr/local/lib/python3.4/dist-packages/sseclient.py", line 64, in __next__
self.buf += nextline
TypeError: Can't convert 'bytes' object to str implicitly`
Any Ideas?The HAPUSH error has nothing to do with the grey screen - what browser are you using?
Im stuck, using the docker install for pi Im getting this when dashing start
Could not find gem ‘data_mapper’ in any of the gem sources listed in your Gemfile or available on this machine.
Run bundle install to install missing gems.
And did you run bundle install ?
yup, follow all the steps. Manage to make it work at the end, I was missing thin. Now, I just need to figure it out how to start it at the boot.
1 Like
I have the same issue when not using the docker installation
Do you have an up to date version of SSE Client? And are you maybe using SSL?
So I have a template sensor setup to determine trash day, it shows correct on my Front end and HADashboard the first time, but I couldn’t get it updated via hapush. It’s just a sensor like other sensor but I got updated via hapush perfectly (like weather…)… Today it keeps saying 6, where it is supposed to be 5… and I click Reload on the HaDashboard and it loads the right data…
what gives? what did I do wrong? I need an extra set of eyes. It has to be something really small that I can’t see 
<li data-row="3" data-col="1" data-sizex="1" data-sizey="1">
<div data-id="until_trash_day" data-view="Hasensor" data-title="Trash Day In" data-unit="Days" data-color="#FF0000"></div>
</li>
sensor:
- platform: template
sensors:
trash_day_number:
value_template: >
{% if is_state("input_select.trash_day","Sun") %}
6
{% elif is_state("input_select.trash_day","Mon") %}
0
{% elif is_state("input_select.trash_day","Tue") %}
1
{% elif is_state("input_select.trash_day","Wed") %}
2
{% elif is_state("input_select.trash_day","Thu") %}
3
{% elif is_state("input_select.trash_day","Fri") %}
4
{% elif is_state("input_select.trash_day","Sat") %}
5
{% endif %}
until_trash_day:
friendly_name: 'Trash Day In'
value_template: >
{{ (states('sensor.trash_day_number')|int - now().weekday()) % 7 }}
unit_of_measurement: 'days'It is a Docker