Looked through the logs, nothing out of the ordinary when the cpu goes crazy though, but sure I can raise an issue.
As tu la solution à mon problème pour avoir un sensor sur l’addon tydom2mqtt ?
merci bien
Hi all,
I have a question about round-trip updates. Everything is set-up and working (Mqtt, tydom add-on…) and I’m starting to put some cards in the dashboard.
However, I see the following behaviour using the “Light” card: If I turn on the light in HA, it’s fine, Tydom app is updated (1-2 seconds). But, if I turn off the light in Tydom app, the card is not updated.
So, basically, is there any way to update the card whenever there is a change in Tydom app? I have checked the logs (Add-on), and the Add-on is notified about the changes in the app, so, it’s just from the Add-on to the card, I suppose.
Am I missing some configuration? Any hint?
Thanks!
Jordi
1 Like
Hello @fmartinou, j’ai actuellement ce problème :
2023-04-05 16:00:17,088 - main - WARNING - Unable to handle message: no close frame received or sent
Quand je le met en mode error j’ai ceci 
2023-04-05 21:16:13,349 - The configuration is valid
2023-04-05 21:16:16,253 - sensors.Switch - ERROR - ‘level’
Aurais tu quelques choses pour voir les caméras (tycam 2000 & 2100) ?
Hello everyone. Let me make a warning:
Be very careful with this integration, it really doesn’t work well and completely crashed my Tydom2 box.
j’ai ça aussi régulièrement, si on relance c’est OK.
il faudrait peut-être mettre en place une reconnexion automatique
The feature developed by @CyrilP (getting the tydom password using the Delta dore cloud) is available in the latest version (3.1.2) 
1 Like
Hi everyone !
I installed Tydom2MQTT and it finaly made it work started after some tries
Unfortunatelly it does not seam to recognise my “Rothelec heaters” that are linked to my Tydom.
Any clue on how to solve this problem ?
Thanks in advance 
My Tydom2MQTT Log :
--- Logging error ---
Traceback (most recent call last):
File "/usr/local/lib/python3.11/logging/__init__.py", line 1110, in emit
msg = self.format(record)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 953, in format
return fmt.format(record)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 687, in format
record.message = record.getMessage()
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 377, in getMessage
msg = msg % self.args
~~~~^~~~~~~~~~~
TypeError: not all arguments converted during string formatting
Call stack:
File "/app/main.py", line 119, in <module>
main()
File "/app/main.py", line 115, in main
loop.run_forever()
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 607, in run_forever
self._run_once()
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1922, in _run_once
handle._run()
File "/usr/local/lib/python3.11/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/app/main.py", line 54, in listen_tydom
await message_handler.incoming_triage()
File "/app/tydom/MessageHandler.py", line 250, in incoming_triage
await self.parse_response(incoming)
File "/app/tydom/MessageHandler.py", line 294, in parse_response
logger.warning('Unknown message type received', data)
Message: 'Unknown message type received'
Arguments: ('{"status": "CLOSE", "lastAccess": "2021-10-05T19:38:00Z"}',)
2023-05-21 19:23:37,690 - tydom.MessageHandler - WARNING - Unknown device name (1674257513_1674257513)
2023-05-21 19:23:37,690 - tydom.MessageHandler - WARNING - Unknown device type (1674257513_1674257513)
2023-05-21 19:23:37,690 - tydom.MessageHandler - INFO - Device update (id=1674257513, endpoint=1674257513, name=, type=)
2023-05-21 19:23:37,690 - tydom.MessageHandler - WARNING - Unknown device name (1674257625_1674257625)
2023-05-21 19:23:37,690 - tydom.MessageHandler - WARNING - Unknown device type (1674257625_1674257625)
2023-05-21 19:23:37,690 - tydom.MessageHandler - INFO - Device update (id=1674257625, endpoint=1674257625, name=, type=)
2023-05-21 19:23:37,691 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:23:37,691 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:23:37,691 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:23:39,219 - tydom.MessageHandler - WARNING - Unknown device name (1674257513_1674257513)
2023-05-21 19:23:39,219 - tydom.MessageHandler - WARNING - Unknown device type (1674257513_1674257513)
2023-05-21 19:23:39,219 - tydom.MessageHandler - INFO - Device update (id=1674257513, endpoint=1674257513, name=, type=)
2023-05-21 19:23:40,431 - tydom.MessageHandler - WARNING - Unknown device name (1674257625_1674257625)
2023-05-21 19:23:40,431 - tydom.MessageHandler - WARNING - Unknown device type (1674257625_1674257625)
2023-05-21 19:23:40,431 - tydom.MessageHandler - INFO - Device update (id=1674257625, endpoint=1674257625, name=, type=)
2023-05-21 19:29:38,580 - tydom.MessageHandler - WARNING - Unknown device name (1674257212_1674257212)
2023-05-21 19:29:38,580 - tydom.MessageHandler - WARNING - Unknown device type (1674257212_1674257212)
2023-05-21 19:29:38,581 - tydom.MessageHandler - INFO - Device update (id=1674257212, endpoint=1674257212, name=, type=)
2023-05-21 19:29:38,581 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:29:38,581 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:29:38,581 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:29:39,739 - tydom.MessageHandler - WARNING - Unknown device name (1674257212_1674257212)
2023-05-21 19:29:39,739 - tydom.MessageHandler - WARNING - Unknown device type (1674257212_1674257212)
2023-05-21 19:29:39,740 - tydom.MessageHandler - INFO - Device update (id=1674257212, endpoint=1674257212, name=, type=)
2023-05-21 19:29:42,120 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:29:42,121 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:29:42,121 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:35:39,459 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:35:39,459 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:35:39,459 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:38:43,706 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:38:43,706 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:38:43,706 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:41:40,339 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:41:40,340 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:41:40,340 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
2023-05-21 19:44:40,774 - tydom.MessageHandler - WARNING - Unknown device name (1674257212_1674257212)
2023-05-21 19:44:40,774 - tydom.MessageHandler - WARNING - Unknown device type (1674257212_1674257212)
2023-05-21 19:44:40,775 - tydom.MessageHandler - INFO - Device update (id=1674257212, endpoint=1674257212, name=, type=)
2023-05-21 19:44:45,096 - tydom.MessageHandler - WARNING - Unknown device name (1674257690_1674257690)
2023-05-21 19:44:45,096 - tydom.MessageHandler - WARNING - Unknown device type (1674257690_1674257690)
2023-05-21 19:44:45,097 - tydom.MessageHandler - INFO - Device update (id=1674257690, endpoint=1674257690, name=, type=)
maybe you can now close issue #63 Support for tydom username & password login · Issue #63 · fmartinou/tydom2mqtt · GitHub
I’ve created a new PR to fix the disconnection problem. I have it running successfully for a few days now
hello, i’m a newby with HA and Tydom, for some physicall constraint, the only solution i find is to install some deltadore devices, tyxia 5731 (+ telco tyxia 1705) + tydom Pro to manage venetian blinds (up/down/stop/slats)
before i will buy all the material (10 pack + tydom) i have to be sure i will be able to drive all the venetian blinds with HA (on RPI4, HAOS, 32bit)
so my questions are:
1 - is Tydom Pro compatible ?
2 - what is to do about the user / password of the tydom (do i need to do something ?)
3 - what release / addon do i have to install on HA (HACS / standard / …)
4 - may i have to create a new user on HA ?
5 - are the tyxia 5731 already integrated or do i need to add something manually somewhere?
before i asked, i took a time to read a great part of this topic, sorry if all theses questions are obvious and
thank you for anyone to take a time to answser and add comments before i spend a lot of money with this solution.
Same error, had it 3 times in the last week whereas I had no issue until now. I’m forced to restart the addon when that happens. I’m wondering what changed to have this issue only now. 
There’s a pending pull request for this. you can try to apply the patch on your installation :
the cause is probably a firmware update which causes the connection to be closed by the tydom after a delay
Hi,
I’ve a installation of tydom2mqtt who works since many months.
I’ve added a new door sensor and rename the other one but I can’t see the new sensor and the old renamed.
However I can arm/unarm alarm.
But in logs I’ve an error who is perhaps linked to these problems :
--- Logging error ---
Traceback (most recent call last):
File "/usr/local/lib/python3.11/logging/__init__.py", line 1110, in emit
msg = self.format(record)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 953, in format
return fmt.format(record)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 687, in format
record.message = record.getMessage()
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/logging/__init__.py", line 377, in getMessage
msg = msg % self.args
~~~~^~~~~~~~~~~
TypeError: not all arguments converted during string formatting
Call stack:
File "/app/main.py", line 125, in <module>
main()
File "/app/main.py", line 121, in main
loop.run_forever()
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 607, in run_forever
self._run_once()
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1922, in _run_once
handle._run()
File "/usr/local/lib/python3.11/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/app/main.py", line 55, in listen_tydom
await message_handler.incoming_triage()
File "/app/tydom/MessageHandler.py", line 309, in incoming_triage
await self.parse_response(incoming)
File "/app/tydom/MessageHandler.py", line 346, in parse_response
logger.warning('Unknown message type received', data)
Message: 'Unknown message type received'
Arguments: ('[]\r\n',)
Any idea ?
La dernière version 3.4.1 semble résoudre le problème. Je vois bien les nouveaux appareils ajoutés sur le Tydom.
Par contre, j’ai maintenant un message qui ne semble pas bloquant.
2023-09-02 17:07:23,360 - tydom.MessageHandler - WARNING - Unknown message type received ([]
)
Et bien que je vois les nouveaux devices dans les logs de l’addon Tydom2Mqtt, ils n’apparaissent pas dans HA malgré des redémarrages…
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Tydom2MQTT - Beta
Link between a Delta Dore's Tydom 1.0 Hub and and a MQTT broker, unofficial of course, hassio addon version
-----------------------------------------------------------
Add-on version: release_v1.2.4
You are running the latest version of this add-on.
parse error: Expected string key before ':' at line 1, column 4
[21:46:27] ERROR: Unknown HTTP error occured
System: (aarch64 / raspberrypi3-64)
Home Assistant Core: 2023.8.4
Home Assistant Supervisor: 2023.08.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting /opt/tydom2mqtt/main.py
Hello,
I’m trying to install Tydom Beta, but it hangs for 10 seconds after installation. I’ve tried debugging, but the error remains the same.
My Discord : Shadorlo
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Tydom2MQTT - Beta
Link between a Delta Dore's Tydom 1.0 Hub and and a MQTT broker, unofficial of course, hassio addon version
-----------------------------------------------------------
Add-on version: release_v1.2.4
You are running the latest version of this add-on.
parse error: Expected string key before ':' at line 1, column 4
[23:38:07] ERROR: Unknown HTTP error occured
System: (aarch64 / raspberrypi3-64)
Home Assistant Core: 2023.8.4
Home Assistant Supervisor: 2023.08.3
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting /opt/tydom2mqtt/main.py
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
STARTING TYDOM2MQTT
Dectecting environnement......
/data/options.json detected ! Hassio Addons Environnement : parsing options.json....
{'TYDOM_MAC': '********', 'TYDOM_IP': '192.168.1.16', 'TYDOM_PASSWORD': '*******', 'TYDOM_ALARM_PIN': 123456, 'TYDOM_ALARM_HOME_ZONE': 1, 'TYDOM_ALARM_NIGHT_ZONE': 2, 'MQTT_HOST': 'localhost', 'MQTT_USER': 'userrrrr', 'MQTT_PASSWORD': 'userrrr', 'MQTT_PORT': 1883, 'MQTT_SSL': False, 'log_level': 'info'}
Initialising TydomClient Class
Setting local mode context.
Starting main loop_task
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Attempting MQTT connection...
MQTT host : localhost
MQTT user : userrrrr
##################################
Subscribing to : +/tydom/#
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
TYDOM WEBSOCKET CONNECTION INITIALISING....
Building headers, getting 1st handshake and authentication....
Upgrading http connection to websocket....
Attempting websocket connection with tydom hub.......................
Host Target :
192.168.1.16
Tydom Client is connected to websocket and ready !
Requesting 1st data...
>>>>>>>>>> Sending to tydom client..... GET /info
##################################
##################################
>>>>>>>>>> Sending to tydom client..... POST /refresh/all
>>>>>>>>>> Sending to tydom client..... GET /configs/file
>>>>>>>>>> Sending to tydom client..... GET /devices/data
<<<<<<<<<< Receiving from tydom_client...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
receiveMessage error
RAW :
b'HTTP/1.1 200 OK\r\nServer: Tydom-*******\r\nUri-Origin: /info\r\nContent-Type: application/json\r\nTransfer-Encoding: chunked\r\nTransac-Id: 0\r\n\r\n1\r\n{\r\n18\r\n"productName": "TYDOM2",\r\n16\r\n"mac": "***********",\r\n11\r\n"config": "prod",\r\n12\r\n"bddEmpty": false,\r\nF\r\n"bddStatus": 0,\r\n10\r\n"apiMode": true,\r\n1C\r\n"mainVersionSW": "03.08.19",\r\n1C\r\n"mainVersionHW": "00.00.01",\r\n14\r\n"mainId": "6414118",\r\n1C\r\n"mainReference": "21260010",\r\n1B\r\n"keyVersionSW": "01.04.14",\r\n1B\r\n"keyVersionHW": "00.00.01",\r\n1E\r\n"keyVersionStack": "04.00.50",\r\n1B\r\n"keyReference": "21260011",\r\n31\r\n"bootReference": "", "bootVersion": "02.211.128",\r\n10\r\n"TYDOM.dat": 43,\r\n12\r\n"config.json": 43,\r\nE\r\n"mom.json": 0,\r\n13\r\n"gateway.dat": 176,\r\nF\r\n"bdd.json": 12,\r\n12\r\n"collect.json": 1,\r\n12\r\n"groups.json": 40,\r\n13\r\n"mom_api.json": 18,\r\n13\r\n"scenario.json": 2,\r\n11\r\n"site.json": 378,\r\n12\r\n"bdd_mig.json": 1,\r\n13\r\n"info_mig.json": 0,\r\n13\r\n"info_col.json": 0,\r\n12\r\n"absence.json": 9,\r\n13\r\n"anticip.json": 16,\r\n12\r\n"trigger.json": 0,\r\n12\r\n"bioclim.json": 0,\r\n16\r\n"data_config.json": 0,\r\n26\r\n"urlMediation": "mediation.tydom.com",\r\n15\r\n"pltRegistered":true,\r\n19\r\n"updateAvailable": false,\r\n17\r\n"passwordEmpty": false,\r\nF\r\n"maintenance":{\r\n28\r\n"id": "ffffffffffffffffffffffffffffffff"\r\n2\r\n},\r\nB\r\n"geoloc": {\r\n15\r\n"longitude": 1405123,\r\n14\r\n"latitude": 43996921\r\n2\r\n},\r\nA\r\n"clock": {\r\n25\r\n"clock": "2023-09-05T23:38:14+02:00",\r\n10\r\n"source": "ntp",\r\nF\r\n"timezone": 60,\r\n14\r\n"summerOffset": "ON"\r\n2\r\n},\r\nC\r\n"moments": {\r\nC\r\n"suspend": {\r\n7\r\n"to": 0\r\n3\r\n}},\r\nF\r\n"local_claim":{\r\n12\r\n"status": "CLOSE",\r\n24\r\n"lastAccess": "2014-01-01T00:00:00Z"\r\n2\r\n},\r\nC\r\n"weather": {\r\n28\r\n"outTempSrc":{"devId":null,"epId":null},\r\n27\r\n"weatherSrc":{"devId":null,"epId":null}\r\n2\r\n},\r\nE\r\n"protocols": [\r\n71\r\n{"protocol":"X3D", "available":true, "installed":true, "ready":true, "status":"running", "installStatus":"idle"},\r\n3B\r\n{"protocol":"ZIGBEE", "available":true, "installed":false},\r\n27\r\n{"protocol":"X3DV", "available":false},\r\n2C\r\n{"protocol":"PltService", "available":false}\r\n1\r\n]\r\n1\r\n}\r\n0\r\n\r\n'
Incoming payload :
None
Error :
type object 'HTTPResponse' has no attribute 'from_httplib'
Exiting to ensure systemd restart....
Starting /opt/tydom2mqtt/main.py
I have now managed to connect it:
“Tydom Client is connected to websocket and ready!”
But I’m getting lots of errors. What can I do?
Hi,
I’m unable to see new devices on MQTT.
Especially « belmDoor » type devices.
However, I can enable/disable alarm.
sensors.Sensor - INFO - Binary sensor created / updated : kernelUpToDate ON
2023-10-01 17:58:05,648 - sensors.Alarm - INFO - Alarm created / updated : Tyxal Alarm 1520677197_1520677197 disarmed
2023-10-01 17:58:05,648 - tydom.MessageHandler - INFO - Device update (id=1619877546, endpoint=1619877546, name=Porte balcon, type=belmDoor)
2023-10-01 17:58:05,649 - sensors.Sensor - INFO - Binary sensor created / updated : intrusionDetect OFF
2023-10-01 17:58:05,650 - tydom.MessageHandler - INFO - Device update (id=1693389439, endpoint=1693389439, name=Porte salle bas, type=belmDoor)
2023-10-01 17:58:05,651 - sensors.Sensor - INFO - Binary sensor created / updated : intrusionDetect OFF
2023-10-01 17:58:05,659 - tydom.MessageHandler - WARNING - Unknown message type received ([]
)
Do you know why ?
Any solution to this problem?