fmartinou / tydom2mqtt Goto Github PK

Bonjour,

je rencontre des difficultés avec une porte de garage, celle ci est bien détectée avec la création d'un switch mais aucune actions ou remontée d'informations ne s'effectuent.
Les portes de garage sont elles gérées?

merci d'avance pour votre retour.

informations :

Product garage_door 1 (switch.product_garage_door_1)
MQTT discovery data:
Topic: homeassistant/switch/tydom/3_0/config
Payload
name: Product garage_door 1
unique_id: '3_0'
command_topic: switch/tydom/3_0/set_levelCmdGate
state_topic: switch/tydom/3_0/state
json_attributes_topic: switch/tydom/3_0/attributes
payload_on: TOGGLE
payload_off: TOGGLE
retain: 'false'
device:
manufacturer: Delta Dore
model: Porte
name: Product garage_door 1
identifiers: '3_0'
platform: mqtt
Subscribed topics:
switch/tydom/3_0/attributes
0 dernier(s) message(s) reçu(s)
switch/tydom/3_0/state
0 dernier(s) message(s) reçu(s)

device_id_tydom__Product_garage_door_1 (sensor.device_id_tydom_product_garage_door_1)
MQTT discovery data:
Topic: homeassistant/sensor/tydom/device_id_tydom_3_0/config
Payload
name: device_id_tydom__Product_garage_door_1
unique_id: device_id_tydom_3_0
device:
manufacturer: Delta Dore
model: Sensor
name: device_id_tydom__Product_garage_door_1
identifiers: 3_0_sensors
state_topic: sensor/tydom/device_id_tydom_3_0/state
platform: mqtt
Subscribed topics:
sensor/tydom/device_id_tydom_3_0/state
1 dernier(s) message(s) reçu(s)
Received 22:35:27
QoS: 0
Payload: 3
endpoint_id_tydom__Product_garage_door_1 (sensor.endpoint_id_tydom_product_garage_door_1)
MQTT discovery data:
Topic: homeassistant/sensor/tydom/endpoint_id_tydom_3_0/config
Payload
name: endpoint_id_tydom__Product_garage_door_1
unique_id: endpoint_id_tydom_3_0
device:
manufacturer: Delta Dore
model: Sensor
name: endpoint_id_tydom__Product_garage_door_1
identifiers: 3_0_sensors
state_topic: sensor/tydom/endpoint_id_tydom_3_0/state
platform: mqtt
Subscribed topics:
sensor/tydom/endpoint_id_tydom_3_0/state
1 dernier(s) message(s) reçu(s)
Received 22:35:27
QoS: 0
Payload: 0
id_tydom__Product_garage_door_1 (sensor.id_tydom_product_garage_door_1)
MQTT discovery data:
Topic: homeassistant/sensor/tydom/id_tydom_3_0/config
Payload
name: id_tydom__Product_garage_door_1
unique_id: id_tydom_3_0
device:
manufacturer: Delta Dore
model: Sensor
name: id_tydom__Product_garage_door_1
identifiers: 3_0_sensors
state_topic: sensor/tydom/id_tydom_3_0/state
platform: mqtt
Subscribed topics:
sensor/tydom/id_tydom_3_0/state
1 dernier(s) message(s) reçu(s)
Received 22:35:27
QoS: 0
Payload: 3_0
thermicDefect_tydom__Product_garage_door_1 (binary_sensor.thermicdefect_tydom_product_garage_door_1)
MQTT discovery data:
Topic: homeassistant/binary_sensor/tydom/thermicdefect_tydom_3_0/config
Payload
name: thermicDefect_tydom__Product_garage_door_1
unique_id: thermicDefect_tydom_3_0
device:
manufacturer: Delta Dore
model: Sensor
name: thermicDefect_tydom__Product_garage_door_1
identifiers: 3_0_sensors
state_topic: binary_sensor/tydom/thermicDefect_tydom_3_0/state
platform: mqtt
Subscribed topics:
binary_sensor/tydom/thermicDefect_tydom_3_0/state
1 dernier(s) message(s) reçu(s)
Received 22:35:27
QoS: 0
Payload: False

Bonjour,
suite à l'installation de tydom2mqtt, la totalité de mes son bien remontés hormis les modules BSO.
Le journal indique :
2022-12-21 15:15:51,816 - tydomMessagehandler - INFO - POST message processed !
2022-12-21 15:16:03,969 - tydomMessagehandler - WARNING - 1607415916_1607415916 not in dic device_name
2022-12-21 15:16:03,969 - tydomMessagehandler - WARNING - 1607415916_1607415916 not in dic device_type
2022-12-21 15:16:03,970 - tydomMessagehandler - INFO - Incoming data parsed successfully !

Merci pour votre aide.

Hi,

An issue with my tywatt consumptions appeared at the beginning of the year.
Since January 1st, each consumption sensor (ELEC_OUTLET_tydom__Tywatt, ELEC_HEATING_tydom__Tywatt, etc...) receive 2 different information: The total consumption since the setup of my HA, and a few minutes later the yearly consumption.
Here is a look at my consumption history (from 31/12/2022 at 23:00, to 01/01/2023 at 01:00):

ELEC_TOTAL_tydom__Tywatt is the only one not facing this issue.
From what I understand, the total consumption and yearly consumption were the same in 2022 (which looks right because I started my HA in 2022). But now these are 2 different values assigned to the same sensor.

Is anyone facing the same issue ?
Please find below the part of the log showing the issue.

2023-01-04 11:56:27,231 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 11:56:27,232 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyInstant&unit=ELEC_A&reset=false
2023-01-04 11:56:27,663 - sensors - INFO - Sensor created / updated : ELEC_A_tydom__Tywatt 600
2023-01-04 11:56:27,664 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:57:09,667 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 11:57:09,668 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_TOTAL&reset=false
2023-01-04 11:57:10,758 - sensors - INFO - Sensor created / updated : ELEC_TOTAL_tydom__Tywatt 8712934
2023-01-04 11:57:10,760 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:57:19,447 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:58:01,453 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 11:58:01,453 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_HEATING&reset=false
2023-01-04 11:58:01,602 - sensors - INFO - Sensor created / updated : ELEC_HEATING_tydom__Tywatt 1376367
2023-01-04 11:58:01,603 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:58:05,821 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:58:47,823 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 11:58:47,824 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_COOLING&reset=false
2023-01-04 11:58:52,154 - sensors - INFO - Sensor created / updated : ELEC_COOLING_tydom__Tywatt 0
2023-01-04 11:58:52,155 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 11:59:34,158 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 11:59:34,159 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_HOTWATER&reset=false
2023-01-04 11:59:34,309 - sensors - INFO - Sensor created / updated : ELEC_HOTWATER_tydom__Tywatt 803320
2023-01-04 11:59:34,310 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 12:00:16,315 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 12:00:16,316 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_OUTLET&reset=false
2023-01-04 12:00:18,781 - sensors - INFO - Sensor created / updated : ELEC_OUTLET_tydom__Tywatt 4489406
2023-01-04 12:00:18,782 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 12:00:22,820 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 12:01:04,824 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 12:01:04,825 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyIndex&dest=ELEC_OTHER&reset=false
2023-01-04 12:01:04,977 - sensors - INFO - Sensor created / updated : ELEC_OTHER_tydom__Tywatt 2043841
2023-01-04 12:01:04,978 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2023-01-04 12:01:46,989 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2023-01-04 12:01:46,990 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1634493627/endpoints/1634493631/cdata?name=energyDistrib&period=YEAR&periodOffset=0&src=ELEC
2023-01-04 12:01:49,350 - sensors - INFO - Sensor created / updated : ELEC_HEATING_tydom__Tywatt 16949
2023-01-04 12:01:49,350 - sensors - INFO - Sensor created / updated : ELEC_HOTWATER_tydom__Tywatt 18442
2023-01-04 12:01:49,351 - sensors - INFO - Sensor created / updated : ELEC_OUTLET_tydom__Tywatt 33168
2023-01-04 12:01:49,352 - sensors - INFO - Sensor created / updated : ELEC_OTHER_tydom__Tywatt 16111
2023-01-04 12:01:49,352 - tydomMessagehandler - INFO - Incoming data parsed successfully 

