Bonsoir
Bon j'arrive pas a installer python3.7
j'ai testé avec python3.8 mais j'ai une erreur
je pense que mon soucis c'est que je suis en version BullEye
root@voiceassiste:/usr/bin# cat /etc/*release*
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
Tu peux me dire si tu es en bullEye ou Buster ? cat /etc/*release* ?
merci d'avance
Delta Dore X2D/X3D (Tydom)
Re: Delta Dore X2D/X3D (Tydom)
re-bonsoir
Je viens de reinstaller une version buster avec un python 3.7
mais j'ai une erreur Syntax error ?
root@raspberrypi:~/Tydom# python -V
Python 3.7.3
root@raspberrypi:~/Tydom# ./manage_tydom.sh
File "/root/Tydom/main.py", line 191
async def send_message(websocket, msg):
^
SyntaxError: invalid syntax
root@raspberrypi:~/Tydom#
root@raspberrypi:~/Tydom#
root@raspberrypi:~/Tydom# cat /etc/*release*
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Merci de ton aide
cordialement
Je viens de reinstaller une version buster avec un python 3.7
mais j'ai une erreur Syntax error ?
root@raspberrypi:~/Tydom# python -V
Python 3.7.3
root@raspberrypi:~/Tydom# ./manage_tydom.sh
File "/root/Tydom/main.py", line 191
async def send_message(websocket, msg):
^
SyntaxError: invalid syntax
root@raspberrypi:~/Tydom#
root@raspberrypi:~/Tydom#
root@raspberrypi:~/Tydom# cat /etc/*release*
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Merci de ton aide
cordialement
Re: Delta Dore X2D/X3D (Tydom)
Bonjour
Je viens de m'apercevoir qu'il existe une Tydom V1.0 et une Tydom Home
Moi j'ai la Tydom Home (voir photo)
Est ce que ton api est compatible avec la Tydom Home ?
Mes derniers tests !
root@raspberrypi:~/Tydom# root@raspberrypi:~/Tydom# python3 -E main.py get_devices_meta
DEB - Action : get_devices_meta
DEB - id : not set
DEB - value : not set
DEBUG:websockets.client:= connection is CONNECTING
DEBUG:websockets.client:> GET /mediation/client?mac=00:1A:25:05:E9:E7&appli=1 HTTP/1.1
DEBUG:websockets.client:> Host: 192.168.1.31
DEBUG:websockets.client:> Upgrade: websocket
DEBUG:websockets.client:> Connection: Upgrade
DEBUG:websockets.client:> Sec-WebSocket-Key: 9zQBnt/KHRiTAiwI+VnWWw==
DEBUG:websockets.client:> Sec-WebSocket-Version: 13
DEBUG:websockets.client:> Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
DEBUG:websockets.client:> Authorization: Digest username="00:1A:25:05:E9:E7", realm="protected area", nonce="b254ce1fd233a71b12765facf2a33333", uri="/mediation/client?mac=00:1A:25:05:E9:E7&appli=1", response="6278c78ed38b6f60877a3ba99725f560", qop="auth", nc=00000001, cnonce="c02de746ecd646e3"
DEBUG:websockets.client:> User-Agent: Python/3.7 websockets/10.3
DEBUG:websockets.client:< HTTP/1.1 401 Unauthorized
DEBUG:websockets.client:< Connection: close
DEBUG:websockets.client:< WWW-Authenticate: Digest realm="Protected Area", qop="auth", nonce="45e513a084ba97f3331fe1a40371ba3f", opaque="e736fdb9cbfe560313d9b45298846622"
DEBUG:websockets.client:< Content-Type: text/html
DEBUG:websockets.client:! failing connection with code 1006
DEBUG:websockets.client:x closing TCP connection
ERROR:asyncio:SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x75882e30>
transport: <_SelectorSocketTransport fd=6 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
self._sslobj.unwrap()
File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
DEBUG:websockets.client:= connection is CLOSED
Traceback (most recent call last):
File "main.py", line 375, in <module>
asyncio.get_event_loop().run_until_complete(main_task())
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "main.py", line 308, in main_task
extra_headers=websocketHeaders, ssl=websocket_ssl_context) as websocket:
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 633, in __aenter__
return await self
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 650, in __await_impl_timeout__
return await asyncio.wait_for(self.__await_impl__(), self.open_timeout)
File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 663, in __await_impl__
extra_headers=protocol.extra_headers,
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 328, in handshake
raise InvalidStatusCode(status_code, response_headers)
websockets.exceptions.InvalidStatusCode: server rejected WebSocket connection: HTTP 401
Pourtant en 192.168.1.31 j'ai bien le tydom home (voir photo)
Merci
Je viens de m'apercevoir qu'il existe une Tydom V1.0 et une Tydom Home
Moi j'ai la Tydom Home (voir photo)
Est ce que ton api est compatible avec la Tydom Home ?
Mes derniers tests !
root@raspberrypi:~/Tydom# root@raspberrypi:~/Tydom# python3 -E main.py get_devices_meta
DEB - Action : get_devices_meta
DEB - id : not set
DEB - value : not set
DEBUG:websockets.client:= connection is CONNECTING
DEBUG:websockets.client:> GET /mediation/client?mac=00:1A:25:05:E9:E7&appli=1 HTTP/1.1
DEBUG:websockets.client:> Host: 192.168.1.31
DEBUG:websockets.client:> Upgrade: websocket
DEBUG:websockets.client:> Connection: Upgrade
DEBUG:websockets.client:> Sec-WebSocket-Key: 9zQBnt/KHRiTAiwI+VnWWw==
DEBUG:websockets.client:> Sec-WebSocket-Version: 13
DEBUG:websockets.client:> Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
DEBUG:websockets.client:> Authorization: Digest username="00:1A:25:05:E9:E7", realm="protected area", nonce="b254ce1fd233a71b12765facf2a33333", uri="/mediation/client?mac=00:1A:25:05:E9:E7&appli=1", response="6278c78ed38b6f60877a3ba99725f560", qop="auth", nc=00000001, cnonce="c02de746ecd646e3"
DEBUG:websockets.client:> User-Agent: Python/3.7 websockets/10.3
DEBUG:websockets.client:< HTTP/1.1 401 Unauthorized
DEBUG:websockets.client:< Connection: close
DEBUG:websockets.client:< WWW-Authenticate: Digest realm="Protected Area", qop="auth", nonce="45e513a084ba97f3331fe1a40371ba3f", opaque="e736fdb9cbfe560313d9b45298846622"
DEBUG:websockets.client:< Content-Type: text/html
DEBUG:websockets.client:! failing connection with code 1006
DEBUG:websockets.client:x closing TCP connection
ERROR:asyncio:SSL error in data received
protocol: <asyncio.sslproto.SSLProtocol object at 0x75882e30>
transport: <_SelectorSocketTransport fd=6 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata
self._sslobj.unwrap()
File "/usr/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)
DEBUG:websockets.client:= connection is CLOSED
Traceback (most recent call last):
File "main.py", line 375, in <module>
asyncio.get_event_loop().run_until_complete(main_task())
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "main.py", line 308, in main_task
extra_headers=websocketHeaders, ssl=websocket_ssl_context) as websocket:
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 633, in __aenter__
return await self
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 650, in __await_impl_timeout__
return await asyncio.wait_for(self.__await_impl__(), self.open_timeout)
File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 663, in __await_impl__
extra_headers=protocol.extra_headers,
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/client.py", line 328, in handshake
raise InvalidStatusCode(status_code, response_headers)
websockets.exceptions.InvalidStatusCode: server rejected WebSocket connection: HTTP 401
Pourtant en 192.168.1.31 j'ai bien le tydom home (voir photo)
Merci
- Fichiers joints
-
- tydomHOME.PNG (40.6 Kio) Vu 449 fois
-
- face arriere
- 20220524_143550.jpg (1.1 Mio) Vu 450 fois
-
- face avant
- 20220524_143545.jpg (2.26 Mio) Vu 450 fois
Re: Delta Dore X2D/X3D (Tydom)
Bonjour Zatow,
As-tu trouvé la solution? J'ai le même souci!
As-tu trouvé la solution? J'ai le même souci!
Zatow a écrit : ↑10 nov. 2021, 01:27 Bonjour à tous,
Le TYDOM semble maintenant lié à un compte DeltaDore, je n'ai pas la possibilité de récuéprer le mot de passe de mon TYDOM :
Quand je fais la manipulation pour faire un reset du password, il me donne directement accès au TYDOM sans changer de mot de passe..
Est-ce que cela vous parle ?
Merci.