Keep up the good work, always love the pace at which things get released (and so open too)
Keep up the GREAT WORK!!! I love Home Assistant and where it is headed. Going to try user authentication next. One question, I don’t think the docs accurately represent what happened to the Pollen.com sensor. Mine all stayed the same they were just appended with a _2.
Is this correct?
Thanks
We wouldn’t have this statement below if there aren’t any “security concerns/I’ve been hacked” threads, right?
The new additions to component lists seem very quiet for 0.73. No new additions that get me excited. Well, just Rachio and HomeKit and that’s about it… I will wait for 0.74 as I only have two Insteon dimmers and a receiver hooked up.
Holy mother of home automations… 
That Lovelace UI is going 
Thank you guys for the hard work on this!
The correct assumption is I did read the real blog post and clicked “Continue Discussion.” All the changes are a lot more detailed compared to see if there are any new components for 0.73. I read the changes again and there’s not that much that is exciting.
Lovelace does seem interesting, but my home automation setup is barely minimal unless I have money for more products that I can make use of, such as Konnected.
Seems like Rachio still isn’t working?
rachio:
api_key: 6axxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Getting an invalid config.
Same here. I double checked my config.
@dcnoren rachio is working for me, you need to configure the switch and binary_sensor to complete it.
Enabled username/password authentication and getting prompted for a username and passoword which works, but password is not masked as ***. Is it supposed to be so?
posting this only to show that even a total novice can begin to figure this out. I use a tablet in kiosk so I have to keep the panels uncluttered. this is just the first layout. will learn to customize more.
1 Like
I didn’t change anything, just restarted and it works…just now all my zones have an entity id with a 2 added to them…for example switch.back_yard is now switch.back_yard_2.
yea the old integration added the switches to the entity_registry.yaml for now you can remove those entries from that file and restart home assistant to remove the _2
1 Like
All fixed…thanks
Another change not mentioned in the release notes above that may catch people by surprise (it did me) is that the behavior of the lock toggle in the UI has changed. As of 0.73 the behavior is now reversed:
- the toggle is off when the door is locked
- the toggle is on when the door is unlocked
previously it worked the other way round
For more information on this change and potential future changes around the lock UI see 73.0 -- lock status is inverted and the corresponding issue in Github https://github.com/home-assistant/home-assistant/issues/15276
2 Likes
Rachio is failing for me on all 3 components: hub, binary_sensor, and switch. There isn’t a lot to get wrong on syntax here. It was working before the update.
We just released 0.73.1 which removes the toggle. No more confusion!
4 Likes
Also still having problems with pollen.com in this release:
2018-07-08 13:00:53 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.pollen
2018-07-08 13:00:53 ERROR (MainThread) [homeassistant.components.sensor] pollen: Error on device update!
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 248, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 317, in async_device_update
yield from self.async_update()
File "/usr/lib/python3.6/site-packages/homeassistant/components/sensor/pollen.py", line 186, in async_update
data = self.pollencom.data[self._category]['Location']
KeyError: 'allergy_index'
My config for this component is unchanged from 0.72.1, and still matches a “correct” config according to the documentation for the component. Oddly: one of the conditions I’m monitoring is “disease_average_forecasted”, and though that no longer shows up as an entity for me, I do now see “sensor.cold__flu_forecasted_average_2”, which would appear to be the same data under a different name; a name that is not listed in the documentation as a valid entity.
Please post a bug and we’ll take a look.