Binary sensors don't run., No matching payload found for entity: thermicDefect_tydom despite the modification made in the 1.3.1 version. Their state is always "Unknown"
extracts of logs

2022-09-10 17:30:41.663 INFO (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: thermicDefect_tydom__Chambre_1 with state topic: binary_sensor/tydom/thermicDefect_tydom_1651773567_1651773567/state. Payload: 'False'
2022-09-10 17:30:41.695 INFO (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: onFavPos_tydom__Chambre_1 with state topic: binary_sensor/tydom/onFavPos_tydom_1651773567_1651773567/state. Payload: 'False'
2022-09-10 17:30:41.696 INFO (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: obstacleDefect_tydom__Chambre_1 with state topic: binary_sensor/tydom/obstacleDefect_tydom_1651773567_1651773567/state. Payload: 'False'
2022-09-10 17:30:41.808 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: cover tydom 1651773567_1651773567

Hi,

I have a connected door (https://www.k-line.fr/porte-ouverture-distance-connectee) I can open remotely. It use a Tydom box, but it's not detected at all by tydom2mqtt.
I have another device on the same box (door open detection), and this one works.

Here the startup logs of tydom2mqtt :

2022-12-26 11:34:14,807 - __main__ - INFO - STARTING TYDOM2MQTT
2022-12-26 11:34:14,807 - __main__ - INFO - Detecting environnement......
2022-12-26 11:34:14,808 - __main__ - INFO - No /data/options.json, seems we are not in hassio addon mode.
2022-12-26 11:34:14,808 - tydomConnector - INFO - Initialising TydomClient Class
2022-12-26 11:34:14,808 - tydomConnector - INFO - Setting local mode context.
2022-12-26 11:34:14,813 - __main__ - INFO - Starting main loop_task
/app/main.py:141: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()
2022-12-26 11:34:14,816 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-12-26 11:34:14,816 - mqtt_client - INFO - Attempting MQTT connection...
2022-12-26 11:34:14,817 - mqtt_client - INFO - MQTT host : localhost
2022-12-26 11:34:14,817 - mqtt_client - INFO - MQTT user : hass
2022-12-26 11:34:14,824 - gmqtt.mqtt.protocol - INFO - [CONNECTION MADE]
2022-12-26 11:34:14,827 - mqtt_client - INFO - ##################################
2022-12-26 11:34:14,828 - mqtt_client - INFO - Subscribing to : +/tydom/#
2022-12-26 11:34:14,828 - gmqtt.mqtt.package - INFO - [SEND SUB] 1 [b'homeassistant/status']
2022-12-26 11:34:14,829 - gmqtt.mqtt.package - INFO - [SEND SUB] 2 [b'+/tydom/#']
2022-12-26 11:34:14,831 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,)
2022-12-26 11:34:14,831 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,)
2022-12-26 11:34:14,832 - tydomConnector - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-12-26 11:34:14,832 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING....                     
2022-12-26 11:34:14,833 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication....
2022-12-26 11:34:16,708 - tydomConnector - INFO - Upgrading http connection to websocket....
2022-12-26 11:34:16,709 - tydomConnector - INFO - Attempting websocket connection with tydom hub.......................
2022-12-26 11:34:16,709 - tydomConnector - INFO - Host Target : 192.168.1.11
2022-12-26 11:34:18,136 - __main__ - INFO - Tydom Client is connected to websocket and ready !
2022-12-26 11:34:18,137 - tydomConnector - INFO - Requesting 1st data...
2022-12-26 11:34:18,137 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /info
2022-12-26 11:34:18,138 - tydomConnector - INFO - ##################################
2022-12-26 11:34:18,139 - tydomConnector - INFO - ##################################
2022-12-26 11:34:18,139 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-12-26 11:34:18,141 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /configs/file
2022-12-26 11:34:18,142 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/cmeta
2022-12-26 11:34:23,148 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/data
2022-12-26 11:34:23,154 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-12-26 11:34:23,161 - tydomMessagehandler - INFO - Configuration updated
2022-12-26 11:34:23,161 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-12-26 11:34:23,164 - tydomMessagehandler - INFO - Metadata configuration updated
2022-12-26 11:34:23,165 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-12-26 11:34:23,169 - sensors - INFO - Sensor created / updated : openState_tydom__Porte_Fenêtre LOCKED
2022-12-26 11:34:23,170 - tydomMessagehandler - INFO - Incoming data parsed successfully !

Any idea or way to support it ?

Thank you !

Hello everyone,
I'm new with Tydom box, I have just recently bought a house with this techno.
I've just installed the box. Everything is OK in the app, but as all my domotic stuff I want it in HA.
So I've installed the fmartinou's add-on (thaks a lot, to you) but when I fill the configuration and restart the add-on, the cofiguration seems to not take effect.
As you can see there, I have a login/password for my MQTT broker, but the Add-on try to connect with default cofiguration.

Any idea ?
Many thanks in advance,

Best Regards,
Gauthier

J’ai installé tydomtoMQTT et cela fonctionne très bien. Sauf que, pour chaque lampe cela m’a créé 2 appareils différents l’un avec les capteurs (Entités liées: level_tydom__Plafond_Bureau, thermicDefect_tydom__Plafond_Bureau, id_tydom__Plafond_Bureau, device_id_tydom__Plafond_Bureau, endpoint_id_tydom__Plafond_Bureau) , l’autre avec le controles (light.lum_salle_de_sport_plafond).
Mon problème c’est que quand je contrôle ma lampe depuis home assistant, Il remonte bien l’info dans « level_tydom__Plafond_Bureau » passant de 0 quand éteint à 100 quand allumé. L’icône du contrôleur passe bien au jaune donc allumé.

Par contre si j’appuie sur le bouton physique le capteur « level_tydom__Plafond_Bureau » réagit correctement mais l’icône du contrôleur ne réagit pas car les deux appareils sont séparés. Par conséquent si j’allume par home assistant ma lumière et que je l’étain physiquement l’icône du contrôleur ne bouge pas.

Du coup comment faire pour réunir dans un seul appareil les commande et les sensor. Je le même problème pour les volets

Hi,
how can we do this with the new Tydom Home product ?
I don't know how to change/reset hardware password and don't know even if exists !? :(

Hi,

Have you read this part of the documentation?

The password needed here is not the same as the password you're using on the Tydom app.
It' already been discussed here, here, here, here, here and here 😀

You likely need to install an old Tydom app version to be able to set/reset the tydom hardware appliance password.

Originally posted by @fmartinou in #24 (comment)

Hello,

I have been using the february version of tydom2mqtt.
I tryed to update in July, the new version works flawlessly for 6 hours, but then makes my tydom 1.0 crash. I reverted to the Feb. release.
I tryed to update yesterday, I was happy to find the shutter intrusion sensor working, but then during the night the tydom 1.0 crashed.
The container keep restarting, the bridge is crashed and need to be restarted physically.

My first question is : what is the recommanded firmware of the tydom ? I refused a firware upgrade on the app the other day because I was scrared I couldn't change the password anymore.

I run docker version of HA and mosquitto. The command I run is the following :

docker run -d --restart always --name tydom2mqtt -e TYDOM_MAC="macadress" -e TYDOM_PASSWORD="password1" --network=chuwi --ip 172.120.0.4 -h tydom2mqtt -e MQTT_HOST="192.168.1.35" -e MQTT_USER="ha" -e MQTT_PASSWORD="password2" fmartinou/tydom2mqtt

following an update, the AUTO preset mode seems to have disappeared? This mode existed previously and was very useful on the delta dore themostat

Hello.

I am very grateful for this addon, it's running perfectly.

But some installations have more than 1 Tydom Hub. therefore they have 2 (or more) mac address, and tydom password.

How could I connect more than 1 Tydom hub? Could I install the same repository twice? (I don't know do it) or, could I add on the yaml file more:

TYDOM_MAC:
TYDOM_IP:
TYDOM_PASSWORD:

Thanks for your ideas.
Gada

Hello,

This morning my docker image got updated by watchtower with latest release this morning and now covers are not longer available in Home Assistant. In fact, the device position_tydom_ got well updated but not the itself.

Logs for the device "Volet_Bureau":
2022-09-04 09:03:37,197 - sensors - INFO - Sensor created / updated : device_id_tydom__Volet_Bureau 1611312665
2022-09-04 09:03:37,197 - sensors - INFO - Sensor created / updated : endpoint_id_tydom__Volet_Bureau 1611312665
2022-09-04 09:03:37,197 - sensors - INFO - Sensor created / updated : id_tydom__Volet_Bureau 1611312665_1611312665
2022-09-04 09:03:37,197 - sensors - INFO - Sensor created / updated : position_tydom__Volet_Bureau 0
2022-09-04 09:03:37,197 - cover - INFO - Cover created / updated : Volet Bureau 1611312665_1611312665

HA Logs for this device:
Exception in async_discover when dispatching 'mqtt_discovery_new_cover_mqtt': ({'name': 'Volet Bureau', 'unique_id': '1611312665_1611312665', 'command_topic': 'cover/tydom/1611312665_1611312665/set_positionCmd', 'set_position_topic': 'cover/tydom/1611312665_1611312665/set_position', 'json_attributes_topic': 'cover/tydom/1611312665_1611312665/attributes', 'payload_open': 'UP', 'payload_close': 'DOWN', 'payload_stop': 'STOP', 'retain': 'false', 'device': {'manufacturer': 'Delta Dore', 'model': 'Volet', 'name': 'Volet Bureau', 'identifiers': '1611312665_1611312665'}, 'platform': 'mqtt'},) Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 272, in call return self._compiled([], data) File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 818, in validate_callable return schema(data) File "/usr/src/homeassistant/homeassistant/components/mqtt/cover.py", line 123, in validate_options raise vol.Invalid( voluptuous.error.Invalid: 'set_position_topic' must be set together with 'position_topic'. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 323, in async_discover config = schema(discovery_payload) File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 232, in call return self._exec((Schema(val) for val in self.validators), v) File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 355, in _exec raise e if self.msg is None else AllInvalid(self.msg, path=path) File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 351, in _exec v = func(v) File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 276, in call raise er.MultipleInvalid([e]) voluptuous.error.MultipleInvalid: 'set_position_topic' must be set together with 'position_topic'.

Here is an extract of the log from the tydom2MQTT
FR : Extrait du fichier journal de tydom2MQTT

2022-07-27 22:53:16,812 - sensors - INFO - Sensor created / updated : device_id_tydom__Chambre_1 1651773567
2022-07-27 22:53:16,815 - sensors - INFO - Sensor created / updated : endpoint_id_tydom__Chambre_1 1651773567
2022-07-27 22:53:16,816 - sensors - INFO - Sensor created / updated : id_tydom__Chambre_1 1651773567_1651773567
2022-07-27 22:53:16,818 - sensors - INFO - Binary sensor created / updated : thermicDefect_tydom__Chambre_1 False
2022-07-27 22:53:16,820 - sensors - INFO - Sensor created / updated : position_tydom__Chambre_1 0
2022-07-27 22:53:16,822 - sensors - INFO - Binary sensor created / updated : onFavPos_tydom__Chambre_1 False
2022-07-27 22:53:16,824 - sensors - INFO - Binary sensor created / updated : obstacleDefect_tydom__Chambre_1 False
2022-07-27 22:53:16,826 - sensors - INFO - Binary sensor created / updated : intrusion_tydom__Chambre_1 False
2022-07-27 22:53:16,827 - sensors - INFO - Binary sensor created / updated : battDefect_tydom__Chambre_1 False
2022-07-27 22:53:16,829 - cover - INFO - Cover created / updated : Chambre 1 1651773567_1651773567 0

But the states are not updated
FR:Les état des variables créées ne sont pas mis à jour

je pense qu'il s'agit d'un problème de décodage de la réponse json .

Merci pour votre aide

Hello since 2.4.0 each time i have to reload or reboot HA, i need to close open my cover because their state is not good.
Some says that they are closed even if they're open, some says they're at 60% open even if all are open.The log seems to tell they're all open.maybe it doesn't update well mqtt.

En utilisant la dernière version du container dans docker-compose, j'obtiens l'erreur suivante :

MQTT connection Error : 'str' object has no attribute 'wrap_bio'

Voici la config de mon docker-compose :

  tydom2mqtt:
    image: fmartinou/tydom2mqtt:latest
    container_name: tydom2mqtt
    restart: unless-stopped
    environment:
      - TYDOM_MAC=00:00:00:00:00:00
      - TYDOM_PASSWORD=XXXXXXXX
      - TYDOM_IP=10.0.0.66
      - MQTT_HOST=mosquitto
      - MQTT_SSL=0

"mosquitto" est le nom du service docker-compose dans lequel tourne le broker mosquitto.
Un ping mosquitto ou ping 10.0.0.66 renvoi bien une reponse.

I have a external temperature sensor directly connected to the Tydom box (without any Calybox). The sensor is shown in the Tydom app, but no entity is created in Home Assistant.

Hello,
in configuration page it's impossible to set a alarm code if it start with a zero

Bonjour, j'utilise HA et cette lib avec mes équipements Delta Dore, tout fonctionne, modules de porte de garage et portail, lumiere extérieures, volets, mais l'alarme j'ai bien le statut, mais je ne parviens pas a la piloter.

je vois bien la commande partir, mais peu etre est-elle mal formatée? le code PIN de l'alarme est bon.

2022-12-19 15:43:07,036 - tydomConnector - INFO - Sending to tydom client..... PUT cdata {"value":"ON","pwd":"1234"}
2022-12-19 15:43:07,043 - tydomMessagehandler - INFO - Incoming data parsed successfully !

Merci pour votre aide

Bonjour,

J'utilise Tydom2mqtt Beta ( https://github.com/mrwiwi/tydom2mqtt )depuis 1 an, pour gérer mon matériel Tydom sous HA, impeccable hormis la porte de garage qui comporte un module Tyxia delta dore non pris en charge.

J'ai essayé de migrer vers tydom2mqtt de fmartinou mais la même configuration ne fonctionne pas je ne m'explique pas les erreur du fichier log si jamais vous avez une idée je suis preneur :)

Merci pour vos lumières :)

2022-09-29 19:28:11,201 - main - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-09-29 19:28:11,201 - main - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-09-29 19:28:11,202 - main - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-09-29 19:28:11,202 - main - INFO - STARTING TYDOM2MQTT
2022-09-29 19:28:11,203 - main - INFO - Detecting environnement......
2022-09-29 19:28:11,203 - main - INFO - /data/options.json detected ! Hassio Addons Environnement : parsing options.json....
2022-09-29 19:28:11,204 - tydomConnector - INFO - Initialising TydomClient Class
2022-09-29 19:28:11,204 - tydomConnector - INFO - Setting local mode context.
2022-09-29 19:28:11,209 - main - INFO - Starting main loop_task
/app/main.py:141: DeprecationWarning: There is no current event loop
loop = asyncio.get_event_loop()
2022-09-29 19:28:11,213 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-09-29 19:28:11,213 - mqtt_client - INFO - Attempting MQTT connection...
2022-09-29 19:28:11,213 - mqtt_client - INFO - MQTT host : localhost
2022-09-29 19:28:11,214 - mqtt_client - INFO - MQTT user : mosquitto_user
2022-09-29 19:28:11,226 - mqtt_client - INFO - MQTT connection Error : Multiple exceptions: [Errno 111] Connect call failed ('127.0.0.1', 1883), [Errno 99] Address not available
2022-09-29 19:28:11,227 - mqtt_client - INFO - MQTT error, restarting in 8s...

HACS ne détecte pas cette nouvelle version?
j'ai essaye de rajouter l'integration via HACS j'obtiens le message :
<Integration fmartinou/tydom2mqtt> Repository structure for 2.3.0 is not compliant

Bonjour,
j'ai installé l'addon sur home assistant.
Configuré avec les bonnes infos mais impossible de sauvegarder
erreur :
Échec de l'enregistrement de la configuration du module complémentaire, not a valid value. Got {'TYDOM_MAC': '001A25XXXXXX', 'TYDOM_IP': '10.0.0.X', 'TYDOM_PASSWORD': 'password', 'TYDOM_ALARM_PIN': 9999, 'TYDOM_ALARM_HOME_ZONE': 1, 'TYDOM_ALARM_NIGHT_ZONE': 2, 'MQTT_HOST': 'localhost', 'MQTT_USER': 'mqtt', 'MQTT_PASSWORD': 'mqtt', 'MQTT_PORT': 1883, 'MQTT_SSL': False, 'log_level': 'info'}

Une idée?

Hello,
I use tydom2mqtt and Home Assistant since several weeks ! It's work fine, thanks for the job.
But I am a problem with my Tywatt 5100, the data insn't collected by tydom2mqtt on HA.

I also have Kline detector for door and windows => works fine, Tywatt 5400 => for Linky consumption : work fine too
I have only probleme with Tywatt 5100

Après installation de cette mise à jour

• l'add-on tydom2mqtt ne fonctionne pas

extrait du journal:

('127.0.0.1', 1883), [Errno 99] Address not available
2022-09-06 15:16:14,977 - mqtt_client - INFO - MQTT error, restarting in 8s...
2022-09-06 15:16:23,000 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-09-06 15:16:23,000 - mqtt_client - INFO - Attempting MQTT connection...
2022-09-06 15:16:23,000 - mqtt_client - INFO - MQTT host : localhost
2022-09-06 15:16:23,000 - mqtt_client - INFO - MQTT user :
2022-09-06 15:16:23,007 - mqtt_client - INFO - MQTT connection Error : Multiple exceptions: [Errno 111] Connect call failed ('127.0.0.1', 1883), [Errno 99] Address not available
2022-09-06 15:16:23,008 - mqtt_client - INFO - MQTT error, restarting in 8s...
2022-09-06 15:16:31,108 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-09-06 15:16:31,114 - mqtt_client - INFO - Attempting MQTT connection...
2022-09-06 15:16:31,114 - mqtt_client - INFO - MQTT host : localhost
2022-09-06 15:16:31,114 - mqtt_client - INFO - MQTT user :
2022-09-06 15:16:31,134 - mqtt_client - INFO - MQTT connection Error : Multiple exceptions: [Errno 111] Connect call failed ('127.0.0.1', 1883), [Errno 99] Address not available
2022-09-06 15:16:31,135 - mqtt_client - INFO - MQTT error, restarting in 8s...

• Les objets ne sont donc plus mis à jour bien qu'ils aient été créés au niveau MQTT

2022-09-06 15:15:54.457 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom device_id_tydom_1651773567_1651773567
2022-09-06 15:15:54.457 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom endpoint_id_tydom_1651773567_1651773567
2022-09-06 15:15:54.457 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom id_tydom_1651773567_1651773567
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom position_tydom_1651773567_1651773567
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom device_id_tydom_1651782167_1651782167
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom endpoint_id_tydom_1651782167_1651782167
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom id_tydom_1651782167_1651782167
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor tydom position_tydom_1651782167_1651782167
2022-09-06 15:15:54.458 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom thermicdefect_tydom_1651773567_1651773567
2022-09-06 15:15:54.459 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom onfavpos_tydom_1651773567_1651773567
2022-09-06 15:15:54.459 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom obstacledefect_tydom_1651773567_1651773567
2022-09-06 15:15:54.459 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom intrusion_tydom_1651773567_1651773567
2022-09-06 15:15:54.459 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom battdefect_tydom_1651773567_1651773567
2022-09-06 15:15:54.505 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom thermicdefect_tydom_1651782167_1651782167
2022-09-06 15:15:54.505 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom onfavpos_tydom_1651782167_1651782167
2022-09-06 15:15:54.505 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom obstacledefect_tydom_1651782167_1651782167
2022-09-06 15:15:54.506 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom intrusion_tydom_1651782167_1651782167
2022-09-06 15:15:54.506 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor tydom battdefect_tydom_1651782167_1651782167

Since a few days i don't receive updates from some energy consumption sensors.

I use a Tydom Home + Tywatt 1000 and I successfully receive update from some sensors like the total energy consumption (sensor.elec_total_tydom_tywatt) and other sensors, but i don't get updates for other sensors such as sensor.elec_heating_tydom_tywatt.

Values corresponding to these sensors are updated in the tydom app, but tydom2mqtt can't seem to read the values.

tydom2mqtt is at version 2.6.2, here is tydom2mqtt log 5 mins after restart:

2022-11-22 08:48:39,688 - __main__ - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-11-22 08:48:39,689 - __main__ - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-11-22 08:48:39,690 - __main__ - INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-11-22 08:48:39,690 - __main__ - INFO - STARTING TYDOM2MQTT
2022-11-22 08:48:39,691 - __main__ - INFO - Detecting environnement......
2022-11-22 08:48:39,691 - __main__ - INFO - /data/options.json detected ! Hassio Addons Environnement : parsing options.json....
2022-11-22 08:48:39,692 - tydomConnector - INFO - Initialising TydomClient Class
2022-11-22 08:48:39,692 - tydomConnector - INFO - Setting local mode context.
2022-11-22 08:48:39,700 - __main__ - INFO - Starting main loop_task
/app/main.py:141: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()
2022-11-22 08:48:39,704 - mqtt_client - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-11-22 08:48:39,705 - mqtt_client - INFO - Attempting MQTT connection...
2022-11-22 08:48:39,705 - mqtt_client - INFO - MQTT host : core-mosquitto
2022-11-22 08:48:39,706 - mqtt_client - INFO - MQTT user : homeassistant
2022-11-22 08:48:39,725 - gmqtt.mqtt.protocol - INFO - [CONNECTION MADE]
2022-11-22 08:48:40,178 - mqtt_client - INFO - ##################################
2022-11-22 08:48:40,179 - mqtt_client - INFO - Subscribing to : +/tydom/#
2022-11-22 08:48:40,179 - gmqtt.mqtt.package - INFO - [SEND SUB] 1 [b'homeassistant/status']
2022-11-22 08:48:40,181 - gmqtt.mqtt.package - INFO - [SEND SUB] 2 [b'+/tydom/#']
2022-11-22 08:48:40,183 - tydomConnector - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-11-22 08:48:40,184 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING....                     
2022-11-22 08:48:40,184 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication....
2022-11-22 08:48:42,653 - tydomConnector - INFO - Upgrading http connection to websocket....
2022-11-22 08:48:42,654 - tydomConnector - INFO - Attempting websocket connection with tydom hub.......................
2022-11-22 08:48:42,655 - tydomConnector - INFO - Host Target : 192.168.1.80
2022-11-22 08:48:42,743 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,)
2022-11-22 08:48:42,744 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,)
2022-11-22 08:48:45,167 - __main__ - INFO - Tydom Client is connected to websocket and ready !
2022-11-22 08:48:45,168 - tydomConnector - INFO - Requesting 1st data...
2022-11-22 08:48:45,168 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /info
2022-11-22 08:48:45,170 - tydomConnector - INFO - ##################################
2022-11-22 08:48:45,170 - tydomConnector - INFO - ##################################
2022-11-22 08:48:45,171 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:48:45,172 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /configs/file
2022-11-22 08:48:45,173 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/cmeta
2022-11-22 08:48:50,249 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/data
2022-11-22 08:48:50,283 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:48:50,331 - tydomMessagehandler - INFO - Configuration updated
2022-11-22 08:48:50,331 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:48:50,334 - tydomMessagehandler - INFO - Metadata configuration updated
2022-11-22 08:48:50,335 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:48:50,337 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:49:32,343 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:49:32,344 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyInstant&unit=ELEC_A&reset=false
2022-11-22 08:49:33,029 - sensors - INFO - Sensor created / updated : ELEC_A_tydom__Tywatt 400
2022-11-22 08:49:33,030 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:50:15,038 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:50:15,039 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyIndex&dest=ELEC_TOTAL&reset=false
2022-11-22 08:50:15,197 - sensors - INFO - Sensor created / updated : ELEC_TOTAL_tydom__Tywatt 722361
2022-11-22 08:50:15,197 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:50:57,201 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:50:57,202 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyIndex&dest=ELEC_COOLING&reset=false
2022-11-22 08:50:57,362 - sensors - INFO - Sensor created / updated : ELEC_COOLING_tydom__Tywatt 0
2022-11-22 08:50:57,364 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:51:39,369 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:51:39,370 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyIndex&dest=ELEC_OUTLET&reset=false
2022-11-22 08:51:39,517 - sensors - INFO - Sensor created / updated : ELEC_OUTLET_tydom__Tywatt 150616
2022-11-22 08:51:39,522 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:52:21,529 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:52:21,529 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyIndex&dest=ELEC_OTHER&reset=false
2022-11-22 08:52:21,677 - sensors - INFO - Sensor created / updated : ELEC_OTHER_tydom__Tywatt 291320
2022-11-22 08:52:21,678 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:53:03,685 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:53:03,687 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyDistrib&period=YEAR&periodOffset=0&src=ELEC
2022-11-22 08:53:03,844 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-22 08:53:45,845 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-11-22 08:53:45,846 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/1664101359/endpoints/1664101359/cdata?name=energyInstant&unit=ELEC_A&reset=false
2022-11-22 08:53:46,515 - sensors - INFO - Sensor created / updated : ELEC_A_tydom__Tywatt 400
2022-11-22 08:53:46,515 - tydomMessagehandler - INFO - Incoming data parsed successfully !

Is it possible to add support for Tywatt ?

I use it with tydom-client and mqtt by hand for now and it works really well (integrated in the new Energy panel!). Only problem is that it needs polling so I don't know if it would be easy for you.

Here is an example of how I use it (no error handling, really quick an dirty and first HA dev so there may be mistakes) :

Discover : mosquitto_pub -r -h 127.0.0.1 -p 1883 -t "homeassistant/sensor/tydom_power_total/config" -m '{"unique_id": "tydom_power_total", "name": "Total consumption", "unit_of_measurement": "Wh", "device_class": "energy", "state_class": "total_increasing", "state_topic": "homeassistant/sensor/tydom_power_total/state"}'

Get data : request /devices/XXXX/endpoints/XXXX/cdata?name=energyIndex&dest=ELEC_TOTAL&reset=false --username USER --password PASS --hostname IP --command

Update : mosquitto_pub -r -h 127.0.0.1 -p 1883 -t "homeassistant/sensor/tydom_power_total/state" -m VALUE

You can replace ELEC_TOTAL with ELEC_HEATING, ELEC_COOLING, ELEC_HOTWATER, ELEC_OUTLET, ELEC_OTHER (you can get the list using request /devices/cmeta)

I don't think energyHisto and energyDistrib commands would be of any use, however energyInstant is interesting (using "unit_of_measurement": "VA", "device_class": "current", "state_class": "measurement").

Thanks for the great software !

Hello,

I am new user of tydom 1.0.

I use your app with docker but i have a problem.

The connexion with MQTT is OK but just after, when it tries to connect to the tydom 1.0 i have an 401 error.

I am sure of the password cause i just entered it on the tydom.

I can"t connect with a browser, user = mac address and password : tydom password.

Is it an update?

Thanks

Bonjour,
Je ne connais pas trop docker. Je suis plutot habituer à faire des installations directement sur mon RPi
Quand je lance "sudo docker-compose up" après avoir configurer mon fichier, le process ne se lance pas et j'ai l'eereur suivante
tydom2mqtt | Traceback (most recent call last):
tydom2mqtt | File "/app/main.py", line 2, in
tydom2mqtt | import asyncio
tydom2mqtt | File "/usr/local/lib/python3.10/asyncio/init.py", line 8, in
tydom2mqtt | from .base_events import *
tydom2mqtt | File "/usr/local/lib/python3.10/asyncio/base_events.py", line 18, in
tydom2mqtt | import concurrent.futures
tydom2mqtt | File "/usr/local/lib/python3.10/concurrent/futures/init.py", line 8, in
tydom2mqtt | from concurrent.futures._base import (FIRST_COMPLETED,
tydom2mqtt | File "/usr/local/lib/python3.10/concurrent/futures/_base.py", line 7, in
tydom2mqtt | import logging
tydom2mqtt | File "/usr/local/lib/python3.10/logging/init.py", line 57, in
tydom2mqtt | _startTime = time.time()
tydom2mqtt | PermissionError: [Errno 1] Operation not permitted

Je suppose que cela vient peut-etre de mon installation deocker

Avez-vous une idée ?

Merci d'avance

PM

Mon fichier config
version: '3'
services:
tydom2mqtt:
image: fmartinou/tydom2mqtt
container_name: tydom2mqtt
environment:
- TYDOM_MAC=001A25xxxxxx
- TYDOM_PASSWORD=
- TYDOM_IP=192.168.x.x
- MQTT_HOST=192.168.y.y
- MQTT_PORT=port
- MQTT_USER=user
- MQTT_PASSWORD=pass

Hello,
there is no link for configuration for home assistant via docker.
is the documentation provided?

Thank you

FRA: Malgré des infructueux de recherche en reverse engineering de APK version 4.xx, mon bur est de pouvoir collecter les différents évènements de l'alarme comme défaut pile, autoprotection ouverture d'issue, alarme déclenché, etc... qu'on pouvait consulter depuis mobile, mais c'est hyper lourd et hyper lent lorsqu'on a pas mal d'entrée.

Connaisseriez-vous une commande équivaut de ce type "GET /devices/{deviceId}/endpoints/{deviceId}" ou autre url qui permet d'interroger les events ? Cela me servira des suivies et des préventifs pour changer des piles.

J'utilise le TYDOM-1 et Delta Pack4...

Merci

ENG : Despite unsuccessful research in reverse engineering of APK on version 4.xx, my goal is to be able to collect some events of the alarm such as battery failure, autoprotection, opening of an issue, alarm triggered, etc... which we could consult from mobile, but it's very heavy and very slow when you have a lot of input.

Do you know an equivalent command of this type "GET /devices/{deviceId}/endpoints/{deviceId}" or other url that allows you to query the events ? This will be to use as follow-ups and preventives for changing batteries.

I use the TYDOM-1 and Delta Pack4...

Thanks

Bonjour tydom2mqtt fonctionne très bien !!!, sauf qu'il est impossible de l'intégrer dans le gestion de l'énergie de home assistance les sensors ne sont pas répertoriées avez-vous une idée du problème cordialement

Hi folks,

I have 1 1/2 year experience with Home Assistant. And some time ago I was able to install the tydom2mqtt addon.

I had to reinstall all my home assistant and the only thing I couldn't get back was my Tydom.

I've been with this for months and it doesn't freak me out. I am asking for some help please.....

This is the error the log gives me:

Hello,
Is it possible to add support for the boost option (fan) of the Eco-Logic with Aterno Recept SDB X3D 868MHZ?

Device information:
{"id_endpoint":xxxyyy,"first_usage":"hvac","skill":"TYDOM_X3D","id_device":xxxyyy,"name":"BathRoom","anticipation_start":false,"space_id":"","picto":"default_device","last_usage":"electric"}],"old_tycam":false,"os":"android","groups":[

Config:

{"id":xxxyyy,"endpoints":[
{"id":xxxyyy,"error":0,"data":[
{"name":"authorization","validity":"upToDate","value":"HEATING"}\r\n39\r\n,
{"name":"setpoint","validity":"upToDate","value":22.000}\r\n3B\r\n,
{"name":"thermicLevel","validity":"upToDate","value":null}\r\n3B\r\n,
{"name":"hvacMode","validity":"upToDate","value":"NORMAL"}\r\n35\r\n,
{"name":"timeDelay","validity":"upToDate","value":0}\r\n3C\r\n,
{"name":"temperature","validity":"upToDate","value":22.140}\r\n37\r\n,
{"name":"tempoOn","validity":"upToDate","value":false}\r\n3B\r\n,
{"name":"antifrostOn","validity":"upToDate","value":false}\r\n3E\r\n,
{"name":"loadSheddingOn","validity":"upToDate","value":false}\r\n3F\r\n,
{"name":"openingDetected","validity":"upToDate","value":false}\r\n40\r\n,
{"name":"presenceDetected","validity":"upToDate","value":false}\r\n37\r\n,
{"name":"absence","validity":"upToDate","value":false}\r\n40\r\n,
{"name":"productionDef', rsv1=False, rsv2=False, rsv3=False)
{"name":"batteryCmdDefect","validity":"upToDate","value":false}\r\n40\r\n,
{"name":"tempSensorDefect","validity":"upToDate","value":false}\r\n42\r\n,
{"name":"tempSensorShortCut","validity":"upToDate","value":false}\r\n42\r\n,
{"name":"tempSensorOpenCirc","validity":"upToDate","value":false}\r\n37\r\n,
{"name":"boostOn","validity":"upToDate","value":false}\r\n40\r\n,
{"name":"anticipCoeff","validity":"upToDate","value":30}]}]}]\r\n\r\n0\r\n\r\n', rsv1=False, rsv2=False, rsv3=False)

Switch on message part:
"data":[{"name":"setpoint","validity":"upToDate","value":20.000}, => real temp setpoint is neglected and always set to 20.0 to activate boost mode
{"name":"tempoOn","validity":"upToDate","value":true}, => change both true/false
{"name":"boostOn","validity":"upToDate","value":true} => change both true/false

Switch off message part:
"data":[{"name":"setpoint","validity":"upToDate","value":22.000}\r\n35\r\n,{"name":"timeDelay","validity":"upToDate","value":0}\r\n37\r\n,{"name":"tempoOn","validity":"upToDate","value":false}\r\n3E\r\n,{"name":"boostOn","validity":"upToDate","value":false}]}]}]\r\n\r\n0\r\n\r\n'

