Can't connect to Lifedomus Tydom Box

[bgillet-tbscg]

Describe the bug

I am trying to connect Homebridge to a Tydom 2.0 Lifedomus box.
Connection just doesn't work no matter what hostname / login / pwd configuration I am using.
I am a Tydom 2.0 box - it's an Intel NUC - from 2018.

Related hardware

Expected behavior

Logs

Starting to advertise 'Homebridge BE8A E166' using bonjour-hap backend!
[2/22/2021, 1:30:47 PM] Homebridge v1.3.0 (Homebridge BE8A) is running on port 51648.
2021-02-22T12:30:47.120Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:48.297Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:48.299Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:50.526Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:50.527Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:54.735Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:30:54.735Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:02.937Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:02.938Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:19.041Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:19.042Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:51.127Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:31:51.127Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:32:55.334Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:32:55.335Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:35:03.450Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:35:03.450Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:39:19.616Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:39:19.617Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:47:51.768Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T12:47:51.768Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T13:04:55.911Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'
2021-02-22T13:04:55.911Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=Admin&appli=1'

Dumps

Versions

• homebridge-tydom: v0.21.6

Additional context

[bgillet-tbscg]

It might be the case of my Lifedomus (which replaces Tydom 3.0) is missing some connectivity. Both "Pack Connectivité" and "Pack Connectivité Avancée" are not available and are locked. I only have X3D and Velux KLF200 enabled on the Lifedomus. Can anybody confirm what is needed on the Tydom box? In the log we clearly see there is no answer whatsoever from my Lifedomus box...

[mgcrea]

@bgillet-tbscg the URL connection does not look right, are you sure your username configuration is right? It looks like you've set it to Admin where it is supposedly expected to receive a macAdress value (eg. "username": "001A25123456"). Check your username in the mobile app:

Your username is the MAC Address of your local Tydom hardware, it should be 001A25 + your 6-character home ID that you can find in the mobile app.

I don't know anything about tydom3 packs but I think that if your mobile app is working this plugin should work too.

[bgillet-tbscg]

Ok In this case my username should be 001A25GILLET BUt result is the same - no connection to the box. Thé URL itself does not work in a browser neither, it just says server can’t connect.

…

-- Bertrand Gillet +33 658902058 Le 22 févr. 2021 à 19:43, Olivier Louvignes <[email protected]> a écrit :  @bgillet-tbscg<https://github.com/bgillet-tbscg> the URL connection does not look right, are you sure your username configuration is right? It looks like you've set it to Admin where it is supposedly expected to receive a macAdress value (eg. "username": "001A25123456"). Check your username in the mobile app: Your username is the MAC Address of your local Tydom hardware, it should be 001A25 + your 6-character home ID that you can find in the mobile app. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#58 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AROWGW4A6HTEWE7ZI7ZXOX3TAKQV3ANCNFSM4YARZQXQ>. This email and its attachments may contain confidential or proprietary information and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of TBSCG. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error. For further information on how we process your data, please see our Privacy Policy<https://www.tbscg.com/home/privacy-policy>.

[StephanH27]

@bgillet-tbscg . It's a MacAdress, somethings like 00:1A:25:0A:0B:0C ...
Only hexadecimals characters are allowed ...

[bgillet-tbscg]

No change with this one: https://192.168.1.40/mediation/client?mac=18E366700113&appli=1%27
The problem is not the request itself, it's the fact the server does not answer at all :/

Starting to advertise 'Homebridge BE8A E166' using bonjour-hap backend!
[2/23/2021, 9:17:35 AM] Homebridge v1.3.0 (Homebridge BE8A) is running on port 51648.
2021-02-23T08:17:35.916Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:37.059Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:37.059Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:39.147Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:39.148Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:43.247Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:43.248Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:51.311Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:17:51.311Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:18:07.401Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:18:07.401Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:18:39.480Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:18:39.481Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:19:43.577Z tydom-client About to retry GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'
2021-02-23T08:19:43.578Z tydom-client About to GET request with url='https://192.168.1.40/mediation/client?mac=18E366700113&appli=1'

[bgillet-tbscg]

I found the Mac address of eth0 of the Lifedomus in its configuration UI.
Now I try this: https://mediation.tydom.com/mediation/client?mac=94c6911fd560&appli=1
I use the password of my "Admin" user on my Lifedomus - but here I really unsure it's the right password :)

[2/24/2021, 11:14:30 AM] Homebridge v1.3.0 (Homebridge BE8A) is running on port 51648.
2021-02-24T10:14:30.256Z tydom-client About to GET request with url='https://mediation.tydom.com/mediation/client?mac=94c6911fd560&appli=1'
2021-02-24T10:14:30.374Z tydom-client Attempting to open new socket for hostname='mediation.tydom.com'
2021-02-24T10:14:30.441Z tydom-client Tydom socket error for hostname='mediation.tydom.com'
2021-02-24T10:14:30.442Z tydom-client Tydom socket closed for hostname='mediation.tydom.com'
[2/24/2021, 11:14:30 AM] [Tydom] Disconnected from Tydom hostname='mediation.tydom.com'"
[2/24/2021, 11:14:30 AM] [Tydom] Failed to connect to Tydom hostname=mediation.tydom.com with username="94c6911fd560"
(node:21497) UnhandledPromiseRejectionWarning: Error: Unexpected server response: 401
at ClientRequest. (/usr/local/lib/node_modules/homebridge-tydom/node_modules/ws/lib/websocket.js:604:7)
at ClientRequest.emit (events.js:315:20)
at HTTPParser.parserOnIncomingClient (_http_client.js:641:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
at TLSSocket.socketOnData (_http_client.js:509:22)
at TLSSocket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at TLSSocket.Readable.push (internal/streams/readable.js:223:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
(Use node --trace-warnings ... to show where the warning was created)
(node:21497) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:21497) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[mgcrea]

@bgillet-tbscg as-tu l'application mobile tydom qui fonctionne sur un smartphone? Ce sont les mêmes identifiants que l'application mobile.

[StephanH27]

On parle d'un Tydom 2.0 ou d'une Lifedomus 3 (qui est totalement différente des Tydom) ?

[bgillet-tbscg]

Lifedomus

[StephanH27]

je ne suis pas certain du tout que Lifedomus (une société rachetée par DettaDoire) utilise le même serveur de médiation que ceux de Tydom 1 et 2 ...

[bgillet-tbscg]

Forget about this piece of shit that is Lifedomus - it's been killed by Delta Dore. I paid a significant amount of money for this in 2017, and now I can thrown everything to the bin. Nice move, Delta Dore. I now need to find a solution to replace this Lifedomus box to control my Delta Dore lights and my Somfy shades.
http://www.etts.fr/news/arret_lifedomus

[mgcrea]

Just to let you know that if you are still stuck with lifedomus and that the current application works to control your devices, you might be able to retreive a working username/password for your setup using the procedure described in this ticket: #72 (comment)

Worked for some Tydom 1.0 users that have auto-generated passwords.