Open lupus78 opened 1 year ago
I'm running the app with this command on a raspberry pi 4:
./GoSungrow mqtt sync > output.log 2>&1 &
It works fine, but after a few hours the requests start to timeout an stay like that. Here is a snippet of the output.log:
2023/02/07 16:45:40 INFO: Syncing 211 entries with HASSIO from queryDeviceList. -UU-UU-U-UU-UUU 2023/02/07 16:45:40 INFO: Syncing 148 entries with HASSIO from getPsList. UUUUUUUUUUUUUUUUUUUUUU?UUUU??UUUUUU?UUUUUUUUUUUUUUUCUUUUUUUUUUUUUUUU?UUUUUUCUUUCUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU?UU?UUUUUUUUUUUUUUUCUUCUUUUUUUUUU 2023/02/07 16:45:40 INFO: Syncing 205 entries with HASSIO from getPsDetail. UUUUU?UUUUUUUUUUUUU???UUCUU??UUU???U?U???UUUU???UUUUU?U?UUU???UUU?UUU?UUUU?UUUU??UUUU?UU??UU?U???U?U?U?UUU??UUCUU??UUUU?U?UUUU?U?UUU?U?U??U?U?UU?UUUUU?U??UUU??UCU?U?UU?UUU?UU????UUCUU?U?UUUUU?UU?UUCUUUUUUCUUU??U 2023/02/07 16:50:50 ERROR: Post "https://gateway.isolarcloud.eu/v1/powerStationService/getPsList": dial tcp: lookup gateway.isolarcloud.eu on 192.168.1.1:53: read udp 192.168.1.100:57977->192.168.1.1:53: i/o timeout 2023/02/07 16:55:40 ERROR: Post "https://gateway.isolarcloud.eu/v1/powerStationService/getPsList": dial tcp: lookup gateway.isolarcloud.eu on 192.168.1.1:53: read udp 192.168.1.100:57977->192.168.1.1:53: i/o timeout 2023/02/07 17:00:40 ERROR: Post "https://gateway.isolarcloud.eu/v1/powerStationService/getPsList": dial tcp: lookup gateway.isolarcloud.eu on 192.168.1.1:53: read udp 192.168.1.100:57977->192.168.1.1:53: i/o timeout
After the first timeout it never resumes. But! If I stop the process and start it again, the connection is working again.
Am I doing something wrong, or Sungrow is trying to make our lives harder? :)
This comment mentions the same issue: https://github.com/MickMake/GoSungrow/issues/30#issuecomment-1401206072
I'm running the app with this command on a raspberry pi 4:
It works fine, but after a few hours the requests start to timeout an stay like that. Here is a snippet of the output.log:
After the first timeout it never resumes. But! If I stop the process and start it again, the connection is working again.
Am I doing something wrong, or Sungrow is trying to make our lives harder? :)
This comment mentions the same issue: https://github.com/MickMake/GoSungrow/issues/30#issuecomment-1401206072