Hi,

I have k-line detectors in my k-line windows.

• classic openings are working fine.
• sliding openings were not detected.

I have made some debug: they seem to be detected as "windowSliding" (and not "klineWindowSliding"), see json below:

      {
         "id_device":1549571289,
         "last_usage":"windowSliding",
         "id_endpoint":1549571289,
         "picto":"picto_detect_window_sliding1",
         "name":"Detector 4",
         "anticipation_start":false,
         "first_usage":"window"
      },

Changing following lines in tydomMessageHandler.py worked on my tests:

line 567:

                            if type_of_id == 'windowFrench' or type_of_id == 'window' or type_of_id == 'klineWindowFrench' or type_of_id == 'klineWindowSliding' or type_of_id == 'windowSliding':

line 402:

            if i["last_usage"] == 'shutter' or i["last_usage"] == 'klineShutter' or i["last_usage"] == 'light' or i["last_usage"] == 'window' or i["last_usage"] == 'windowFrench' or i["last_usage"] == 'windowSliding' or i["last_usage"] == 'belmDoor' or i[

log from test after bugfix:

2022-11-24 03:11:32,791 - tydomMessagehandler - INFO - Incoming data parsed successfully !
2022-11-24 03:11:55,819 - sensors - INFO - Sensor created / updated : openState_tydom__D▒tecteur_4 LOCKED
2022-11-24 03:11:55,819 - tydomMessagehandler - INFO - Incoming data parsed successfully !

Thanks a lot for your work ! Code was interesting and easy to check, especially as I have never developed in Python.

Hi,

I have this error in the homeassistant log. This error happens for all my device_class=door devices.

The doors are from Kline and have a DVI (détecteur de verrouillage intégré) which state is properly reported in HA (LOCKED, UNLOCKED).

2022-10-01 13:19:58.343 ERROR (MainThread) [homeassistant.util.logging] Exception in async_discover when dispatching 'mqtt_discovery_new_sensor_mqtt': ({'name': 'openState_tydom__Porte_patio', 'unique_id': 'openState_tydom_1659982394_1659982394', 'device_class': 'door',                                                                                                                                                                                       
'device': {'manufacturer': 'Delta Dore', 'model': 'Sensor', 'name': 'openState_tydom__Porte_patio', 'identifiers': '1659982394_1659982394_sensors'}, 'state_topic': 'sensor/tydom/openState_tydom_1659982394_1659982394/state', 'platform': 'mqtt'},)      
Traceback (most recent call last):                                                                                                                                                                                                                                                    
  File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 348, in async_discover                                                                                                                                                                                  
    config = discovery_schema(discovery_payload)                                                                                                                                                                                                                                      
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 232, in __call__                                                                                                                                                                                      
    return self._exec((Schema(val) for val in self.validators), v)                                                                                                                                                                                                                    
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 355, in _exec                                                                                                                                                                                         
    raise e if self.msg is None else AllInvalid(self.msg, path=path)                                                                                                                                                                                                                  
  File "/usr/local/lib/python3.10/site-packages/voluptuous/validators.py", line 351, in _exec                                                                                                                                                                                         
    v = func(v)                                                                                                                                                                                                                                                                       
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 272, in __call__                                                                                                                                                                                  
    return self._compiled([], data)                                                                                                                                                                                                                                                   
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 818, in validate_callable                                                                                                                                                                         
    return schema(data)                                                                                                                                                                                                                                                               
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 272, in __call__                                                                                                                                                                                  
    return self._compiled([], data)                                                                                                                                                                                                                                                   
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict                                                                                                                                                                             
    return base_validate(path, iteritems(data), out)                                                                                                                                                                                                                                  
  File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 433, in validate_mapping                                                                                                                                                                          
    raise er.MultipleInvalid(errors)                                                                                                                                                                                                                                                  
voluptuous.error.MultipleInvalid: expected SensorDeviceClass or one of 'apparent_power', 'aqi', 'battery', 'carbon_monoxide', 'carbon_dioxide', 'current', 'date', 'duration', 'energy', 'frequency', 'gas', 'humidity', 'illuminance', 'monetary', 'nitrogen_dioxide',                                                                                                                                                                                              
 'nitrogen_monoxide', 'nitrous_oxide', 'ozone', 'pm1', 'pm10', 'pm25', 'power_factor', 'power', 'pressure', 'reactive_power', 'signal_strength', 'sulphur_dioxide', 'temperature', 'timestamp', 'volatile_organic_compounds', 'voltage' for dictionary value @ data['device_class']                                                                                                                                                                                  

Sunshades can be opened and closed like cover but they also can be oriented (example)

How can we add support for this ?

Hi,

Like many , many , many , many people I had to reinit the password to make it work correctly. To reinit I used the local button on the box and then I use an old version of the app on android (v3+ as recommended in FAQ). As I don't have an android device I have used an android emulator (This NOX portable version).

I use the tydom2mqtt Home Assistant Addon. MQTT discovery has done his job, I have a lot of tydom sensors in HA.
So I have some questions about the add-on in Home Assistant :

1. By default HA create 2 button for the alarm. So what is the difference between : "Arm away" and "Arm Home" ? Is it really applicable to Tydom alarm ?
2. I really can't use my motion detectors in Home Assistant ?
3. What is this "cdata message" for motion detectors ? Is it an xml sent to MQTT ? Can we use it in HA (to have a presence history for example ) ?
4. Is the parameter "TYDOM_ALARM_PIN" really useful to make the add-on working ?
5. I would prefer to type it manually on a pinpad directly in Home Assistant UI. I see that it is possible to add a pinpad in HA so is it possible to send the typed pinpad to the tydom alarm (to avoid to put it in configuration file) ?

Some remarks :

• Little problem on the add-on : if you don't specify a TYDOM_ALARM_PIN , it is set by default to "9999" which crash the add-on at start (it seems it require 6 characters)
• May be a filter / additional parameters in the add-on could be useful to expose only what we need.

Thanks for the great work on this add-on !

EN:

Hello,

I have a small problem with the add-on.
My devices are correctly recognized, and the values seem to be correctly read in the logs.
However, my devices in Home Assistant are not updated; they have as state value "unknow".

Can you help me?

FR:

Bonjour,

J'ai un petit problème avec l'addon.
Mes équipement Delta Dore sont correctement reconnus, et les valeurs semblent être correctement lues dans le journal de l'add-on.
Cependant, mes appareils dans Home Assistant ne sont pas mis à jour et ont pour valeur d'etat "inconnue"

Pouvez-vous m'aider ?

Hi,

for an unknown reason, the add-on restarts every night between 2:30am and 3:30am.

The restart fails with the following error:

2022-10-04 03:15:07,181 - tydomConnector - INFO - Host Target : mediation.tydom.com
2022-10-04 03:15:07,285 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,)
2022-10-04 03:15:07,288 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,)
2022-10-04 03:15:07,416 - __main__ - INFO - Tydom Client is connected to websocket and ready !
2022-10-04 03:15:07,420 - tydomConnector - INFO - Requesting 1st data...
2022-10-04 03:15:07,423 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /info
2022-10-04 03:15:07,430 - tydomConnector - INFO - ##################################
2022-10-04 03:15:07,434 - tydomConnector - INFO - ##################################
2022-10-04 03:15:07,437 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-10-04 03:15:07,442 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /configs/file
2022-10-04 03:15:07,447 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/cmeta
2022-10-04 03:15:12,458 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/data
Traceback (most recent call last):
  File "/app/main.py", line 226, in <module>
    loop_task()
  File "/app/main.py", line 148, in loop_task
    loop.run_until_complete(listen_tydom_forever(tydom_client))
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/app/main.py", line 162, in listen_tydom_forever
    await tydom_client.setup()
  File "/app/tydomConnector.py", line 438, in setup
    await self.get_data()
  File "/app/tydomConnector.py", line 409, in get_data
    await self.get_devices_data()
  File "/app/tydomConnector.py", line 386, in get_devices_data
    await self.send_message(method=req, msg=msg_type)
  File "/app/tydomConnector.py", line 243, in send_message
    await self.connection.send(a_bytes)
  File "/usr/local/lib/python3.10/site-packages/websockets/legacy/protocol.py", line 620, in send
    await self.ensure_open()
  File "/usr/local/lib/python3.10/site-packages/websockets/legacy/protocol.py", line 921, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: received 4001 (private use) Tydom non connecté.; then sent 4001 (private use) Tydom non connecté.

