Renaming an entity using the new UI state dialog is - to my knowledge - only possible for entities that have been added to the entity registry. In my case, it’s the Hue light bulbs.
The entered new name is added as “name” attribute to an entry of the entity registry. The text can still be overriden by a friendly_name attribute in customize.yaml.
I modified the entuty_registry, for a hue bulb, name field, this changes only the friendly name
So thus is wrong?
Where is this new UI where you can change the entity_id?
Since upgrading from 0.64 to 0.65.3 my log is flooded with Telegram errors. I get this message 5 or 6 times a minute
2018-03-15 07:19:31 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] wrong status 409I’m using polling now and I don’t see that errors in my log. Now that you’ve mentioned it, I recall I did see such errors in earlier version. I guess that’s why I moved to webhooks.
I use ha 0.65.5 on hassbian and raspbian. just install telegram polling yesterday and it works so fine.
Mine is just try to use telegram bot from Mr. masterkenobi share
Sorry I lost track of this issue
This is my current config
google_assistant:
project_id: homeassistant
client_id: CLIENTID
access_token: TOKEN
agent_user_id: [email protected]
api_key: APIKEY
exposed_domains:
- switch
- light
- group
entity_config:
sensor.temperature_158d0001fa985e:
expose: true
name: Living Room
sensor.temperature_158d0001fa9917:
expose: true
name: Bedroom
Is this correct? When I type/do the following on Google Assistant via app “sync my devices” it replies “An error occured while syncing my test app”
Also when I say “What is my bedroom temperature”
It says “Sorry I am unable to reach bedroom right now”…
I can see the API connection making a call
2018-03-20 11:44:08 INFO (MainThread) [homeassistant.components.http.view] Serving /api/google_assistant to 66.249.82.137 (auth: False)
The IP being a google proxy…
So is the setup correct or I need to make changes since 0.65 ???
google assistant component is not support sensor domain but support climate domain. By putting some domain that not support by google assistant will cause account link failed or end up with see no devices in your google assistant app. Try putting only support domain for google assistant. each domain that you put in google assistant app. You also need to put in entity_config for that specific devices.
Currently, the following domains are available to be used with Google Assistant, listed with their default types:
group (on/off)
input boolean (on/off)
scene (on)
script (on)
switch (on/off)
fan (on/off)
light (on/off/brightness/rgb color/color temp)
cover (on/off/set position (via set brightness))
media_player (on/off/set volume (via set brightness))
climate (temperature setting)
I leave input_boolean away as well. As putting in input_boolean, google assistant can not discover input_boolean anyway.
Same here, running 0.65.5 now and still the same problem. Nothing in the logs suggesting it’s not working
edit released people may think I’m referring to the google assistant problem, I’m actually referring to the Yeelight problem mentioned by @brahmafear
I downgraded to 0.64.3 and it’s working fine again.
Thanks… What would I need to change in my above code to make it climate? Something like?
google_assistant:
project_id: homeassistant
client_id: CLIENTID
access_token: TOKEN
agent_user_id: [email protected]
api_key: APIKEY
exposed_domains:
- switch
- light
- group
- climate
entity_config:
climate.temperature_158d0001fa985e:
expose: true
name: Living Room
climate.temperature_158d0001fa9917:
expose: true
name: Bedroom
Must be something else as how will the sensors tie to climate?
This is what home assistant support under climate component
The Google Assistant component does not support temperature sensors. We’re still waiting for Google to add support for this. In the meanwhile, you can configure a generic thermostat to have Google Assistant read your temperature sensor.
What should be the heater: in this case? create fake switch or something?
climate:
- platform: generic_thermostat
name: Study
heater: switch.study_heater
target_sensor: sensor.study_temperature
Anyone having a complete example will be really helpful…
Have done the following but google assistant still doesn’t like it
google_assistant:
project_id: homeassistant
client_id: CLIENTID
access_token: TOKEN
agent_user_id: [email protected]
api_key: APIKEY
exposed_domains:
- switch
- light
- group
- climate
entity_config:
switch.living_room:
name: Living Room Temperature
switch.second_bedroom:
name: Bedroom Temperature
climate:
- platform: generic_thermostat
name: Living Room
heater: switch.living_room
target_sensor: sensor.temperature_158d0001fa985e
- platform: generic_thermostat
name: Bedroom
heater: switch.second_bedroom
target_sensor: sensor.temperature_158d0001fa9917
After update to 65.5, my Lifx bulbs are gone. I can’t see them in the dev states tab and there are no errors in my log concerning Lifx. Sort of stuck on where to look to for a fix.
Could be related to the Yellight problem a few of us are having?
For anyone wondering about the easiest way to this release of HA running on Ubuntu 16.04 LTS, this is the way I upgraded Python to make it work.
python3 --version # 16.04 LTS is Python 3.5.2
sudo add-apt-repository ppa:jonathonf/python-3.5
sudo apt-get update
sudo apt upgrade
python3 --version # Python 3.5.3+
Use at your own risk, compile it from source using one of various tutorials or wait until 18.04 LTS. 
Two things.
The first is just an observation. I haven’t tried it yet, but I don’t see how the new light group differs from just putting your lights in groups. I have groups configured for my lights and they seem to work exactly like the pictures/description of the new light groups work… I have always had entries in my groups.yaml that look like this:
bedroom_lights:
name: Bedroom lights
entities:
- light.bedroom0
- light.bedroom1
I can set the colour for all lights by changing the group, etc.
The second thing is that it seems that some information is no longer being passed to my influxdb db and therefore my grafana graphs are not working for everything I’l like to graph. Specifically, sensor.load_15m, sensor.load_1m, sensor.load_5m are not being written to influxdb any longer. My influxdb config is using all the defaults and therefore I only have influxdb: in my configuration.yaml.
Does anyone know why some things would stop writing to influxdb with hass 0.65?
Influx stopped working for me as well. I’m getting the following traceback when HA is setting it up:
2018-03-23 01:57:35 ERROR (MainThread) [homeassistant.setup] Error during setup of component influxdb
Traceback (most recent call last):
File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
component.setup, hass, processed_config)
File "/usr/lib64/python3.6/asyncio/futures.py", line 327, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib64/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/lib64/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/usr/lib64/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/components/influxdb.py", line 95, in setup
from influxdb import InfluxDBClient, exceptions
File "/opt/homeassistant/lib/python3.6/site-packages/influxdb/__init__.py", line 9, in <module>
from .client import InfluxDBClient
File "/opt/homeassistant/lib/python3.6/site-packages/influxdb/client.py", line 16, in <module>
from six.moves import xrange
ModuleNotFoundError: No module named 'six.moves'; 'six' is not a package
Reverting back to 0.64.3 worked for me 
Hi,
This may be unrelated to the 0.65 upgrade, but is anyone else having issues with the Dark Sky sensor? I noticed my sensor data was not updating when I was on 065.3 and now that I have upgraded to 065.6 my sensor icons have disappeared from my UI.
I’d appreciate any suggestions for troubleshooting this as I can see any issues in the logs.
My config is as follows:
sensor: