I will try to help then and submit a PR then. Thanks a lot for keeping this OSS project alive.
Hi guys.
I’m still getting the http error when starting up the tydom2mqtt. Any ideas what I need to do? Any help would be really appreciated.
Thanks.
Which http error ? Is it a new and fresh installation ?
Hello.
I am also a new user and I also get an HTTP error.
Blockquote
parse error: Expected string key before ‘:’ at line 1, column 4
[09:33:17] ERROR: Unknown HTTP error occured
Blockquote
I still get the temperature info but all the alarm info are not working.
Any suggestions
[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
[09:33:17] ERROR: Unknown HTTP error occured
System: (armv7 / raspberrypi3)
Home Assistant Core: 2021.10.6
Home Assistant Supervisor: 2021.10.8
-----------------------------------------------------------
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 TRACE
[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
To all new users : could you please restart the inital process with an old tydom app (from 2020 for example), the new onboarding seems to change some things…
I don’t see the error (“blockquote”) ?
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
[09:33:17] ERROR: Unknown HTTP error occured
System: (armv7 / raspberrypi3)
Home Assistant Core: 2021.10.6
Home Assistant Supervisor: 2021.10.8
the error is not “blockquote”, that was just me trying to isolate the line where the error appear.
The error is "
parse error: Expected string key before ':' at line 1, column 4
[09:33:17] ERROR: Unknown HTTP error occured
"
I do not understand your request to use a old tydom app. How do you do that?
Download an old version of the tydom app for the initial onboiarding ! (Old APK))
I don’t think the http error is the cause of the alarm issues… I think you could ignore it, try to arm / disarm while connecting to check if you have more data !
I just get this in log and nothing else?
TYDOM WEBSOCKET CONNECTION INITIALISING…
Building headers, getting 1st handshake and authentication…
Traceback (most recent call last):
File “/opt/tydom2mqtt/main.py”, line 159, in
loop_task()
File “/opt/tydom2mqtt/main.py”, line 103, in loop_task
loop.run_until_complete(listen_tydom_forever(tydom_client))
File “/usr/lib/python3.8/asyncio/base_events.py”, line 616, in run_until_complete
return future.result()
File “/opt/tydom2mqtt/main.py”, line 115, in listen_tydom_forever
await tydom_client.connect()
File “/opt/tydom2mqtt/tydomConnector.py”, line 96, in connect
conn.request(“GET”, “/mediation/client?mac={}&appli=1”.format(self.mac), None, httpHeaders)
File “/usr/lib/python3.8/http/client.py”, line 1252, in request
self._send_request(method, url, body, headers, encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1298, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1247, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1007, in _send_output
self.send(msg)
File “/usr/lib/python3.8/http/client.py”, line 947, in send
self.connect()
File “/usr/lib/python3.8/http/client.py”, line 1414, in connect
super().connect()
File “/usr/lib/python3.8/http/client.py”, line 918, in connect
self.sock = self._create_connection(
File “/usr/lib/python3.8/socket.py”, line 808, in create_connection
raise err
File “/usr/lib/python3.8/socket.py”, line 796, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out
Starting /opt/tydom2mqtt/main.py
This the Log for the MQTT Mosquitto i have running to. Any help would really be appreciated.
1637859244: Client 0d3f33ad-tydom2mqtt-hassio2021-11-25 16:52:33.655949 has exceeded timeout, disconnecting.
1637859262: New connection from 172.30.32.2 on port 1883.
1637859262: Socket error on client , disconnecting.
1637859286: New connection from 192.168.0.111 on port 1883.
1637859286: New client connected from 192.168.0.111 as 0d3f33ad-tydom2mqtt-hassio2021-11-25 16:54:46.769110 (p5, c1, k60, u’homeassistant’).
Hi all, please migrate to the fork by @fmartinou : (all new updates will be push to this repository now)
1 Like
[Solved]
Hi mates,
I read the entire tread but I don’t find anything related to this.
I tried to install this add-on in two different Home Assistants (one with Docker, other as Hassio) and in both I’ve an error on mqtt authentification.
This is from the log of tydom2mqtt add-on
Attempting MQTT connection…
MQTT host : homeassistant
MQTT user :
[CONNACK] 0x87
MQTT connection Error : code 135 (Connection Refused: Not authorized)
MQTT error, restarting in 8s…
MQTT Disconnected !
##################################
Did you face up this issue? I’d the installation of mqtt since more than 2 years without this issue.
Thanks in advance
[Solution]
After play around I just set the mqtt user and password from the HA user created for mosquitto
Weird because in others add-ons using mqtt I never had to do it. Now seems is connected.
Now the issue is the websocket issue people is having. I will try to do the onboarding of the tydom from the old apk.
I will keep updating.
Thanks!
Hi, thanks for this great add-on !
This is a copy of my feedback on this github issue to have more visibility to the community 
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 :
- 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 ?
- I really can’t use my motion detectors in Home Assistant ?
- 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 ) ?
- Is the parameter “TYDOM_ALARM_PIN” really useful to make the add-on working ?
- 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 !
1 Like
Interested also by your 5 bullet points @schmurtz !!!
I would like to add the monitoring of door sensor as the DO BL to know if my door is open or not.
I fixed this in a recent PR, so that should be solved now!
Can we have any motion detector activity and door sensor status ??
It would be a great enhancement !
Also can we have the info of who desarmed the alarm? I have a push notif saying the alarm have been disarmed, but i want to know who did it. I will know when my children are at home.
It seems this application for homebridge is providing relevant data : https://github.com/mgcrea/node-tydom-client
I can see in live motion detection or door opening by executing the command line below :
npx tydom-client listen --username 001A25XXXXXX --password XXXXXX
motionDetect or intrusionDetect switch from false to true instantely.
Does anyone have an idea how to grab theses data to home assistant or to integrate theses functions in the tydom add-on of @fmartinou ?
Hello,
I just migrated my tydom2mqtt add-on from mrwiwi’s Github repository to fmartinou’s.
I saw in the 2.0.1 changelog “Fix sensor type for windows giving status (OPEN, CLOSE, OPEN_HOPPER) and Fix wrong binary_sensor type in some cases”
But my window and door sensors are not reporting correctly on HA. However when an opening is detected it appears in the logs of tydom2MQTT
2022-03-05 10:46:02,751 - sensors - INFO - Binary sensor created / updated: intrusionDetect_tydom__Bureau True
2022-03-05 10:46:02,751 - tydomMessagehandler - INFO - Incoming data parsed successfully!
2022-03-05 10:46:27,151 - sensors - INFO - Binary sensor created / updated: intrusionDetect_tydom__Bureau False
2022-03-05 10:46:27,151 - tydomMessagehandler - INFO - Incoming data parsed successfully!
If I want the sensors to work correctly I have to add this kind of lines in configuration.yaml
binary_sensor:
- platform: mqtt
name: Bureau
state_topic: "binary_sensor/tydom/intrusionDetect_tydom_1616951540_1616951540/state"
payload_on: true
payload_off: false
device_class: windows
My sensors are correctly configured as a window or door on the Tydom application
My lovelace card :
Is it possible to improve the automatic integration of sensors so that “device_class” is up to date?
Thanks for your work!