After that,
Manually restarting the add-on does not fix the problem.
Rebooting the HAss virtual machine does not fix the problem.
Restarting TYDOM box does fix the problem until the next night at around 2:00am when it happens again.

There is no particular message at that moment in home-assistant.log

If you tell me how to collect more logs for mqtt2tydom, I will give you more logs (as currently I only see the restart phase in the add-on log page. I don't see the event that that triggered the restart).

Hello,

Thank you very much for your great effort.

I've been with home Assitant for a one year and the only thing I haven't been able to integrate is Tydom. It's very frustrating.

To integrate tydom in home assistant there are 2 pieces, the mosquitto broker and the tydom2mqtt.

I don't know which one is failing. I'll pass you the configuration of my tydom2mqtt and the log to see if it helps.

In red the altered values ​​but that are good

Thanks a lot

L'addon ne démarre plus. le journal ne s'affiche pas. Comment revenir a la version précédente?

Hi!

As envisioned in the FAQ, the new versions of Tydom uses some cloud login with an account to retrieve the site list and log to them.

Would it be an interesting feature to have in this utility?

Happy to contribute it!

Hi,

I'm trying to configure my tydom2mqtt but I have a problem with mine:

2022-05-26 22:16:26,120 - mqtt_client - INFO - """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 2022-05-26 22:16:26,121 - mqtt_client - INFO - Attempting MQTT connection... 2022-05-26 22:16:26,121 - mqtt_client - INFO - MQTT host : 192.168.1.100 2022-05-26 22:16:26,121 - mqtt_client - INFO - MQTT user : mqtt 2022-05-26 22:16:26,122 - gmqtt.mqtt.protocol - INFO - [CONNECTION MADE] 2022-05-26 22:16:26,124 - mqtt_client - INFO - ################################## 2022-05-26 22:16:26,124 - mqtt_client - INFO - Subscribing to : +/tydom/# 2022-05-26 22:16:26,124 - gmqtt.mqtt.package - INFO - [SEND SUB] 1 [b'homeassistant/status'] 2022-05-26 22:16:26,125 - gmqtt.mqtt.package - INFO - [SEND SUB] 2 [b'+/tydom/#'] 2022-05-26 22:16:26,125 - tydomConnector - INFO - """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 2022-05-26 22:16:26,125 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING.... 2022-05-26 22:16:26,125 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication.... 2022-05-26 22:16:27,245 - tydomConnector - INFO - Upgrading http connection to websocket.... 2022-05-26 22:16:27,245 - tydomConnector - INFO - Attempting websocket connection with tydom hub....................... 2022-05-26 22:16:27,245 - tydomConnector - INFO - Host Target : 192.168.1.101 2022-05-26 22:16:27,274 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,) 2022-05-26 22:16:27,275 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,) 2022-05-26 22:16:28,415 - tydomConnector - ERROR - Exception when trying to connect with websocket ! 2022-05-26 22:16:28,415 - tydomConnector - ERROR - server rejected WebSocket connection: HTTP 401

