Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

集成“gree2”不再提供此实体。如果实体不再使用，可以在“设置”中删除它。？求助大佬指点 #51

Open
ptaoo opened this issue Jul 31, 2024 · 6 comments
Open

集成“gree2”不再提供此实体。如果实体不再使用，可以在“设置”中删除它。？求助大佬指点 #51

ptaoo opened this issue Jul 31, 2024 · 6 comments

Comments

@ptaoo
Copy link

ptaoo commented Jul 31, 2024 •
edited
Loading

image
image

date | stream | content -- | -- | -- 2024/07/31 14:54:02 | stdout | �[36m2024-07-31 06:54:02.343 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:54:01 | stdout | �[36m2024-07-31 06:54:01.796 DEBUG (SyncWorker_33) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:54:01 | stdout | �[32m2024-07-31 06:54:01.796 INFO (SyncWorker_33) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:53:41 | stdout | �[36m2024-07-31 06:53:41.795 DEBUG (SyncWorker_17) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:53:41 | stdout | �[32m2024-07-31 06:53:41.795 INFO (SyncWorker_17) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:53:32 | stdout | �[36m2024-07-31 06:53:32.313 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:53:21 | stdout | �[36m2024-07-31 06:53:21.794 DEBUG (SyncWorker_45) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:53:21 | stdout | �[32m2024-07-31 06:53:21.794 INFO (SyncWorker_45) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:53:02 | stdout | �[36m2024-07-31 06:53:02.283 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:53:01 | stdout | �[36m2024-07-31 06:53:01.792 DEBUG (SyncWorker_37) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:53:01 | stdout | �[32m2024-07-31 06:53:01.792 INFO (SyncWorker_37) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:52:41 | stdout | �[36m2024-07-31 06:52:41.790 DEBUG (SyncWorker_10) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:52:41 | stdout | �[32m2024-07-31 06:52:41.790 INFO (SyncWorker_10) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:52:32 | stdout | �[36m2024-07-31 06:52:32.253 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:52:21 | stdout | �[36m2024-07-31 06:52:21.789 DEBUG (SyncWorker_63) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:52:21 | stdout | �[32m2024-07-31 06:52:21.789 INFO (SyncWorker_63) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:52:02 | stdout | �[36m2024-07-31 06:52:02.227 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:52:01 | stdout | �[36m2024-07-31 06:52:01.788 DEBUG (SyncWorker_52) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:52:01 | stdout | �[32m2024-07-31 06:52:01.788 INFO (SyncWorker_52) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:51:41 | stdout | �[36m2024-07-31 06:51:41.788 DEBUG (SyncWorker_32) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:51:41 | stdout | �[32m2024-07-31 06:51:41.787 INFO (SyncWorker_32) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:51:32 | stdout | �[36m2024-07-31 06:51:32.198 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:51:21 | stdout | �[36m2024-07-31 06:51:21.786 DEBUG (SyncWorker_58) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:51:21 | stdout | �[32m2024-07-31 06:51:21.786 INFO (SyncWorker_58) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:51:02 | stdout | �[36m2024-07-31 06:51:02.160 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:51:01 | stdout | �[36m2024-07-31 06:51:01.785 DEBUG (SyncWorker_43) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:51:01 | stdout | �[32m2024-07-31 06:51:01.785 INFO (SyncWorker_43) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:50:41 | stdout | �[36m2024-07-31 06:50:41.782 DEBUG (SyncWorker_21) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:50:41 | stdout | �[32m2024-07-31 06:50:41.782 INFO (SyncWorker_21) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:50:32 | stdout | �[36m2024-07-31 06:50:32.130 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:50:21 | stdout | �[36m2024-07-31 06:50:21.782 DEBUG (SyncWorker_2) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:50:21 | stdout | �[32m2024-07-31 06:50:21.782 INFO (SyncWorker_2) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:50:02 | stdout | �[36m2024-07-31 06:50:02.102 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:50:02 | stdout | �[36m2024-07-31 06:50:02.033 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Socket timeout reset count :3�[0m 2024/07/31 14:50:02 | stdout | �[36m2024-07-31 06:50:02.033 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Fake socket received error: timed out�[0m 2024/07/31 14:50:01 | stdout | �[36m2024-07-31 06:50:01.780 DEBUG (SyncWorker_33) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:50:01 | stdout | �[32m2024-07-31 06:50:01.780 INFO (SyncWorker_33) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:49:41 | stdout | �[36m2024-07-31 06:49:41.779 DEBUG (SyncWorker_44) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:49:41 | stdout | �[32m2024-07-31 06:49:41.779 INFO (SyncWorker_44) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:49:32 | stdout | �[36m2024-07-31 06:49:32.082 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:49:21 | stdout | �[36m2024-07-31 06:49:21.778 DEBUG (SyncWorker_12) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:49:21 | stdout | �[32m2024-07-31 06:49:21.778 INFO (SyncWorker_12) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:49:02 | stdout | �[36m2024-07-31 06:49:02.055 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:49:01 | stdout | �[36m2024-07-31 06:49:01.972 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Socket timeout reset count :2�[0m 2024/07/31 14:49:01 | stdout | �[36m2024-07-31 06:49:01.972 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Fake socket received error: timed out�[0m 2024/07/31 14:49:01 | stdout | �[36m2024-07-31 06:49:01.777 DEBUG (SyncWorker_18) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:49:01 | stdout | �[32m2024-07-31 06:49:01.777 INFO (SyncWorker_18) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:48:41 | stdout | �[36m2024-07-31 06:48:41.776 DEBUG (SyncWorker_44) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:48:41 | stdout | �[32m2024-07-31 06:48:41.776 INFO (SyncWorker_44) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:48:32 | stdout | �[36m2024-07-31 06:48:32.025 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:48:21 | stdout | �[36m2024-07-31 06:48:21.774 DEBUG (SyncWorker_9) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:48:21 | stdout | �[32m2024-07-31 06:48:21.774 INFO (SyncWorker_9) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:48:01 | stdout | �[36m2024-07-31 06:48:01.998 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:48:01 | stdout | �[36m2024-07-31 06:48:01.914 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Socket timeout reset count :1�[0m 2024/07/31 14:48:01 | stdout | �[36m2024-07-31 06:48:01.913 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Fake socket received error: timed out�[0m 2024/07/31 14:48:01 | stdout | �[36m2024-07-31 06:48:01.773 DEBUG (SyncWorker_32) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:48:01 | stdout | �[32m2024-07-31 06:48:01.773 INFO (SyncWorker_32) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:47:41 | stdout | �[36m2024-07-31 06:47:41.771 DEBUG (SyncWorker_48) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:47:41 | stdout | �[32m2024-07-31 06:47:41.771 INFO (SyncWorker_48) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:47:31 | stdout | �[36m2024-07-31 06:47:31.967 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:47:21 | stdout | �[36m2024-07-31 06:47:21.769 DEBUG (SyncWorker_6) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:47:21 | stdout | �[32m2024-07-31 06:47:21.769 INFO (SyncWorker_6) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:47:01 | stdout | �[36m2024-07-31 06:47:01.955 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:47:01 | stdout | �[36m2024-07-31 06:47:01.873 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Socket timeout reset count :0�[0m 2024/07/31 14:47:01 | stdout | �[36m2024-07-31 06:47:01.873 DEBUG (Thread-3 (fake_listen)) [custom_components.gree2.bridge] Fake socket received error: timed out�[0m 2024/07/31 14:47:01 | stdout | �[36m2024-07-31 06:47:01.768 DEBUG (SyncWorker_4) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:47:01 | stdout | �[32m2024-07-31 06:47:01.768 INFO (SyncWorker_4) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:46:41 | stdout | �[36m2024-07-31 06:46:41.767 DEBUG (SyncWorker_23) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:46:41 | stdout | �[32m2024-07-31 06:46:41.767 INFO (SyncWorker_23) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:46:31 | stdout | �[36m2024-07-31 06:46:31.927 DEBUG (Thread-2 (device_listen)) [custom_components.gree2.bridge] Device socket received error: timed out�[0m 2024/07/31 14:46:21 | stdout | �[36m2024-07-31 06:46:21.766 DEBUG (SyncWorker_8) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:46:21 | stdout | �[32m2024-07-31 06:46:21.766 INFO (SyncWorker_8) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:46:01 | stdout | �[36m2024-07-31 06:46:01.765 DEBUG (MainThread) [custom_components.gree2.bridge] device socket send data {'t': 'scan'} to 192.168.31.23�[0m 2024/07/31 14:46:01 | stdout | �[32m2024-07-31 06:46:01.765 INFO (MainThread) [custom_components.gree2.bridge] scan_broadcast�[0m 2024/07/31 14:46:01 | stdout | �[32m2024-07-31 06:46:01.754 INFO (MainThread) [custom_components.gree2.climate] Setting up Gree climate platform�[0m 2024/07/31 14:46:00 | stdout | �[33m2024-07-31 06:46:00.002 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration gree2 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant�[0m 2024/07/31 14:30:21 | stdout | File "/config/custom_components/gree2/climate.py", line 45, in async_setup_platform
@ptaoo
Copy link
Author

ptaoo commented Jul 31, 2024

日志，配置文件，界面都有

@xcy1231
Copy link
Owner

xcy1231 commented Aug 6, 2024

日志貌似有些错乱，大概也可以看出来云控没有任何响应
1.确定云控ip正确
2.确定ha能访问到云控ip
3.确定云控没有处于死机状态，格力+app可以控制，如果不行最好重置云控
4.还有问题尝试开启fake_server，这时候格力+app就无法再控制云控了

@CplusHua
Copy link

CplusHua commented Aug 16, 2024 •
edited
Loading

日志貌似有些错乱，大概也可以看出来云控没有任何响应 1.确定云控ip正确 2.确定ha能访问到云控ip 3.确定云控没有处于死机状态，格力+app可以控制，如果不行最好重置云控 4.还有问题尝试开启fake_server，这时候格力+app就无法再控制云控了

我没有开启fake_server的情况下，在HA重启后不响应的情况发生后，尝试使用电脑（与HA不是同一个局域网IP）重新发送 {"t":"scan"}，仍然能够响应并返回数据，此时重启HA之后又能连接了。说明可能云控没有关闭udp服务，只是需要先做scan之后才能响应。

 def scan_host():
    s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
    s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
    s.bind(('192.168.1.10', 0))
    while True:
        s.sendto(b'{"t": "scan"}', ('192.168.1.255', 7000))
        print('send broadcast')
        time.sleep(1)
        # 接收局域网信息
        data, addr = s.recvfrom(1024)
        print(addr, data)

{
  "t": "pack",
  "i": 1,
  "uid": 0,
  "cid": "<device's MAC address, e.g. 00123456789a>",
  "tcid": "",
  "pack": "<base64 encoded, encrypted data>"
}

('192.168.1.133', 7000) b'{"t":"pack","cid":"xxx","tcid":"app","uid":0,"i":1,"pack":"xxx"}\n'

如果以上情况可行，可以考虑在不使用fake_server的情况下增加scan，来降低断线率。（仅供参考，非需求，感谢作者的代码，已经很好用了）

测试云控：3代（方盒，4线插口款）
固件版本：WiFi模块 V1.13 云控 V1.2  
中央空调（3台）

@xcy1231
Copy link
Owner

xcy1231 commented Aug 19, 2024

scan是一直再重试的，日志里有体现啊，你的云控ip应该是192.168.1.133，但是你上面host填的是192.168.31.23是有过改动么？填错的话scan应该是直接发往这个错误ip，而不是走广播的方式，这样HA应该就连不了啊，我有些不理解你的场景了

@CplusHua
Copy link

scan是一直再重试的，日志里有体现啊，你的云控ip应该是192.168.1.133，但是你上面host填的是192.168.31.23是有过改动么？填错的话scan应该是直接发往这个错误ip，而不是走广播的方式，这样HA应该就连不了啊，我有些不理解你的场景了

我不是issue提出者，跟他的场景可能不太一样。

我读了README中提到的会有认为死机不响应的情况发生，此时也会出现找不到实体的问题。所以回复到了这里。

我不确定scan是否必须发给广播地址，他才能响应。 直接发送给目的IP的话，会不会出现不响应的情况。

但是我一直没有重启HA的情况下，控制一直可用（从上一次恢复当前issue到现在，一直可用）。

另外，不响应是不是忘记配置dhcp对该mac地址固定分配IP，导致分配的IP地址发生变化，所以无法通信？

@xcy1231
Copy link
Owner

xcy1231 commented Aug 22, 2024

scan是一直再重试的，日志里有体现啊，你的云控ip应该是192.168.1.133，但是你上面host填的是192.168.31.23是有过改动么？填错的话scan应该是直接发往这个错误ip，而不是走广播的方式，这样HA应该就连不了啊，我有些不理解你的场景了

我不是issue提出者，跟他的场景可能不太一样。

我读了README中提到的会有认为死机不响应的情况发生，此时也会出现找不到实体的问题。所以回复到了这里。

我不确定scan是否必须发给广播地址，他才能响应。 直接发送给目的IP的话，会不会出现不响应的情况。

但是我一直没有重启HA的情况下，控制一直可用（从上一次恢复当前issue到现在，一直可用）。

另外，不响应是不是忘记配置dhcp对该mac地址固定分配IP，导致分配的IP地址发生变化，所以无法通信？

好吧，没仔细看，不响应一般是云控或者网络问题，跟填不填host没关系，填错了除外，ip变化了host还填原来的那肯定有问题的，你只有一个云控的话其实不填也没关系，scan广播能找到云控的，固定ip主要还是为了方便

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xcy1231 @ptaoo @CplusHua