for now use mdi: run-fast and mdi:human-male/female … (might have to take out the line in the CC for the icon) is this possible @robmarkcole ? or maybe add the possibility for the on/off in the CC itself?
This is what I added to my customize.yaml - I borrowed another line for stateDisplay from the discussion here but it doesn’t appear to matter if I exclude that line or not
That’s very odd but anything i try here doesn’t work, it appears as per my screenshot above. Templates don’t work in my customize.yaml even though other customizations do.
Is there possibly an error somewhere else in customize.yaml that could be causing this? An errant parentheses or something? I’m using hassio latest public release. Any custom components or anything that I need to install?
in any way seem possibly related to the hue.py CC? Ie checked in my config files for the value_json.state.presence and on, and the only place it seems related to is your CC…
do you recognize these errors in the log. Ive looked everywhere in my config, but can only imagine them to come from the rest switches…
File "/usr/lib/python3.6/site-packages/homeassistant/components/switch/rest.py", line 167, in async_update
yield from self.get_device_state(self.hass)
File "/usr/lib/python3.6/site-packages/homeassistant/components/switch/rest.py", line 178, in get_device_state
text = yield from req.text()
File "/usr/lib/python3.6/site-packages/async_timeout/__init__.py", line 35, in __exit__
self._do_exit(exc_type)
File "/usr/lib/python3.6/site-packages/async_timeout/__init__.py", line 80, in _do_exit
raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError
2018-04-11 23:57:18 ERROR (MainThread) [homeassistant.components.switch.rest] Error while fetch data.
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/components/switch/rest.py", line 178, in get_device_state
text = yield from req.text()
File "/usr/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 829, in text
await self.read()
File "/usr/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 798, in read
self._content = await self.content.read()
File "/usr/lib/python3.6/site-packages/aiohttp/streams.py", line 312, in read
block = await self.readany()
File "/usr/lib/python3.6/site-packages/aiohttp/streams.py", line 328, in readany
await self._wait('readany')
File "/usr/lib/python3.6/site-packages/aiohttp/streams.py", line 250, in _wait
await waiter
File "/usr/lib/python3.6/asyncio/futures.py", line 332, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 237, in result
raise CancelledError
concurrent.futures._base.CancelledError
Here’s how I’ve customised mine to show the ‘movement’ and ‘no movement’ states, in case anyone wants to try it. Looks pretty cute when it switches between states
BTW, what's the status of the motion sensors in Home Assistant at the moment? I've been holding off updating HA, as didn't they remove support for Hue sensors?
OK I’ve tested the CC on HA 0.68.0.dev0 and works fine. If the Hue hub component is stable over the next release I will look at turning the sensors into an official component.
Cheers
@robmarkcole
I was testing and comparing automation using the hue motion sensor (open light when motion) with HomeKit and HA (your component).
Is it normal that Home kit automation is WAY FASTER to open the light on motion than doing it from HA? (maybe because the way it communicate with the sensor or something)
HK is less than a second and with HA, it can be 2 seconds…
Just wondering is this is something to live with or something I can optimize…
For F. sake please! that would be so awesome - Especialy the motion sensors for triggering automations and the remotes.
I’m to worried to change the working setup, its not broke, jet…