tydom2mqtt
tydom2mqtt copied to clipboard
fmartinou
Tydom error
2023-03-26 11:53:14,115 - mqtt.MqttClient - INFO - Connecting to mqtt broker (host=192.168.1.72, port=1883, user=mqqqt, ssl=False) 2023-03-26 11:53:14,120 - tydom.TydomClient - INFO - Connecting to tydom 2023-03-26 11:53:14,328 - tydom.TydomClient - DEBUG - Response headers 2023-03-26 11:53:14,330 - tydom.TydomClient - DEBUG - X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: 0 X-Frame-Options: DENY Set-Cookie: JSESSIONID=51B38025636C0C5DA00C5EA1E4B9B826;path=/;HttpOnly WWW-Authenticate: Digest realm="ServiceMedia", qop="auth", nonce="MTY3OTgyNDY5NDMxODozYmYzMThmYWQ1NDA1ODEyOGU0Yzc0NTI3MmE4Yjc0YQ==" Content-Length: 0 Date: Sun, 26 Mar 2023 09:53:13 GMT 2023-03-26 11:53:14,388 - tydom.TydomClient - DEBUG - Response code 2023-03-26 11:53:14,389 - tydom.TydomClient - DEBUG - 401 2023-03-26 11:53:14,389 - tydom.TydomClient - DEBUG - response 2023-03-26 11:53:14,390 - tydom.TydomClient - DEBUG - b'' 2023-03-26 11:53:14,391 - tydom.TydomClient - DEBUG - Upgrading http connection to websocket.... 2023-03-26 11:53:14,392 - tydom.TydomClient - DEBUG - Attempting websocket connection with Tydom hub 2023-03-26 11:53:14,666 - gmqtt.mqtt.protocol - INFO - [CONNECTION MADE] 2023-03-26 11:53:14,698 - websockets.client - DEBUG - = connection is CONNECTING 2023-03-26 11:53:14,747 - websockets.client - DEBUG - > GET /mediation/client?mac=001A25020082&appli=1 HTTP/1.1 2023-03-26 11:53:14,747 - websockets.client - DEBUG - > Host: mediation.tydom.com 2023-03-26 11:53:14,747 - websockets.client - DEBUG - > Upgrade: websocket 2023-03-26 11:53:14,748 - websockets.client - DEBUG - > Connection: Upgrade 2023-03-26 11:53:14,749 - websockets.client - DEBUG - > Sec-WebSocket-Key: mtMZ5M6qDedBIQirPyp8pQ== 2023-03-26 11:53:14,749 - websockets.client - DEBUG - > Sec-WebSocket-Version: 13 2023-03-26 11:53:14,750 - websockets.client - DEBUG - > Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits 2023-03-26 11:53:14,750 - websockets.client - DEBUG - > Authorization: Digest username="001A25020082", realm="ServiceMedia", nonce="MTY3OTgyNDY5NDMxODozYmYzMThmYWQ1NDA1ODEyOGU0Yzc0NTI3MmE4Yjc0YQ==", uri="/mediation/client?mac=001A25020082&appli=1", response="a2714029beab2baf6f51a246a615977b", qop="auth", nc=00000001, cnonce="75dd924d579dcf0c" 2023-03-26 11:53:14,751 - websockets.client - DEBUG - > User-Agent: Python/3.11 websockets/10.4 2023-03-26 11:53:14,794 - websockets.client - DEBUG - < HTTP/1.1 101 2023-03-26 11:53:14,794 - websockets.client - DEBUG - < X-Content-Type-Options: nosniff 2023-03-26 11:53:14,795 - websockets.client - DEBUG - < X-XSS-Protection: 1; mode=block 2023-03-26 11:53:14,796 - websockets.client - DEBUG - < Cache-Control: no-cache, no-store, max-age=0, must-revalidate 2023-03-26 11:53:14,797 - websockets.client - DEBUG - < Pragma: no-cache 2023-03-26 11:53:14,797 - websockets.client - DEBUG - < Expires: 0 2023-03-26 11:53:14,798 - websockets.client - DEBUG - < X-Frame-Options: DENY 2023-03-26 11:53:14,799 - websockets.client - DEBUG - < Set-Cookie: JSESSIONID=2BE74AFCE869D9CDED4C5E18B8DC3B71;path=/;HttpOnly 2023-03-26 11:53:14,799 - websockets.client - DEBUG - < Upgrade: websocket 2023-03-26 11:53:14,800 - websockets.client - DEBUG - < Connection: upgrade 2023-03-26 11:53:14,800 - websockets.client - DEBUG - < Sec-WebSocket-Accept: uIE0NZpFsZ/IvtCTfIydFFydtOU= 2023-03-26 11:53:14,801 - websockets.client - DEBUG - < Sec-WebSocket-Extensions: permessage-deflate;client_max_window_bits=15 2023-03-26 11:53:14,801 - websockets.client - DEBUG - < Date: Sun, 26 Mar 2023 09:53:13 GMT 2023-03-26 11:53:14,803 - websockets.client - DEBUG - = connection is OPEN 2023-03-26 11:53:14,804 - tydom.TydomClient - INFO - Connected to tydom 2023-03-26 11:53:14,805 - tydom.TydomClient - INFO - Setup tydom client 2023-03-26 11:53:14,805 - tydom.TydomClient - DEBUG - Sending message to tydom (GET /info) 2023-03-26 11:53:14,806 - websockets.client - DEBUG - > BINARY 02 47 45 54 20 2f 69 6e 66 6f 20 48 54 54 50 2f ... 64 3a 20 30 0d 0a 0d 0a [104 bytes] 2023-03-26 11:53:14,808 - tydom.TydomClient - DEBUG - Sending message to tydom (POST /refresh/all) 2023-03-26 11:53:14,809 - websockets.client - DEBUG - > BINARY 02 50 4f 53 54 20 2f 72 65 66 72 65 73 68 2f 61 ... 64 3a 20 30 0d 0a 0d 0a [112 bytes] 2023-03-26 11:53:14,811 - tydom.TydomClient - DEBUG - Sending message to tydom (GET /configs/file) 2023-03-26 11:53:14,812 - websockets.client - DEBUG - > BINARY 02 47 45 54 20 2f 63 6f 6e 66 69 67 73 2f 66 69 ... 64 3a 20 30 0d 0a 0d 0a [112 bytes] 2023-03-26 11:53:14,814 - tydom.TydomClient - DEBUG - Sending message to tydom (GET /devices/cmeta) 2023-03-26 11:53:14,815 - websockets.client - DEBUG - > BINARY 02 47 45 54 20 2f 64 65 76 69 63 65 73 2f 63 6d ... 64 3a 20 30 0d 0a 0d 0a [113 bytes] 2023-03-26 11:53:14,817 - tydom.TydomClient - DEBUG - Sending message to tydom (GET /devices/data) 2023-03-26 11:53:14,818 - websockets.client - DEBUG - > BINARY 02 47 45 54 20 2f 64 65 76 69 63 65 73 2f 64 61 ... 64 3a 20 30 0d 0a 0d 0a [112 bytes] 2023-03-26 11:53:15,012 - websockets.client - DEBUG - < BINARY 02 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b ... 7d 0d 0a 30 0d 0a 0d 0a [1815 bytes] 2023-03-26 11:53:15,014 - websockets.client - DEBUG - < BINARY 02 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b ... 64 3a 20 30 0d 0a 0d 0a [140 bytes] 2023-03-26 11:53:15,017 - tydom.MessageHandler - DEBUG - Message received detected as (msg_info) 2023-03-26 11:53:15,017 - tydom.MessageHandler - DEBUG - Incoming data parsed with success 2023-03-26 11:53:15,076 - websockets.client - DEBUG - < BINARY 02 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b ... 72 6b 73 22 3a 5b 5d 7d [1371 bytes] 2023-03-26 11:53:15,077 - websockets.client - DEBUG - < BINARY 02 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b ... 0a 0d 0a 30 0d 0a 0d 0a [321 bytes] 2023-03-26 11:53:15,078 - websockets.client - DEBUG - < BINARY 02 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b ... 0a 0d 0a 30 0d 0a 0d 0a [1635 bytes] 2023-03-26 11:53:15,081 - tydom.MessageHandler - DEBUG - Message received detected as (msg_config) 2023-03-26 11:53:15,082 - tydom.MessageHandler - DEBUG - Configuration updated 2023-03-26 11:53:15,082 - tydom.MessageHandler - DEBUG - Incoming data parsed with success 2023-03-26 11:53:15,084 - tydom.MessageHandler - DEBUG - Message received detected as (msg_cmetadata) 2023-03-26 11:53:15,085 - tydom.MessageHandler - DEBUG - Metadata configuration updated 2023-03-26 11:53:15,085 - tydom.MessageHandler - DEBUG - Incoming data parsed with success 2023-03-26 11:53:15,087 - tydom.MessageHandler - DEBUG - Message received detected as (msg_data) 2023-03-26 11:53:15,088 - tydom.MessageHandler - INFO - Device update (id=1645988476, endpoint=1645988476, name=Chauffage 1, type=boiler) 2023-03-26 11:53:15,089 - tydom.MessageHandler - ERROR - Error on parsing tydom response ('NoneType' object has no attribute 'publish') 2023-03-26 11:53:15,091 - tydom.MessageHandler - DEBUG - Incoming data parsed with success 2023-03-26 11:53:15,775 - gmqtt.mqtt.handler - DEBUG - [CMD 0x20] b'\x00\x00\x06"\x00\n!\x00\x14' 2023-03-26 11:53:15,777 - gmqtt.mqtt.handler - DEBUG - [CONNACK] flags: 0x0, result: 0x0 2023-03-26 11:53:15,777 - mqtt.MqttClient - DEBUG - Subscribing to topics (+/tydom/#) 2023-03-26 11:53:15,779 - gmqtt.mqtt.utils - DEBUG - NEW ID: 1 2023-03-26 11:53:15,780 - gmqtt.mqtt.package - INFO - [SEND SUB] 1 [b'homeassistant/status'] 2023-03-26 11:53:15,781 - gmqtt.mqtt.utils - DEBUG - NEW ID: 2 2023-03-26 11:53:15,782 - gmqtt.mqtt.package - INFO - [SEND SUB] 2 [b'+/tydom/#'] 2023-03-26 11:53:15,784 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:15,784 - mqtt.MqttClient - INFO - Connected to mqtt broker 2023-03-26 11:53:15,844 - websockets.client - DEBUG - < BINARY 02 50 55 54 20 2f 64 65 76 69 63 65 73 2f 64 61 ... 0a 0d 0a 30 0d 0a 0d 0a [262 bytes] 2023-03-26 11:53:15,845 - tydom.MessageHandler - DEBUG - PUT /devices/data message detected ! 2023-03-26 11:53:15,847 - tydom.MessageHandler - DEBUG - Message received detected as (msg_data) 2023-03-26 11:53:15,848 - tydom.MessageHandler - INFO - Device update (id=1645988476, endpoint=1645988476, name=Chauffage 1, type=boiler) 2023-03-26 11:53:15,849 - gmqtt.mqtt.package - DEBUG - Sending PUBLISH (q0), 'b'homeassistant/climate/tydom/1645988476_1645988476/config'', ... (695 bytes) 2023-03-26 11:53:15,851 - gmqtt.mqtt.package - DEBUG - Sending PUBLISH (q0), 'b'climate/tydom/1645988476_1645988476/temperature'', ... (5 bytes) 2023-03-26 11:53:15,852 - tydom.MessageHandler - DEBUG - Incoming data parsed with success 2023-03-26 11:53:16,025 - gmqtt.mqtt.handler - DEBUG - [CMD 0x90] b'\x00\x01\x00\x00' 2023-03-26 11:53:16,026 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,) 2023-03-26 11:53:16,027 - gmqtt.mqtt.utils - DEBUG - FREE MID: 1 2023-03-26 11:53:16,066 - gmqtt.mqtt.handler - DEBUG - [CMD 0x90] b'\x00\x02\x00\x00' 2023-03-26 11:53:16,067 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,) 2023-03-26 11:53:16,068 - gmqtt.mqtt.utils - DEBUG - FREE MID: 2 2023-03-26 11:53:16,068 - gmqtt.mqtt.handler - DEBUG - [CMD 0x30] b'\x00/climate/tydom/1645988476_1645988476/temperature\x0021.27' 2023-03-26 11:53:16,069 - gmqtt.mqtt.handler - DEBUG - [RECV climate/tydom/1645988476_1645988476/temperature with QoS: 0] b'\x0021.27' 2023-03-26 11:53:16,070 - gmqtt.mqtt.utils - DEBUG - FREE MID: None 2023-03-26 11:53:20,790 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:25,797 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:30,804 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:34,810 - websockets.client - DEBUG - % sending keepalive ping 2023-03-26 11:53:34,811 - websockets.client - DEBUG - > PING b0 20 b7 0a [binary, 4 bytes] 2023-03-26 11:53:34,839 - websockets.client - DEBUG - < PONG b0 20 b7 0a [binary, 4 bytes] 2023-03-26 11:53:35,807 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:40,814 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:45,817 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:50,825 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:53:54,818 - websockets.client - DEBUG - % sending keepalive ping 2023-03-26 11:53:54,820 - websockets.client - DEBUG - > PING ae 53 4f 61 [binary, 4 bytes] 2023-03-26 11:53:54,873 - websockets.client - DEBUG - < PONG ae 53 4f 61 [binary, 4 bytes] 2023-03-26 11:53:55,829 - gmqtt.client - DEBUG - [QoS query IS EMPTY] 2023-03-26 11:54:00,832 - gmqtt.client - DEBUG - [QoS query IS EMPTY]
2023-03-26 01:56:26,199 - main - WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
For information I use Home Assistant OS all my devices are connected on the same network in ethernet I opened the ports requested
How to solve this problem? 2023-03-26 01:56:26,199 - main - WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
How to solve this problem? 2023-03-26 01:56:26,199 - main - WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
I have the same problem. WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
Sometimes it works and the temperature gets set and highlighted back in a black font, sometimes it fails and the temperature stays highlighted in red. I'm using the local ip address of my tydom v1. Any ideas? I have already updated to the latest version. All versions in the past have had the problem where I'm not always 100% sure if the temperature will be set or not. Sometimes it works and sometimes it fails.
How to solve this problem? 2023-03-26 01:56:26,199 - main - WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
I have the same problem. WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK)
Sometimes it works and the temperature gets set and highlighted back in a black font, sometimes it fails and the temperature stays highlighted in red. I'm using the local ip address of my tydom v1. Any ideas? I have already updated to the latest version. All versions in the past have had the problem where I'm not always 100% sure if the temperature will be set or not. Sometimes it works and sometimes it fails.
@Shadorlo @KeepYourITUp I fix this issue by replacing "mediation.tydom.com" by my local IP adress. it didn't work before, but now it's ok.
Hi, Thanks for the suggestion but the configuration was already set to the local ip. I tried both the local ip and mediation.tydom.com but it still gives the same error.
I get the errors below: WARNING - Unable to handle message: received 1000 (OK); then sent 1000 (OK) WARNING - Unable to handle message: no close frame received or sent
Any idea? When I restart the Tydom add-on it usually works again for x minutes/hours.