Closed dkrushev closed 3 months ago
Hey there @jpbede, @viktorvav99, mind taking a look at this issue as it has been labeled with an integration (co2signal
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
co2signal documentation co2signal source (message by IssueLinks)
Please check the log file, is there anything logged?
Do you have some logs we can take a look at?
I don't see any issues with the API from Electricity Maps side.
Since integration is no longer installed and any attempt to install it is with above error, I'm not sure how to enable/extract logs. Can you advise?
You have a home-assistant.log
in your configuration directory. Simply attach it here
Hello,
Nothing related to Electricity Maps integration in that log. Here are are the rows form this morning while I repeatedly tried to set it up again:
2024-07-15 07:58:56.903 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721019531860'} 2024-07-15 08:04:56.921 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721019891877'} 2024-07-15 08:10:56.945 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721020251901'} 2024-07-15 08:12:26.954 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721020341908'} 2024-07-15 08:21:26.988 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721020881945'} 2024-07-15 08:23:56.997 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721021031954'} 2024-07-15 08:24:57.003 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721021091960'} 2024-07-15 09:17:49.340 ERROR (MainThread) [custom_components.hacs] Could not update integration - Timeout of 60s reached 2024-07-15 09:17:49.342 ERROR (MainThread) [custom_components.hacs] Could not update plugin - Timeout of 60s reached 2024-07-15 09:17:49.344 ERROR (MainThread) [custom_components.hacs] Could not update template - Timeout of 60s reached 2024-07-15 09:47:57.126 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000f42654', 'apikey': '', 'sequence': '1721026072082'} 2024-07-15 09:47:57.496 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000f42654', 'apikey': '', 'sequence': '1721026072452'} 2024-07-15 09:49:57.231 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000ae8d5a', 'apikey': '', 'sequence': '1721026192188'} 2024-07-15 09:53:57.140 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000f42654', 'apikey': '', 'sequence': '1721026432097'} 2024-07-15 09:53:57.515 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000f42654', 'apikey': '', 'sequence': '1721026432471'} 2024-07-15 13:55:27.870 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1000f42654', 'apikey': '', 'sequence': '1721040922826'} 2024-07-15 15:17:49.342 ERROR (MainThread) [custom_components.hacs] Could not update plugin - Timeout of 60s reached 2024-07-15 15:17:49.346 ERROR (MainThread) [custom_components.hacs] Could not update template - Timeout of 60s reached 2024-07-15 15:17:49.350 ERROR (MainThread) [custom_components.hacs] Could not update integration - Timeout of 60s reached
Local time is CEST+1
Based on your log I would say that your instance has a network problem. The sonoff custom component runs into a timeout and HACS itself aswell
A timeout error actually usually indicates a problem with the network/internet, as your instance cannot reach the Electricity Maps servers. You can try to disable IPv6.
A timeout error actually usually indicates a problem with the network/internet, as your instance cannot reach the Electricity Maps servers. You can try to disable IPv6.
Deleted my post, figured out it was due to DNS server. Somehow my Home Assistant took ISP DNS instead of Google. All good now.
A timeout error actually usually indicates a problem with the network/internet, as your instance cannot reach the Electricity Maps servers. You can try to disable IPv6.
Disabling IPv6 solved the issue. Thank you!
Then I'm going to close this
I also had an issue with the integration for the past month or so, and disabling IPv6 fixed it.
The problem
Electricity Maps has stopped working for past several days. I tried to re-initialize, but returned a timeout error. Removed, rebooted HA and tried to install again, but it gives "Unexpected error" message in the setup GUI. Requested new token, same result.
What version of Home Assistant Core has the issue?
core-2024.7.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Electricity Maps
Link to integration documentation on our website
https://www.home-assistant.io/integrations/co2signal
Diagnostics information
Since integration is no longer installed and any attempt to install it is with above error, I'm not sure how to enable/extract logs.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response