Announcement: HADashboard v1.72

[aimc (Andrew Cockburn)]

Two ctrl-c is expected behavior, but i am not clear what the issue is?

[GraysonPeddie]

I followed the instructions to configure hapush in here:
https://home-assistant.io/ecosystem/hadashboard/hapush/

It seems hapush is not responding to events. I turned on the switch for Living Room Lights in Home Assistant, but the HADashboard did not react to changes. I have to refresh the HADashboard to see that the light is on. I can click in the Living Room Lights inside the HADashboard and the frontend of Home Assistant reacts to changes. I opened up HADashboard in my tablet to do the same to see if HADashboard in my desktop reacts to changes as well.

I have HADashboard web page opened in Google Chrome in my desktop.
I also have HADashboard shown up in my smartphone.

Both my desktop and smartphone points to http://192.168.0.2:3030/main.

Turning on the Living Room Lights from my smartphone shows it as on, but in my desktop, the dashboard shows it as “off.” Turning on the Living Room Lights from my desktop would simply do nothing but set the state to “on.” Turning off the Living Room Lights from my smartphone will still show it as “on” in my desktop.

I turned on DEBUG mode for hapush and it seems hapush is listening to Home Assistant’s change in state, but it’s not listening to HADashboard’s change in state in both my desktop and smartphone.

[hass@home-server hapush]$ ./hapush.py hapush.cfg -D DEBUG 2016-12-28 20:22:41,004 INFO Reading dashboard: /fileserver/users/homeassistant/hadashboard/dashboards/example.erb 2016-12-28 20:22:41,010 INFO Reading dashboard: /fileserver/users/homeassistant/hadashboard/dashboards/main.erb 2016-12-28 20:22:55,677 DEBUG Event type:call_service: 2016-12-28 20:22:55,823 DEBUG Event type:state_changed: 2016-12-28 20:22:55,823 DEBUG Entity ID:light.living_room_lights: 2016-12-28 20:22:55,958 DEBUG Event type:state_changed: 2016-12-28 20:22:55,959 DEBUG Entity ID:group.all_lights: 2016-12-28 20:22:55,986 DEBUG Event type:service_executed: 2016-12-28 20:23:00,675 DEBUG Event type:state_changed: 2016-12-28 20:23:00,675 DEBUG Entity ID:sensor.date__time: 2016-12-28 20:23:30,873 DEBUG Event type:state_changed: 2016-12-28 20:23:30,874 DEBUG Entity ID:sun.sun: 2016-12-28 20:23:32,982 DEBUG Event type:call_service: 2016-12-28 20:23:33,074 DEBUG Event type:service_executed: 2016-12-28 20:23:46,707 DEBUG Event type:call_service: 2016-12-28 20:23:46,848 DEBUG Event type:state_changed: 2016-12-28 20:23:46,848 DEBUG Entity ID:light.living_room_lights: 2016-12-28 20:23:46,984 DEBUG Event type:state_changed: 2016-12-28 20:23:46,985 DEBUG Entity ID:group.all_lights: 2016-12-28 20:23:47,012 DEBUG Event type:service_executed: 2016-12-28 20:23:57,506 DEBUG Event type:call_service: 2016-12-28 20:23:57,600 DEBUG Event type:service_executed: 2016-12-28 20:24:00,585 DEBUG Event type:state_changed: 2016-12-28 20:24:00,585 DEBUG Entity ID:sensor.date__time:

I messed with the frontend to see if HAPush is listening and I saw media_player.living_room_receiver (which is my Marantz SR5008 receiver, by the way) and at least it’s working. Alas, the receiver is not in my HADashboard.

I hope I can be of help.

[rpitera (Robert Pitera)]

@aimc - Any ideas about my issue?

[aimc (Andrew Cockburn)]

Hi Rob - sorry I missed this. I don’t really have anything to add as I am not using the IFrame widget, and nothing in any of my updates should have made any difference to it.

[rpitera (Robert Pitera)]

No problem - thanks. I just don’t understand what happened as I didn’t change anything on my end during the updates but maybe I’ll just delete it and start from scratch again. Cheers.

