You should try to find which device has that serial number, the daylight sensor isn’t a clip sensor (now a days it’s disabled by default though)
yeah, but where to look? the mac is only in this device_registry file. I take it,
with serial number you mean the Mac-address in
"connections": [
[
"mac",
"02:42:ac:1e:21:06"
]
? Of course I have tried to find any mentioning of this anywhere in my network/system, but there’s no clue whatsoever… I wonder if “mac” in fact is referencing the Mac_address? the Daylight sensor has “zigbee”, while the deconz itself has no connection (to itself? so that would seem logical…)
If mac is indeed the Mac_address, and it doesnt come from a Zigbee device, whence could it come from (trying to narrow down the search here)? Could it be a networked device? Its not mentioned in the routers database.
If nothing seems to help solve this mystery, can’t I unplug/plug the Conbee II maybe, to have it recreate its database somehow?
With only 1 sensor, I am really starting to dread the user friendliness/maturity of this little piece of hardware. I do like some heavy tinkering, but this goes beyond that. Talking about the User Acceptance Factor, it would be real low on the scale…
It could be the machine that hosts deconz Mac aswell
Ok thanks, yes, that would seem logical somehow. Otoh, I only know of a Lan Mac address of that Pi and that isnt the same. Could it be its usb address maybe? (believed USB not to have a Mac address only lan and wifi) and if so, how to identify that, because in Supervisor/Hardware, all I can see is:
one more thought: I did try to register a Hue bulb on the deconz, but it failed (as in never showed up any success after the 3 minutes wait)
Could it somehow be the remnants of an unregistered bulb I am seeing here?
Its probably the host machine you’re seeing so it’s normal. I don’t think deconz sends anything unless a device is paired properly.
Got my Conbee II yesterday and it’s been a hell of a ride. I like technical challenges but this is a bit much.
Anyway, I have Deconz installed on VM (Virtualbox) Ubuntu, and I finally got it to work reliably. However, I’m having trouble pairing it with HA (core). First off, HA doesn’t automatically discover it (I have discovery: in my config file). So I next went and mapped port 8080 on the guest machine to port 8080 on my host machine. I can now access the Phoscon app at http://127.0.0.1:8080. If I choose “manually specify gateway” in the integration steup page, and enter this information, I can successfully pair HA with Deconz, and I see the devices. However, they are all unavailable to HA. I tried rebooting both HA, Deconz, and the VM, as well as trying to call device_refresh, and re-pairing the devices after the integration. This is what I see in the logs:
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.lock] Setting up lock.deconz
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.fan] Setting up fan.deconz
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.setup] Setup of domain light took 0.0 seconds
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.climate] Setting up climate.deconz
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.deconz entity: sensor.daylight
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.sensor] Not adding entity Daylight because it’s disabled
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.deconz entity: sensor.dimmer_switch_battery_level
2021-01-13 01:53:40 ERROR (MainThread) [pydeconz.websocket] Client connection error
2021-01-13 01:53:40 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2021-01-13 01:53:40 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.cover] Setting up cover.deconz
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.components.light] Setting up light.deconz
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new light.deconz entity: light.phillips_hue_light_2
2021-01-13 01:53:40 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new light.deconz entity: light.bedroom
2021-01-13 01:53:55 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2021-01-13 01:53:55 ERROR (MainThread) [pydeconz.websocket] Client connection error
2021-01-13 01:53:55 DEBUG (MainThread) [pydeconz.websocket] Websocket starting
2021-01-13 01:53:55 DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
Any ideas? Obviously the websocket is failing, but I don’t really have an indication why…
Have you exposed the websocket?
@Robban Thanks for trying to help. I’ve exposed :8080 and mapped it to the same port on the Host machine, but I’m not sure what you mean by “exposing the websocket”. I have Googled around this term in VirtualBox and couldn’t find anything relevant. Is exposing the websocket basically exposing a port? (I wouldn’t think so)
Does anyone know how to VNC into the marthoc/deconz docker?
I can establish a VNC connection, and I know the password should be “changeme”, since I did not change it.
But what is the username to use? I’d like to be able to configure the mesh/deconz app. Everything else works.
Thanks
Http port is not the same as the websocket port
Thank you very much for the useful link. Any idea how can I find my API key? I’m in the VM and going to api/config without it gives minimal information. Maybe I need to generate one first?
You can find the api key used by hass deconz integration in .storage/core.config_entries.
You can also enable debug for hass deconz integration to see the endpoint print out
1 Like
@Robban @sjee - you guys are super-awesome for helping out like this, also learned a lot of Deconz in the process.
Now onto the next mission - how do I control it better? Deconz applies some kind of “delayed” on/off for lights. Meaning the command is sent, but the light is slower to turn on/off - is that adressable?
There is no username needed as far as I know.
Ok thanks.
Still no luck. 
try pi
I have tried it 
VNC is active by default, yes? I don’t need to set any options? I mean, it connects and asks for credentials.
You need to set DECONZ_VNC_MODE=1
Ohh, it was not clear on github. I thought it was enabled by default.
Will try that. Thanks.