did that fix it?
Sorry, wasnt clear. Yes, a rollback fixed it.
Change log for 4.1 states this :
- Change internal API port back to 40850, to prevent issue with discovery
Have you look whether your network config tie in with that port change ?
EDIT: I precise I haven’t updated it yet
I’m using Hassio 0.103.2 after upgrading deconz to 4.1 the option to map ports for the API and WebSocket is removed, I’m interfacing deconz from node red via the server IP & Port.
Anyone using node-red-contrib-deconz and have idea how to properly set it?
I also liked the option that I can access deconz outside of home assistant.
The option to map ports 80 & 8080 is removed at 4.1
I don’t seem to have many options to change this: Am I missing something:
1 Like
Arf… Not sure removing port setting flexibility within this update was the best move to do…
Thoses parts could better be showing or not depending if Advande mode is set in User Profile or something like that(advanced mode param in config ?)
1 Like
Is the issue with authentication? Every restart of hassio throws the error below and I have to reset the password in phoscon
2019-12-20 09:56:56 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from
1 Like
I still have these settings with 4.1
Is it possible to remember login? I think I didn’t have to log in every time I accessed Deconz through port.
It seems like its restarting (powercycling) the device and resetting the password to default each time.
Ok, in my local net I can at least access the Phoscon webpage. But I can’t login.
Oef… I was just going to update due to ingress… Think i will wait for a while…
1 Like
Sorry, even if some of you have more serious problems a maybe simple question beside:
I already installed an additional motion sensor from hue.
As fas as I remember, all of them are preconfigured with sensitivity 2 or 3.
I would like to increase.
So I tried it with the deconz service.
Unfortunately you only get response in case of errors.
So can anybody confirm,that my service call pointed the right field?
or does anybody has an idea how to find out the active value?
1 Like
looks good to me
1 Like
Upgrade to 4.1 went okay, everything works okay, but my Settings/Gateway page is just blank. It’s not that important to me other than for firmware upgrades but… it’s a bit unnerving.
Is there any deconz dev keeping an eye/monitoring this thread? Has anyone create an issue ticket already?
I was going to update, but glad I actively follow this topic and now know its best to wait a bit 
1 Like
after i did a update
was not seeing the USB stick
HAD TO
reboot and plug it then plug into differance USB port and prayed
everything start work again 
it was not seeing it plug in
Well, I ended up having to rebuild my entire deconz entity list after updating to 4.1, and I’m having trouble consistently getting deconz to pick up Hue motion sensors. I’ve tried about 20 times and have 2 of 5 recognized.
I also added a Xioami motion sensor, and ended up removing it because Home Assistant stopped responding to the sensors. Trying to add it back again and it won’t pick it up.
Any suggestions? I’ve removed all the old entities and device entries for the Xioami sensor and rebooted both HA and deconz multiple times, but it still won’t add back.
@frenck released a fix for deCONZ in 0.103.3
Have you guys tried that in combination with deconz 4.1?