Hello,
With a fresh and up to date version of Home Assistant, I can't start latest version of tydom2mqtt
Here my log

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
STARTING TYDOM2MQTT
Detecting environnement......
/data/options.json detected ! Hassio Addons Environnement : parsing options.json....
{'TYDOM_MAC': '001A25xxxxxx', 'TYDOM_IP': '192.168.1.xx', 'TYDOM_PASSWORD': 'xx', 'TYDOM_ALARM_PIN': '9999', 'TYDOM_ALARM_HOME_ZONE': 1, 'TYDOM_ALARM_NIGHT_ZONE': 2, 'MQTT_HOST': 'xx', 'MQTT_USER': 'x', x'MQTT_PASSWORD': 'xx', 'MQTT_PORT': 1883, 'MQTT_SSL': False, 'log_level': 'trace'}
Initialising TydomClient Class
Setting local mode context.
Starting main loop_task
/app/main.py:119: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Attempting MQTT connection...
MQTT host :  homeassistant
MQTT user :  xx
##################################
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.xx
Exception when trying to connect with websocket !
did not receive a valid HTTP response
wss://192.168.1.xx:443/mediation/client?mac=001A25xxxxxx&appli=1
{'Authorization': 'Digest username="001A25xxxxxx", realm="protected area", nonce="xxxx", uri="/mediation/client?mac=001A25xxxxxx&appli=1", response="xxx", qop="auth", nc=00000001, cnonce="xxx"'}

