0.99: Withings, Device Automations, launch Home Assistant Cast from Python

Love the new update. Only suggestion is when you have a dark theme and you go to “unused entities” you can’t see the devices depending on theme’s colors. It should change with the theme to match colors of text and background. Just a thought.

Hi.

My August Lock 3rd Generation stopped working after updating to 0.99.3

Thanks,
José Henrique.

You need to edit the theme to add the variables for the unused entities page. Something like this:

      card-background-color: 'var(--paper-card-background-color)'
      state-icon-color: 'var(--paper-item-icon-color)'
      state-icon-active-color: 'var(--paper-item-icon-active-color)'

Or use the default theme.

Nice my ES5 frontend is working again in 0.99.3, I’m now able to login to Tileboard using my old iPad. Thanks go out to the devs for fixing ES5 :slight_smile:

Ah thanks David will do!

I have opened a feature request to add an option to disable haptic feedback.
Please vote on it to bump visibility.

@gazelle @pergola.fabio @Khrumb @MandM78 @webserve

2 Likes

thnx for this PR and info

Done. And thanks.

Thanks for this. Done

That did not fix my problem. =(

pi_hole:
  host: pi.hole
  verify_ssl: false

so does pi.hole resolve on your system?

My pi-hole works but I get these errors. I am using the pihole addon through the add-on store.
2019-09-27_21h54_16

I have a command to get the pihole status and that works.

- platform: command_line
    name: PiHole Status
    command: curl -X GET 'http://XXX.XX.XX.XX:4865/admin/api.php?status'
    value_template: >
      {{ value_json.status }}

I’ve tried

pi_hole:

pi_hole:
  host: pi.hole
pi_hole:
  host: XXX.XX.XX.X:4685
pi_hole:
  host: 'localhost:4685'
pi_hole:
  host: pi.hole
  verify_ssl: false

the entities for it remain unavailable but show up
2019-09-28_00h03_27

Hello everyone,
After the latest update to 0.99.3 version, out of the blue I started to receive the following error:

Any ideas how I can fix it?

That is not what I asked you. I asked whether pi.hole resolves, ie resolves to an ip address.

Sorry didn’t quite understand but since the command works

http://XXX.XX.XX.XX:4865/admin/api.php?status

I can type it into a browser and get info
2019-09-28_00h42_39

does that answer what you’re asking?

No I mean does the address pi.hole resolve to an ip address? What is the response to the following in a terminal on your home assistant computer?

nslookup pi.hole
Execute shell command
Command executed: nslookup pi.hole: 1
Server:		127.0.0.11
Address:	127.0.0.11#53

** server can't find pi.hole: NXDOMAIN

There’s multiple possible issues here. The current refactored code doesn’t support multiple pi_hole instances - but this bug shows that the developer is working on it

There’s another one if you attempt to connect to a system that validates to a self signed certificate the verify_ssl: false does not work


Which I logged - I proposed a workaround in the code on that bug check.

I think there is another one where if you want to add a hass.io pihole instance the port number needs to be specified with the host e.g. host:pi.hole:4685

I also believe there’s an issue where it does not collect the data at startup - the first time it worked for me was 5 minutes after startup.

Set SSL to false in the Pi Hole config, not your configuration.yaml file.

{
  "update_lists_on_start": true,
  "ssl": false,
  "certfile": "",
  "keyfile": "",
  "interface": "",
  "ipv6": true,
  "ipv4_address": "",
  "ipv6_address": "",
  "virtual_host": "myddns.service.net",
  "hosts": [],
  "password": "PASSWORD",
  "admin_port": 4865,
  "dns_port": 53
}
1 Like

After update I get alot connection timed out with my Logitech Harmony.

2019-09-27 19:26:55 ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.XX: Connection timed out for hub XXXXXX1
2019-09-27 19:31:45 ERROR (MainThread) [aioharmony.hubconnector] XXX.XXX.X.XXX: Connection timed out for hub XXXXXX2

image