tydom2MQTT addon :D - Delta Dore Tydom to MQTT Broker

Third party integrations
473

Hi
I ve just installed tydom2mqtt to my homeassistant
i had setup my tydom mac, password, ip
i had started tydom2mqtt and i have this error

STARTING TYDOM2MQTT
Dectecting environnement......
/data/options.json detected ! Hassio Addons Environnement : parsing options.json....
{'TYDOM_MAC': '001A2505E9E7', 'TYDOM_IP': '192.168.1.31', 'TYDOM_PASSWORD': 'C', 'TYDOM_ALARM_PIN': 123456, 'TYDOM_ALARM_HOME_ZONE': 1, 'TYDOM_ALARM_NIGHT_ZONE': 2, 'MQTT_HOST': 'localhost', 'MQTT_USER': 'umqtt', 'MQTT_PASSWORD': 'pass4UMQTT', '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 :  umqtt
##################################
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.31
Exception when trying to connect with websocket !
server rejected WebSocket connection: HTTP 401
wss://192.168.1.31:443/mediation/client?mac=001A2505E9E7&appli=1
{'Authorization': 'Digest username="001A2505E9E7", realm="protected area", nonce="ec174b76c6d0701efedf06106bba926a", uri="/mediation/client?mac=001A2505E9E7&appli=1", response="7d55c2783ad2ea79bebe081084f40244", qop="auth", nc=00000001, cnonce="187cb2c6ffc3aaf7"'}

I saw that tydom2mqtt is able to be connected to tydom v1.
I think i have tydom v4.
Is it compatible ?
thx

474

As I had some misery myself, I have documented my troubleshooting process. It has not yet bin integrated in the official project on GitHub (PR is still pending) but, in the mean time, you can access my documentation from my GitHub. It may help.

475

Thanks @dominig ,

Your troubleshooting process has been integrated to the original doc :+1:

See here

476

Hi @fmartinou have you got some news about tywatt? we cant use your plugin, can you try to approuve this issue ? Probleme Entites Tywatt · Issue #88 · fmartinou/tydom2mqtt · GitHub
thanks :slight_smile:

477

Hi @robinoux ,

Do you mean this PR?

If so, it has been merged this morning.
(it’s still unreleased though)

478

Oui, merci, du coup il faut attendre la prochaine release? elle sort quand? merci

479

English please, I use tydom2mqtt too and I don’t speak French.

480

Hi,
Your post is from 11/2022 but I try.
I’m facing the exact same problem where HA try to send TOGGLE when ON or OFF seems to be needed by my Delta Dore module. Where did you edit the file to change TOGGLE by ON and OFF?

Thanks,

481

in sensors/Switch.py , replace the payload TOGGLE
I’ve replaced the addon version by a docker version to make this change.
It works like a charm for me even I still cannot get the status of the garage door with tydom. ( I’ve added a simple zigbee sensor for that )

482

Hi,

Thanks a lot for your answer. I will try with the docker version, but I need to redeploy Ha to a regular distro, im using HAOS and it seems that it can not play with external container :frowning_face:

483

I’m using HAOS as well. You just need the MQTT integration on HAOS. But that’s it. Tydom2mqtt can be anywhere.

484

I finally find an other work around. Instead off editing the python file inside docker I create a new cover entity using configuration.yaml

mqtt:
  cover:
    - unique_id: porte_garage
      name: "Porte du Garage"
      command_topic: "switch/tydom/1707845294_1707845294/set_levelCmdGate"
      payload_open: "ON"
      payload_close: "OFF"
      optimistic: false
      qos: 0
      retain: true

I didn’t find any topic that give me the door state, so I will also probably order at least a zigbee sensor to manage this point.

The problem comes from how mqtt detect the door module (available in debug of MQTT Device):

Garage (switch.product_1_2)
MQTT discovery data:
Topic: homeassistant/switch/tydom/1707845294_1707845294/config
Payload
name: null
unique_id: '1707845294_1707845294'
command_topic: switch/tydom/1707845294_1707845294/set_levelCmdGate
state_topic: switch/tydom/1707845294_1707845294/state
json_attributes_topic: switch/tydom/1707845294_1707845294/attributes
payload_on: TOGGLE
payload_off: TOGGLE
retain: 'false'
device:
  manufacturer: Delta Dore
  model: Porte
  name: Garage
  identifiers: '1707845294_1707845294'
platform: mqtt

Not perfect but it works.

Thanks again for your help

485

Yep. Good point. I’ve had some progress by manually playing with the sent commands but I was not successfull with the configuration.yaml . It’s now a long time ago. My goal was also trying to do some partial opening like the tydom app. I’ve failed. ON and OFF is ok but if the garage door is already opening or closing . It can be unsuccessfull. That’s where the additionnal sensor is usefull. The detection as a switch of the garage door module is weird and it’s probably a part of the problem why we can’t do a partial opening but I don’t have the knowledge to fix that.

486

On my side on tydom app I can only open or close the door and check the status (closed or opened) there is no other option. My goal now is to find the correct state topic, if we can get the state on tydom, it should be possible to get it in ha with mqtt. Im going to try to find it with a ssl proxy to decrypt what is going on between my phone app and the tydom box.

487

Hello

I would like to know if someone has managed to activate the alarm using this addon.
I’m using an old tyxal CSX40 alarm and nothing changes when I activate the alarm on Home Assistant.
here is the log:

2024-03-02 01:33:36,433 - mqtt.MqttClient - INFO - set_alarm_state message received (topic=alarm_control_panel/tydom/1612289388_1612289388/set_alarm_state, message=ARM_AWAY)
2024-03-02 01:33:36,433 - tydom.TydomClient - DEBUG - Sending message to tydom ({“value”:“ON”,“pwd”:“1234”}) PUT cdata
2024-03-02 01:33:36,434 - websockets.client - DEBUG - > BINARY 50 55 54 20 2f 64 65 76 69 63 65 73 2f 31 36 31 … 33 34 22 7d 0d 0a 0d 0a [190 bytes]
2024-03-02 01:33:36,440 - websockets.client - DEBUG - < BINARY 48 54 54 50 2f 31 2e 31 20 35 30 30 20 49 6e 74 … 0a 0d 0a 30 0d 0a 0d 0a [352 bytes]
2024-03-02 01:33:36,442 - tydom.MessageHandler - DEBUG - Message received detected as (msg_html)
2024-03-02 01:33:36,442 - tydom.MessageHandler - DEBUG - HTML Response ?
2024-03-02 01:33:36,442 - tydom.MessageHandler - DEBUG - Incoming data parsed with success
2024-03-02 01:33:40,683 - gmqtt.client - DEBUG - [QoS query IS EMPTY]

488

Hello,
How to create lights or Cover automatisations with Tydom2MQTT. I try BluePrints, NodeRed but the services cover.close_cover, cover.open_cover, light.turn_on, … doesn’t work.
Someone has got a working example ?

Thx
DjGogo2000

489

Hello, I’m new to Home Assistant, and I saw that there was a Tydom extension which made me happy (a little less after reading the 427 comments xD)

I have just had a house built, and it is equipped with home automation from Deltador including the following products:

  • Tywell PRO
  • 14 Integrated Lock Detector for my windows
  • 2 door lock detectors
  • Tywell Outdoor Pack (sunlight and outdoor temperature sensor)
  • 8 Tymoove Radio RP2 roller shutters
  • 1x Typass ATL (Receiver for the Atlantic Aflea Duo heat pump)
  • 2 Tywell Control (Indoor thermostats)
  • Tyxal+ pack for the alarm

Currently, I have configured the installation with the Tydom application in Professional mode (installer) I have not yet validated the installation to have it on my user account.

Do you think that @fmartinou tydom2mqtt community extension is fully compatible with all my devices?

And how I can help contribute to the improvement of this extension (log feedback, testing etc. on my devices)

Thank you, and big thanks to @fmartinou for his contribution to the community.

490

I have windows and door lock detectors, roller shutters and typass ATL which are working for me

1 Like
492

Hello @fmartinou , I propose a change request to manage the garage doors as a cover and not a switch and I also add the garage_door_horizontal that was not managed.
It works well on my side :slight_smile:

image

493

All done for me, this work fine :slight_smile:

But not for my lock door :frowning:

How did you configure it ?

My logs say :

2024-03-17 18:47:29,037 - tydom.MessageHandler - WARNING - Unknown device name (1710070598_1710070598)
2024-03-17 18:47:29,038 - tydom.MessageHandler - WARNING - Unknown device type (1710070598_1710070598)

Unknown device name & Unknown device type

I think this is TYSENSE SUN & TEMPERATURE :

Because i don’t see nothing about this on my MQTT.

On MQTT i have this:

image
image1664×730 46 KB

image
image1028×783 50.5 KB

All “Mosquitto Broker” are my door look

How can i define type of object or define template for this one etc ?

Can i change openState to status for exemple ? Like this, with map_attribute or something like that ?
image

I don’t found where i can define object template