0.62: MyChevy, Iota and Venstar Thermostat

Second release of the year and it’s buzzing on GitHub. This release we had 70 people contribute code. We’ve also managed to finally get our PR count below a 100 open PRs again. A lot of cool stuff still waiting to make it to a future Home Assistant release.

I want to give a shout out to @martinhjelmare and @frenck. Martin is doing an amazing job at code reviews and Franck has been kicking ass with Hass.io add-ons and keeping track of our documentation PRs. Thanks for this amazing work!


With this new integration by @sdague you are able to keep an eye on your Chevy Bolt EV. Keep track if your car is plugged in, the battery stats and the range it is currently capable of driving. Hip!

New Platforms

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Breaking Changes

  • Tahoma platform will get new entity IDs (@glpatcern - #11547) (tahoma docs) (cover.tahoma docs) (breaking change)
  • Mold indicator: attribute names no longer include spaces or periods (@olskar - #11694) (sensor.mold_indicator docs) (breaking change)
  • Custom component devs only: EntityComponent.add_entity(entity) and EntityComponent.async_add_entity(entity) have been removed. Use EntityComponent.add_entities([entity]) and EntityComponent.async_add_entities([entity]) instead. Also EntityComponent.entities is no longer a dictionary but instead an iterable. Use EntityComponent.get_entity(entity_id) to get entity by id. (@balloob - #11691) (breaking change)

All changes

This is a companion discussion topic for the original entry at https://home-assistant.io/blog/2018/01/27/release-62/

Starting with the release blog post of 0.62 we’re using our forums for comments instead of Disqus.


Nice to see the comment section of the blogs moving into the Community Forum! :tada:


Is there also a changelog for the frontend fixes and improvements (polymer repository) ?

Two things in my setup that changed:
In configuration.yaml

  name: Home

This doesn’t work anymore, the default tab was renamed to default_view. I fixed that by adding name: under the default_view: in groups.yaml.

    name: 'Home'

Another issue i haven’t looked much into yet, is issues with my device tracker:

Error setting up platform asuswrt
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/device_tracker/__init__.py", line 162, in async_setup_platform
    platform.get_scanner, hass, {DOMAIN: p_config})
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/device_tracker/asuswrt.py", line 81, in get_scanner
    scanner = AsusWrtDeviceScanner(config[DOMAIN])
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/device_tracker/asuswrt.py", line 130, in __init__
    data = self.get_asuswrt_data()
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/device_tracker/asuswrt.py", line 169, in get_asuswrt_data
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/device_tracker/asuswrt.py", line 217, in _get_neigh
    old_ip = cur_devices.get(mac, {}).ip or None
AttributeError: 'dict' object has no attribute 'ip'

I echo appreciation for @martinhjelmare and @frenck: you both are tireless in your efforts. Thank you for all you do!


Thank you @bachya, really appriciated.


So since the “MyChevy” component requires a full Chrome install, that means it won’t work on a raspberryPi?

I’ve got some rfxtrx switches that were working fine and have now broken with this release, although I skipped 0.61, so the last release I can confirm working was 0.60.

I now get errors in the startup:

2018-01-27 16:35:28 ERROR (Thread-17) [homeassistant.components.rfxtrx] Invalid device: 7100a0041010000
2018-01-27 16:35:28 ERROR (Thread-17) [homeassistant.components.rfxtrx] Invalid device: 7100a0041020000
2018-01-27 16:35:28 ERROR (Thread-17) [homeassistant.components.rfxtrx] Invalid device: 7100a0041030000

Other rfx devices are still working.

1 Like

When I use “Reload groups” the follow default groups disappears:

Does anyone else experience this?

1 Like

OK, I can confirm it was actually 0.61 that broke this - I’ve regressed to 0.60 and it’s working.

Right, I’ve found the issue. My device IDs weren’t valid hex numbers (note they’re 15 characters long, an odd number). Adding a leading zero to the device IDs in my configuration fixed it.

Looks like 0.60 was accepting those and 0.62 is a bit fussier.

I did not receive the update.
he always tells me that I have version 0.61.1 and it’s the last one, how do I solve it?

I have a S.O. HASS.IO

Hass.io updates normally follow a day or two later.

This sounds like something I can make use of but how? The documentation doesn’t say anything about this.

I didn’t see anything in the change logs, but something has broken AsusWRT device tracking. Reverting to 0.61.1 corrects the issue.

FYI, there’s a breaking change for the Xiaomi Mijia Bedside Lamp.


has been renamed to:


thanks for info