As you can see 2 issues

/app/main.py:119: DeprecationWarning: There is no current event loop
  loop = asyncio.get_event_loop()

And the main one the "did not receive a valid HTTP response"
I had revert my phone app to an old version to change my Tydom password to a short one but same beheviour

Bonjour,
D’abord très beaux travail.

J'ai installé tydomMQTT et le plugin marche très bien
Je souhaite incorporer les capteurs contacteurs de porte mais je n'arrive pas a les récupérer sous HA
comment peut on faire

merci pour l'aide futur

cordialement
tristan

For boiler (actually Heat pump) the step resolution is 1°C in HA but in fact in tydom app it is 0.5 °C.
If it's set with tydom app it's stay to 0.5°C and can be seen in HA with the good value.

I didn't find where it's set in the app? I'm missing something?

I've been trying to get this running for my local install, and ran into an issue: WWW-Authenticate was not present in the headers returned.

As the code tries to split a NoneType, it then fails and ends. I have found however, that replacing the nonce with an empty string everywhere seems to result in everything running—and the real test is that both of my radiators show in Home Assistant through my MQTT broker and can be controlled (though the temperature sensor on one of them is off by about 10°C).

Sadly I have little to no experience with websockets or the consequences that replacing this with an empty string could have, but thought I should open an issue with an offer to help debug as much as I am able to.

