I didn’t notice they were disabled at first until I created a template sensor to pick up the humidity, and HA renamed it sensor.humidity_2.
That is a new feature, so that would be 0.113
ok thanks. looking forward to that 
Seems like I have same problem:
2020-07-03 13:37:21 ERROR (MainThread) [homeassistant.components.script] Restart - Homekit starten: Error executing script. Unexpected error for call_service at pos 4: unhashable type: ‘list’
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 153, in _async_step
self, f"async{cv.determine_script_action(self._action)}_step"
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 656, in _async_call_service_step
*self._prep_call_service_step(), blocking=True, context=self._context
File “/usr/src/homeassistant/homeassistant/core.py”, line 1260, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1295, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/components/homekit/init.py”, line 336, in async_handle_homekit_service_start
await homekit.async_start()
File “/usr/src/homeassistant/homeassistant/components/homekit/init.py”, line 474, in async_start
(SENSOR_DOMAIN, DEVICE_CLASS_BATTERY),
File “/usr/src/homeassistant/homeassistant/helpers/entity_registry.py”, line 141, in async_get_device_class_lookup
if domain_device_class not in domain_device_classes:
TypeError: unhashable type: ‘list’
My update from 0.112.0 to 0.112.1 failed the first time I tried it. It restored back to 0.122.0 on it’s own and came back up after a reboot. Any one else having issues?
It generally helps if you share things like logs.
Sorry. I’m new at this. Let me dig.
Maybe there is a typo:
condition:
- platform: state
entity_id: light.kitchen
state: 'on'
- platform: state
entity_id: light.living_room
state: 'on'
- platform: state
entity_id: light.office
state: 'on'
Can now be shortened to this:
condition:
- platform: state
entity_id:
- light.kitchen
- light.living_room
- light.office
state: 'on'
An example that tests if the alarm is in any of the specified states:
condition:
- platform: state
entity_id: alarm_control_panel.home
state:
- armed_home
- armed_away
And this condition is now also passing when Frenck is at home or at work (fake, of course, since Frenck works from his home).
condition:
- platform: zone
entity_id: device_tracker.frenck
zone:
- zone.home
- zone.work
Or combine! The following condition would pass if both Frenck and Daphne are either at home or in the work zone.
condition:
platform: zone
entity_id:
- device_tracker.frenck
- device_tracker.daphne
zone:
- zone.home
- zone.work
all “platform” are the correct or must the be “condition”?
Maybe a idea to update it if wrong…
HA 0112.2 will added new info:
reboot denonavr device, then add using new integration.
it work.
Since last update i can no longer use the ‘configure UI’ option from the top right menu in Lovelace. It has always required multiple taps for it to work but now it doesn’t do anything at all for me.
This is on the IOS-app plus both Chrome and Safari on Ipad.
edit upgrading custom header to beta 1.6.6 fixed it.
Strange, mine worked instant , no reboot required
After the update my Xiaomi Air Purifier 3H stopped working too 
[homeassistant.components.xiaomi_miio.fan] Got exception while fetching the state: {'code': -5001, 'message': 'command error'}
I ended up just remaking the HomeKit Bridges I had. It took time setting up the Apple side of things again but everything works as it should.
My guess is it had something to do with the database change. ( but I’m no dev so take that with a grain of salt )
I can confirm that there is a cost associated to access to the Smappee Cloud API. I have a document from smappee explaining the MQTT approach with instructions and can assist in updating the site docs to reflect the MQTT approach. I’m currently waiting to hear back on the cost of the cloud api and verification that the MQTT approach will work on older smappee devices like the smappee solar, or whether it will work on their new Infinity.
Hi,
I am unable to update to the latest version i am getting the below error when trying to update. I am currently running HassIO version 0.112.1.
20-07-03 12:50:34 ERROR (SyncWorker_2) [supervisor.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.112.1 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.112.1: No such image: homeassistant/raspberrypi3-homeassistant:0.112.1”).
20-07-03 12:50:34 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
You most likely don’t have enough disk space for the update.
must admit I really miss the logs on developer-tools… which Logs are, developer tools.
Thanks, I tried that but still can’t seem to start the Homekit service. Do you have filers specified in your config yaml? or just the integration via UI? thanks for the feedback
I don’t use the config.yaml for HomeKit.
After realizing it wasn’t working I;
I also use this automation to start my HomeKit Bridge(s) instead of manually doing it. ( pic below - then the ‘action’ is obviously ‘homekit.start’