[aimc (Andrew Cockburn)]

Looks looks a config issue - HAPush sees the events but does not act on them, my guess would be because the widget names in the dashboard don’t match the entity ids you have for the various devices - can you check that, and maybe post a sample of your dashboard code?

[ReneTode]

ill try to implement your iframe tonight and see what could be the problem.

[GraysonPeddie]

Here you go:

main.erb:

[code]

<li data-row="2" data-col="1" data-sizex="1" data-sizey="1">
  <div data-id="Living_Room_Lights" data-title="Living Room Lights" data-view="Hadimmer"></div>
</li>

<li data-row="2" data-col="2" data-sizex="1" data-sizey="1">
  <div data-id="Bedroom_Lights" data-title="Bedroom Lights" data-view="Hadimmer"></div>
</li>

<li data-row="1" data-col="3" data-sizex="1" data-sizey="1">
  <div data-id="Game_in_PS3" data-title="Game in PS3" data-view="Hascene" data-bgcolor="#003300"></div>
</li>

<li data-row="1" data-col="4" data-sizex="1" data-sizey="1">
  <div data-id="Movie_Time" data-title="Movie Time" data-view="Hascene" data-bgcolor="#003300"></div>
</li>

<li data-row="2" data-col="3" data-sizex="1" data-sizey="1">
  <div data-id="Main_PC" data-title="PC" data-view="Hascene" data-bgcolor="#003300"></div>
</li>

<li data-row="2" data-col="4" data-sizex="1" data-sizey="1">
  <div data-id="Relax" data-title="Relax" data-view="Hascene" data-bgcolor="#003300"></div>
</li>

<li data-row="3" data-col="3" data-sizex="2" data-sizey="1">
  <div data-id="Watch_Sat_TV" data-title="Watch TV over Satellite" data-view="Hascene" data-bgcolor="#003300"></div>
</li>

[/code]

Home Assistant - light.yaml:

[code] - platform: insteondimmeroh
name: “Living Room Lights”
resource: http://localhost:8080/rest/items/ldLRLamps

• platform: insteondimmeroh
  name: “Bedroom Lights”
  resource: http://localhost:8080/rest/items/ldBRLamps[/code]

insteondimmeroh comes from here:

Problem with Insteon

There is no “attach file” here so I am going to paste the component. Save it as insteondimmeroh.py and place in your custom_components\light folder. """ Openhab light platform that implements lights. """ import logging import requests from homeassistant.components.light import ( ATTR_BRIGHTNESS, Light) _LOGGER = logging.getLogger(__name__) DEFAULT_NAME = "Openhab Insteon Dimmer" DEFAULT_BRIGHTNESS = "255" def setup_platform(hass, config, add_devices_callback, discovery_info=None)…

Once again, Home Assistant is able to respond to button presses. Here’s the output from Dashing. I turn off the “Living Room Lights” and turned it back on.

192.168.0.166 - - [29/Dec/2016 11:42:19] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.0961 192.168.0.166 - - [29/Dec/2016 11:42:24] "POST /homeassistant/dimmer HTTP/1.1" 200 11 0.0914

[ReneTode]

what is the configfile from hapush?

to me it seems that hapush isnt pushing, so maybe is the given url wrong?

[GraysonPeddie]

I will post it again from one of my previous posts.

@GraysonPeddie

[hass@home-server hapush]$ cat hapush.cfg
ha_url = “http://192.168.0.2:8123”
ha_key = …secret…
dash_host = “192.168.0.2:3030”
dash_dir = “/fileserver/users/homeassistant/hadashboard/dashboards”
logfile = “/fileserver/users/homeassistant/hadashboard/hapush/hapush.log”

Both Home Assistant, HADashboard, and HAPush are in the same machine.

[ReneTode]

and suddenly it hits me.

data-id=“Living_Room_Lights”

probably is wrong and should be

data-id=“living_room_lights”

hass doesnt have capitals in the entity IDs.

[GraysonPeddie]

HASS seems to be case-insensitive and HAPush does not acknowledge that and you know what? You are right! After I modify the .erb file, it worked!!! Shouldn’t that be documented in HADashboard/HAPush or am I missing something in documentation?

Update after a while: Maybe HADashboard and HAPush needs to convert upper/lower case entity_id variables to lowercase using an entity_id.lower() function where “entity_id” is a string variable…If I have left the data-id"" entity ID variables before, Home Assistant responds just fine. Maybe have something like this in an “if” statement such as:

[code]if((“Living_Room_Lights”).lower() == (“living_room_lights”).lower())

Then respond to event

[/code]

I might look into the code although I have never done any programming with Python.

Update 2: The code does have syntax error, so I’m going to go through a Python tutorial to learn Python. It’s only a pseudo code.

[ReneTode]

it is strange that hass responses anyway.
within hass there are several places where i have struggled with capitals in the beginning. since then i only use capitals in friendly names.

because you are expected to use entity IDs exactly like in hass and because hass doesnt have capitals in its entity IDs there is no need to check for capitals in the Dashboard and Hapush.

[GraysonPeddie]

HASS did not expect me to use lowercase letters for entity IDs. If it does, it should have said say in the log file.

[ReneTode]

robert i created a new erb file with this code:

<div class="gridster">
  <ul>
    <li data-row="1" data-col="1" data-sizex="5" data-sizey="4">
     <div data-id="iframeId1" data-view="Iframe" data-src="https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=EWR&brand=wui&num=10&delay=25&type=TR0&frame=0&scale=1.000&noclutter=0&showstorms=0&mapx=400&mapy=240&centerx=400&centery=240&transx=0&transy=0&showlabels=1&severe=0&rainsnow=1&lightning=0&smooth=0&rand=24562171&lat=0&lon=0&label=you"></div>
    </li>
  </ul>
</div>

and it displayed this:

when i started the try out i made an error in the file outside the widget and got a simular view you showed.
so maybe the problem is in another part from the file then the part you posted.

please try the code i gave as a new erb file to see if that functions correct for you.

[ReneTode]

you can check out your entity IDs in Hass.
just go to developerstools in your frontend and chose the second 1. (states)
you will see all your entities and you will see that all your entities are in lower case.

you gave it a neme with upper cases, but the entity ID is in lower case only. ALL entity IDs are.
if you are creating automations in hass and you use upper cases in entity IDs you will also get into trouble.

[GraysonPeddie]

Okay, great. I’m in trouble because I did not HASS is case-sensitive for entity IDs. Will make sure to use lowercase in entity IDs in YAML files. HASS did not tell me that entity IDs need to be in lower-case. Not even in home-assistant.log.

Perhaps the next version of HASS will tell me that light.Living_Room_Lights is invalid. I tried changing to this:

- name: Movie Time entities: light.LIVING_ROOM_LIGHTS: state: "on" brightness: 1 light.Bedroom_Lights: state: "off" media_player.living_room_receiver: source: "Android TV"

And it works. No error in home-assistant.log.

[ReneTode]

i didnt know it for a long time to.
in many cases hass just translates all upper cases in names automaticly to lower cases.
thats also the case in your case.

but if you make an automation you need to call them exactly like hass hass created them, so in lower cases

i see your example now and thats still 1 of the things i see in hass. it isnt Always consistant.

i created this light this weekend:

light:
  platform: limitlessled
  bridges:
    - host: 192.168.1.12
      groups:
      - number: 1
        name: Vitrine in de gang

and now the name from the entity is light.vitrine_in_de_gang

in some automations i can use light.Vitrine_in_de_gang but in templates i really need it without the upper case.
if i use appdaemon it will tell me that light.Vitrine_in_de_gang doesnt exist in hass.

so i prefer to stay away from upper cases completely

[GraysonPeddie]

Well that makes sense. I will make sure to keep it consistent.

Thanks.

[rpitera (Robert Pitera)]

Thanks man - I’ll try this out sometime later in the evening and report back.

I appreciate it and you’re probably right about some stub of bad code stuck in there.