Click on this symbol and let deconz search. After this I’m able to login again.
I got an issue and can’t solve it.
To get everything right I followed the “Gateway ID 000000000” problem instructions.
So I uninstalled the addon and the integration, installed it again and restored the webapp with my backup.
After several restarts between and after that I started the integration process, but my integration now shows no devices.
I restarted all again, tried the “My integration shows no devices after upgrading” but it didn’t help.
Can you help me start over again.
My log shows following Error:
2019-12-21 14:11:46 WARNING (MainThread) [homeassistant.components.deconz] Invalid key for deCONZ at core-deconz.local.hass.io
Just for the record, the webapp shows all devices and I can controll them, but the integration doesn’t work. My hass.io is on 0.103.3
Doesn’t find anyting new, unfortunately.
Integration continues to work fine (VNC too), but I will not be able to add new devices.
I am running with 0.103.3.
After updating the Deconz addon to 4.1 I have an issue.
The HA seems to work but I am unable to login into the web interface.
I have the error: 403 forbidden.
What can I do to solve the issue?
Do you have IP Bans enabled?
The addon documentation has been updated to include:
Home Assistant IP Ban is triggered by the add-on. This is caused by the Phoscon frontend trying out many different URLs and locations to find devices, triggering an IP ban in the process. We are looking into a solution for this, right now, raising the number of attempts or disabling IP bans in Home Assistant, is the only workaround.
1 Like
Ok, my problem is solved:
I was in the same local network (at home) as my home assistant server, but was accessing it via its global internet adress/domain, which is just a forward of port 8123. Once I tried to access the server via its internal private adress/name, everything worked…
Thanks to everyone who tried to help!
I’ve been using REST commands to call bri_inc (linear dimming), which does not work after the update.
Example:
deconz_dim_group_down:
url: http://192.168.100.156:40850/api/123456abc/groups/{{groupid}}/action
method: PUT
headers:
Content-Type: 'application/json'
payload: '{ "bri_inc": -254, "transitiontime": 50 }'
Is there any way I can do the same through Home Assistant directly?
The HA seems to work but I am unable to login into the web interface.
I have the error: 403 forbidden.
Do you have IP Bans enabled?
Thanks. It solved my issue.
1 Like
Yes. Use the service deconz configure
1 Like
Awesome, thanks!
Been on this most of the afternoon after upgrading Deconz. I’ve uninstalled and installed it at least 4-5 times, restating my nuc and proxmox between tasks.
The first problem, I was unable to get into the Gateway view in the deconz webUI after trying so many times, That turned out to be Safari, Chrome worked with out a problem.
I still couldn’t get the data into the deconz Integration once I had restored my backup in deconz. All was showing in the deconz webUI but not populating the hassio Integration.
The only option I had left was to delete the deconz Integration in hassio, open up the deconz web Gateway, select Advance and select ‘Authenticate app’, then I opened Configuration > Integrations in another browser and clicked on the + to add the docenz integration. This then worked for me and all is well now.
2 Likes
Texted too soon, Just restarted hassio and have lost the integration with deconz.
If I go to the deconz webUI, I can control the lights.
But if I go to Configuration > Integrations I can see the deconz listed but no entities, If I open up the integration, all the entities are listed but not controlable.
Any help would be welcome.
I seem to having the same issue.
If I delete the integration, restart, then re-add it (telling the gateway to allow authentication), then everything works.
As soon as I restart HA again, all the devices connected to the integration go unavailable.
At the moment my “solution” is to go through the re-adding process anytime HA needs to be restarted until a proper fix is released, and limit HA restarts where possible.
I don’t know if this is related to the issue of the addon now generating large amounts of invalid login attempts.
1 Like
Anyone knows where we should raise this issue/bug? Should we report this with deCONZ owner or is this a Home Assistant issue 
Hi Everyone,
Im trying to get my hass.io to recognize the conbee but without any success.
It seems that the vm does not see the usb/serial device.
I have Hass.io running on a virtualbox linux machine.
in the serial port, i have entered COM3, “Host Device” and in the port/address field, i have written “COM3:”.
Any tips?
crap, just updated to 103.1 and 4.1 , also have now errors below, what do we need todo for the fix?
2019-12-22 18:20:41 WARNING (MainThread) [homeassistant.components.deconz] Invalid key for deCONZ at core-deconz.local.hass.io
2019-12-22 18:20:41 ERROR (MainThread) [homeassistant.components.deconz] Error connecting with deCONZ gateway
2019-12-22 18:23:10 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 127.0.0.1
About the “Missing entities in Deconz after updating to 4.1”.
After several hours of trying, the only thing working here is
- delete the deCONZ integration
- reboot HA
- add a new integration MANUALLY ! Any auto attempt here had the same result : an empty new deCONZ integration. But when adding it with the PLUS BUTTON, things went finally ok.
So, juste before adding, you need to grant access to the add-on in PHOSCON > Gateway > Authenticate App (you got one minute).
Waiting of course for some more official solution, but if it may help for now…
Michel
2 Likes
Interesting what you just brought up. With all the other issues of upgrading to 4.1, I never lost any entities.
But thinking back, I never did an auto-discovery. I added/configured each entity individually and manually.
1 Like
For people that my have problems with accessing the api for deCONZ because of ingress feature .
I make an work around using core-ssh , but you need to adapt.
I know people will say this is not supported.
However i have found a way to do this.
Install core-ssh
Edit sshd_config file to allow port forwarding.
core-ssh:~# cat /etc/ssh/sshd_config | grep Tcp
AllowTcpForwarding yes
core-ssh:~# ps -ef
PID USER TIME COMMAND
1 root 0:29 /dev/init – /run.sh
6 root 0:00 /usr/sbin/sshd -D -e
72 root 0:01 sshd: root@pts/0
74 root 0:00 -bash
173 root 0:00 sshd: root@pts/1
175 root 0:00 -bash
225 root 0:00 /bin/bash
240 root 0:00 ps -ef
core-ssh:~#kill -HUP 6
This way you enable SSH port forwarding.
Python sshtunnle.
https://sshtunnel.readthedocs.io/en/latest/
if you need you can use ssh tunneling form your linux box.
My example to access the api.
#!/usr/src/Python-3.7.3/python
from sshtunnel import SSHTunnelForwarder
from pprint import pprint as pp
from requests import get
import json, re, os, time
from influxdb import InfluxDBClient
conf = {
‘url’: ‘http://127.0.0.1:40850/api/’,
‘auth’ : ‘988112a4e198cc1211’,
‘ifx’ : {‘host’: ‘192.168.100.244’, ‘port’: 8086, ‘usr_’: ‘admin’, ‘pass_’: ‘PaSsWoRd’, ‘DB_’: ‘deconz_data’}
}
client = InfluxDBClient(host=conf[‘ifx’][‘host’], port=conf[‘ifx’][‘port’], username=conf[‘ifx’][‘usr_’], password=conf[‘ifx’][‘pass_’])
client.switch_database(conf[‘ifx’][‘DB_’])
api_ = ‘lights’
def url_ (api):
url = conf[‘url’]+conf[‘auth’]+’/’+api
headers = {‘content-type’: ‘application/json’}
response = get(url, headers=headers)
return response
with SSHTunnelForwarder(
(‘192.168.100.244’, 22),
ssh_username=“root”,
ssh_password=“StrongPassword:P”,
remote_bind_address=(‘core-deconz’, 40850),
local_bind_address=(‘0.0.0.0’, 40850)) as tunnel:
pp (url_(api_).text)
data = json.loads(url_(api_).text)