Indeed, I liked Yaml 
Maybe it’s possible by changing it in the storage files manually
Seems to be working 
no issues so far!
1 Like
Doesn’t work for me after the update 
EDIT: fixed (!) indeed; The IP adress changed; I manually forced my UNIFY to go back to the old IP adress.
1 Like
In unify you can create a dhcp reservation - doing that for the dobiss next server will make sure it gets the same address every time
1 Like
Hi,
Can someone tell me if the latest Home Assistant version still works with Dobiss?
I see that the project is not maintained anymore. (Don’t have Dobiss atm, but maybe in the near future…)
its still maintained , but no updates on API side probably, so no update needed
Thank you for the quick response!
And does it works good? Can I just control lights from Dobiss with Home Assistant without a lot of latency/lag/problems sometimes?
I dont use the NXT, i still have old evolution SX system, but i follow the thread here, and its still active! works quite good if i hear from other users!
1 Like
Hi, yea the NXT integration is working very good! It’s instant, so no latency 
And it’s certainly still maintained 
As mentioned, there were no api changes the last NXT updates. The dev is very responsive 
1 Like
I am definitely still supporting this. Let us know how things work for you if you try it out - should be easy to set up!
2 Likes
Thank you! 
Ik gebruik deze integratie nu al een tijdje en wou even langs deze weg mijn appreciatie tonen voor het werk dat hier ingestoken is.
Echt een meerwaarde voor mijn home assistant en heeft altijd, en werkt nog steeds vlekkenloos!
2 Likes
Hi @kester,
Hope you’re doing fine 
It seems the recent dobiss nxt 3.80 upgrade breaks the HA integration. I’m running the latest HA version.
Here you can find the log:
Logger: dobissapi.dobissapi
Bron: /usr/local/lib/python3.12/site-packages/dobissapi/dobissapi.py:890
Eerst voorgekomen: 14:29:03 (118 gebeurtenissen)
Laatst gelogd: 14:48:37
Failed to connect, waiting a bit before retrying: ClientResponseError(RequestInfo(url=URL('ws://x.x.x.x/sockets/api'), method='GET', headers=<CIMultiDictProxy('Host': 'x.x.x.x', 'Authorization': 'Bearer x.x', 'Upgrade': 'websocket', 'Connection': 'Upgrade', 'Sec-WebSocket-Version': '13', 'Sec-WebSocket-Key': 'xxxx==', 'Accept': '*/*', 'Accept-Encoding': 'gzip, deflate, br', 'User-Agent': 'Python/3.12 aiohttp/3.10.8')>, real_url=URL('ws://x.x.x.x/sockets/api')), (), status=426, message='No Sec-WebSocket-Protocols requested supported', headers=<CIMultiDictProxy('Server': 'nginx/1.18.0', 'Date': 'Wed, 16 Oct 2024 12:47:57 GMT', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Upgrade': 'websocket', 'Sec-WebSocket-Version': '13', 'Sec-WebSocket-Protocol': 'wamp', 'X-Powered-By': 'Ratchet/0.4.4')>)
Failed to connect, waiting a bit before retrying:
....
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/dobissapi/dobissapi.py", line 858, in listen_for_dobiss
ws = await self._session.ws_connect(self._ws_url, headers=headers)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 933, in _ws_connect
resp = await self.request(
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 789, in _request
resp.raise_for_status()
File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1121, in raise_for_status
raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 426, message='No Sec-WebSocket-Protocols requested supported', url='ws://x.x.x.x/sockets/api'
I uploaded a new dev version - see Dobiss NXT v3.80 - toggles · Issue #202 · kesteraernoudt/dobiss · GitHub as well.
If it’s verified to work I’ll package it up and create a new release!
I created release v1.9 which hopefully fixes this incompatibility for all!
1 Like