J’ai essayé de changer l’IP de ma box, mais impossible. Je lui force une IP fixe sur mon routeur (Unifi), mais la box semble garde toujours la même (je vois ça dans l’appli dans les infos).
Comment lui as-tu changé l’IP toi ?
Je pense que le problème vient de là : le mqtt n’arrive pas à accrocher une connexion sur la Tydom 2.0.
Mais je sèche pour la solution.
Si une personne connais la solution pour mon problème de chauffage je suis intéressé j’essaie de l’intégrer à ce graphique si une personne peut l’adapter ou autre
il me faudrait l’intégrer sur température intérieur
Bien sûr oui 
Ma config fonctionnait il y a 1 mois. Elle occasionnait bcp de lenteur pour accéder à la Tydom depuis l’appli.
Et un jour plus aucun accès, sans rien toucher !
Au niveau log ?
Can you please write in english? I’m having very high cpu usage after the latest update. Screenshot is from hypervisor. Twice I’ve had to restart the addon, now it’s disabled due to this.
Hi,
Please raise an issue on the GitHub project with all possible informations (hardware, addon version, configuration…) and logs at debug level.
It will be easier to track than on this thread.
Thank you.
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
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) 
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. 