deCONZ and HASS all live on the Pi.
So when I restart - full reboot - deCONZ, it also reboots HASS as well.
A deconz.conf file will be created in your .homeassistant folder unless you’ve specified your deconz api key in your configuration.yaml file.
Sure, but if you add a device to deconz it is enough to restart hass to get the new devices loaded by hass
Done that more then a few times. Nothing. Trying to locate the config file now. I didn’t change the install directions. I followed what @marthocoo provided above.
That being the case, where is this config file? I want to help and perform the troubleshooting to assist in resolving the problem.
deconz.conf will be located in your config directory, the same directory where configuration.yaml is located. Is the problem that you haven’t set up the deconz component in HA yet?
Yea - I may be confused. I added the following to configuration.yaml.
# Zigbee
light:
platform: hue
host: 10.1.30.191
# deCONZ
deconz:
host: 10.1.30.191
port: 80
It found the Hue Configurator, I configured it and that was it.
OK… problem found.
Remove this entirely:
light:
platform: hue
host: 10.1.30.191
Change your deconz section to this only:
deconz:
host: 10.1.30.191
(I’m assuming that 10.1.30.191 is the IP of deconz; if they’re on the same Pi, you could also use 127.0.0.1 i.e. the loopback adapter).
Now restart HA. When it comes back up, there will be a configurator for deCONZ in the frontend. It will instruct you to unlock your gateway. You do that by going to 10.1.30.191:80 (the Wireless Light web app), Menu, Settings, and there is a button that says “Unlock Gateway”.
The problem is that deCONZ was never connected to your HA, so of course it wasn’t pulling in the various devices.
Done
Done. Updated with 127.0.0.1 because yes, they are on the same box/Pi.
No that did happen, because like I said, I can see some devices in HA. See image.
Let me give the reboot a shot with the new configuration.
Yes, it connected through the Hue component (deCONZ fakes being a Hue bridge), but not through the deconz component. The deconz component is where you get the sensors, switches, and instant status update support via websockets.
I stand corrected!
Ok - Now it’s looking much better
It’s already integrating much better than the Hue hub. I was unable to pull much of this information as easily.
The only strange thing I notice is that it may be duplicating devices
What it shows in entities is the following:
light.garage_entrance_light
light.hue_dimmer_garage
light.garage_entrance_light_2
light.hue_dimmer_garage
sensor.motion_sensor
sensor.motion_sensor2
Ok - so I decided to reboot the Pi to try and clear the duplicates and now deCONZ won’t start. Here are the errors.
2018-01-26 12:27:07 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up platform deconz
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/asyncio/tasks.py", line 180, in _step
result = coro.send(None)
File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
File "/usr/lib/python3.6/site-packages/homeassistant/components/binary_sensor/deconz.py", line 29, in async_setup_platform
if sensor.type in DECONZ_BINARY_SENSOR:
AttributeError: 'NoneType' object has no attribute 'type'
@Robban here is the output from the command:
{"1":{"config":{"battery":100,"group":"8057","on":true,"reachable":true},"ep":2,"etag":"17b9b865a6467fb69058ca999b525e19","manufacturername":"Philips","mode":1,"modelid":"RWL020","name":"Hue Dimmer Garage","state":{"buttonevent":4002,"lastupdated":"2018-01-26T17:41:54"},"swversion":"5.45.1.17846","type":"ZHASwitch","uniqueid":"00:17:88:01:02:d6:4b:a3-02-fc00"},"2":{"config":{"alert":"none","battery":100,"ledindication":false,"on":true,"pending":[],"reachable":true,"tholddark":12000,"tholdoffset":7000,"usertest":false},"ep":2,"etag":"5a18ec52930c181f10dfa4837b8bc95e","manufacturername":"Philips","modelid":"SML001","name":"Motion Sensor","state":{"dark":false,"daylight":false,"lastupdated":"2018-01-26T18:13:24","lightlevel":16444,"lux":44},"swversion":"6.1.0.18912","type":"ZHALightLevel","uniqueid":"00:17:88:01:02:10:d0:f0-02-0400"},"3":{"config":{"alert":"none","battery":100,"duration":300,"ledindication":false,"on":true,"pending":[],"reachable":true,"sensitivity":0,"sensitivitymax":2,"usertest":false},"ep":2,"etag":"f3f9857ebe693f01421ea35d274704cf","manufacturername":"Philips","modelid":"SML001","name":"Motion Sensor","state":{"lastupdated":"2018-01-26T18:12:05","presence":false},"swversion":"6.1.0.18912","type":"ZHAPresence","uniqueid":"00:17:88:01:02:10:d0:f0-02-0406"},"4":{"config":{"alert":"none","battery":100,"ledindication":false,"on":true,"pending":[],"reachable":true,"usertest":false},"ep":2,"etag":"efaa0b5b220a55571588367f695afe2f","manufacturername":"Philips","modelid":"SML001","name":"Motion Sensor","state":{"lastupdated":"2018-01-26T18:16:08","temperature":2458},"swversion":"6.1.0.18912","type":"ZHATemperature","uniqueid":"00:17:88:01:02:10:d0:f0-02-0402"},"5":{"config":{"duration":60,"on":true,"reachable":true},"etag":"6c86fb4da6838281c92902ef7905428f","manufacturername":"Phoscon","modelid":"PHOSCON_VPIR","name":"VPIR Garage Motion Rules","state":{"lastupdated":"2018-01-26T18:02:56","presence":false},"swversion":"1.0","type":"CLIPPresence","uniqueid":"vpir-1516986821905"},"6":{"config":{"on":true,"reachable":true},"etag":"3a6ecb24e8bd5599ce4225a9bd5fe8ad","manufacturername":"Phoscon","modelid":"PHOSCON_FSM_STATE","name":"FSM_STATE Garage Motion Rules","state":{"lastupdated":"2018-01-26T17:41:54","status":-3},"swversion":"1.0","type":"CLIPGenericStatus","uniqueid":"fsm-state-1516986821905"}}
Here’s what I would do:
Disable the deconz component (comment out the deconz lines in configuration.yaml). Restart HA. See if the light and sensor entities have disappeared.
Re-enable deconz component. Restart the Pi, let everything get pulled in. I took a quick look at the JSON and it looks good, maybe things have just gotten confused as a result of the wrong config initially.
So I did the first step, but the light and dimmer entities remain.
light.garage_entrance_light
light.hue_dimmer_garage
Could this be something stuck somewhere when I added it initially using the Hue component?
Should I be concerned?
edit: after all steps, the motion sensors aren’t there. I’m going to remove them and re-add, even though deCONZ sees them with no problem.
I think initially trying to set up your RaspBee under the Hue component has done some things it shouldn’t have. For example, why is the Dimmer added as a light? That doesn’t make any sense.
Bummer - doesn’t seem like there is anything I can do to fix this. There is nothing else in the config to remove.
@Robban can maybe chime in… but entities should be removed when their component doesn’t load. Are you sure you removed all Hue entries from the config?
Yes. Entities are generated by their components. If the component doesn’t load. No entities will be created. Maybe you have the hue.conf file in your homeassistant folder?
Don’t know how, but I’ve managed to get them out. I’m not doing anything different. This is absolutely the funniest thing ever!
Ok - but, even then - same errors.
2018-01-26 17:26:57 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up platform deconz
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/asyncio/tasks.py", line 180, in _step
result = coro.send(None)
File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
File "/usr/lib/python3.6/site-packages/homeassistant/components/binary_sensor/deconz.py", line 29, in async_setup_platform
if sensor.type in DECONZ_BINARY_SENSOR:
AttributeError: 'NoneType' object has no attribute 'type'
This is your problem, CLIPPresence, some kind of virtual presence sensor in deconz. This is something Phoscon creates with many sensors. HA 0.62 will support this type of sensors as well. You can also remove them in phoscon, unless you know what they do and want to keep that functionality.