I use some cover and the tydom2mqtt version 2.6.2
sometimes the attributes position and current-position from cover.xxx are not updated so that it's impossible to manage them by the entity cover.xxx.
The way to recover the right behavior is to move manually with the Tydom application or to create a button that make a movement...

In the integration the data are updated only if they change, I think that it should be better to update them at each time they are read.

in my exemple, the shutter is physically closed
entities:

• label: Volet Chambre rdc
  type: section
• entity: cover.chambre_1 position = 100
• entity: cover.chambre_1
  type: attribute
  attribute: position value = -
  name: position
• entity: cover.chambre_1
  type: attribute
  attribute: current_position value = 100
  name: position courante
• label: Sensor position
  type: section
• sensor.position_tydom_chambre_1 = 0

It should be also nice to have the general attributes from cover like opening, closing is_closed is_opened

Bonjour, voici les dernieres lignes du log :
2022-06-11 22:49:00,140 - mqtt_client - INFO - """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 2022-06-11 22:49:00,141 - mqtt_client - INFO - Attempting MQTT connection... 2022-06-11 22:49:00,141 - mqtt_client - INFO - MQTT host : 10.0.0.34 2022-06-11 22:49:00,141 - mqtt_client - INFO - MQTT user : mqtt 2022-06-11 22:49:00,142 - gmqtt.mqtt.protocol - INFO - [CONNECTION MADE] 2022-06-11 22:49:00,142 - mqtt_client - INFO - ################################## 2022-06-11 22:49:00,143 - mqtt_client - INFO - Subscribing to : +/tydom/# 2022-06-11 22:49:00,143 - gmqtt.mqtt.package - INFO - [SEND SUB] 1 [b'homeassistant/status'] 2022-06-11 22:49:00,143 - gmqtt.mqtt.package - INFO - [SEND SUB] 2 [b'+/tydom/#'] 2022-06-11 22:49:00,143 - tydomConnector - INFO - """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 2022-06-11 22:49:00,144 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING.... 2022-06-11 22:49:00,144 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication.... Traceback (most recent call last): File "/app/main.py", line 226, in <module> loop_task() File "/app/main.py", line 148, in loop_task loop.run_until_complete(listen_tydom_forever(tydom_client)) File "/usr/local/lib/python3.10/asyncio/base_events.py", line 641, in run_until_complete return future.result() File "/app/main.py", line 160, in listen_tydom_forever await tydom_client.connect() File "/app/tydomConnector.py", line 106, in connect conn.request( File "/usr/local/lib/python3.10/http/client.py", line 1282, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1328, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1277, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/local/lib/python3.10/http/client.py", line 1037, in _send_output self.send(msg) File "/usr/local/lib/python3.10/http/client.py", line 975, in send self.connect() File "/usr/local/lib/python3.10/http/client.py", line 1454, in connect self.sock = self._context.wrap_socket(self.sock, File "/usr/local/lib/python3.10/ssl.py", line 512, in wrap_socket return self.sslsocket_class._create( File "/usr/local/lib/python3.10/ssl.py", line 1070, in _create self.do_handshake() File "/usr/local/lib/python3.10/ssl.py", line 1341, in do_handshake self._sslobj.do_handshake() ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:997)

Hi

I would like to connect a second hand tydom 1.0 to home assistant to control tyxia 5610 lights and related wireless switches.

Do tout know if this hardware will work and be available and controllable in HA?

Thank you for your work

Some interesting values such as the out temperature or the GSM level are part of the alarm attributes, so they are not updated regularly.

So if I create sensors based on these attributes, I cannot use them.

Is there a way to get more regular updates? I was thinking about calling the endpoint that returns all information every x minutes for example.