tydom2mqtt icon indicating copy to clipboard operation
tydom2mqtt copied to clipboard

Tydrom2mqtt crashes the Tydom 1.0

Open Izlud opened this issue 2 years ago • 3 comments

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

Izlud avatar Oct 12 '22 09:10 Izlud

I have sported this warning in the logs, if it can help 2022-10-12 16:51:48,282 - cover - INFO - Cover created / updated : Bureau 1651354688_1651354688 2022-10-12 16:51:48,282 - tydomMessagehandler - INFO - Incoming data parsed successfully ! 2022-10-12 16:51:50,470 - tydomMessagehandler - WARNING - Didn't detect incoming type, here it is : 2022-10-12 16:51:50,471 - tydomMessagehandler - WARNING - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2022-10-12 16:51:50,471 - tydomMessagehandler - WARNING - RAW INCOMING : 2022-10-12 16:51:50,471 - tydomMessagehandler - WARNING - b'\x02\x18\x01\x01\x04\x00\x00\x00\x00\x08\xbb\xfah\x80\x05\x98\x008\xff\x01\x00\x10\x01\xfbW' 2022-10-12 16:51:50,471 - tydomMessagehandler - WARNING - END RAW 2022-10-12 16:51:50,471 - tydomMessagehandler - WARNING - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2022-10-12 16:52:32,474 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all

2022-10-12 17:12:56,014 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all 2022-10-12 17:12:56,014 - main - ERROR - TimeoutError or websocket error - retrying connection in %s seconds... 2022-10-12 17:12:56,014 - main - ERROR - Error: received 1000 (OK); then sent 1000 (OK) 2022-10-12 17:12:58,017 - tydomConnector - INFO - """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 2022-10-12 17:12:58,017 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING.... 2022-10-12 17:12:58,017 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication.... 2022-10-12 17:12:58,107 - tydomConnector - INFO - Upgrading http connection to websocket.... 2022-10-12 17:12:58,107 - tydomConnector - INFO - Attempting websocket connection with tydom hub....................... 2022-10-12 17:12:58,107 - tydomConnector - INFO - Host Target : mediation.tydom.com 2022-10-12 17:12:58,187 - main - INFO - Tydom Client is connected to websocket and ready !

Izlud avatar Oct 12 '22 16:10 Izlud

Is it the same issue as in #46 ?

arnodu avatar Nov 20 '22 22:11 arnodu

Hi, I have the same problem with the Tydom PRO. Tydom PRO crash a few minutes after the Tydom2mqtt (docker version on rasperypi 4) start Normaly the Tydom LED is off but when it's crashed the LED bright slowly orange to white. There is not error on log just that:

2024-01-07 15:22:23,006 - main - ERROR - Websocket connection closed: received 1000 (OK); then sent 1000 (OK) 2024-01-07 15:24:13,481 - tydom.MessageHandler - WARNING - Unknown message type received ([] ) 2024-01-07 15:25:13,501 - main - ERROR - Websocket connection closed: received 1000 (OK); then sent 1000 (OK) 2024-01-07 15:27:11,866 - tydom.MessageHandler - WARNING - Unknown message type received ([] ) 2024-01-07 15:28:11,875 - main - ERROR - Websocket connection closed: received 1000 (OK); then sent 1000 (OK) 2024-01-07 15:30:08,536 - tydom.MessageHandler - WARNING - Unknown message type received ([]

May be there is to much connection per minutes and then the box block all connection... i don't know. I am going to test with full log message

frnicolas avatar Jan 08 '24 16:01 frnicolas