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

"Failed setup, will retry" with "Updated failed: 'time'" #99

Open
eric opened this issue Mar 26, 2024 · 7 comments
Open

"Failed setup, will retry" with "Updated failed: 'time'" #99

eric opened this issue Mar 26, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@eric
Copy link

eric commented Mar 26, 2024

Describe the bug

I recently have an error for my integration saying "Failed setup, will retry" with a mouse-over showing "Updated failed: 'time'".

In the logs it only says:

2024-03-25 18:00:14.008 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.332 seconds (success: False)
2024-03-25 18:00:54.756 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.319 seconds (success: False)
2024-03-25 18:02:15.173 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.353 seconds (success: False)

I have enabled debug logging and it doesn't appear to make a difference.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the installed WeatherFlow Forecast integration
  2. See "Needs Attention" for the installed integration
@briis
Copy link
Owner

briis commented Mar 26, 2024

I cannot reproduce this right now. It can happen, when the Weatherflow Servers are not sending data, or you Internet temporary is down.

@eric
Copy link
Author

eric commented Mar 26, 2024

Interesting. Would it be possible to improve the error message to make it more clear?

@briis briis added the enhancement New feature or request label Apr 5, 2024
@briis
Copy link
Owner

briis commented Apr 5, 2024

Sure. I just need to capture the exact error that comes in from the API Request, so that I can raise the issue when it happens. I have already a few of them there, but obviously not them all.

@blindguynar
Copy link

blindguynar commented Apr 17, 2024 •
edited
Loading

Just saw this for the very first time tonight. Same as OP.

Screenshot 2024-04-16 at 9 43 16 PM

Error in log file
Screenshot 2024-04-16 at 9 47 47 PM

i don't see the API RC and i don't think the integration supports diagnostics so i can't provide that.

It started functioning again a short time later. I did get an email that my weather station was off-line, but it actually was not and never lost connection to wifi or internet. I think the weatherflow servers were off-line..

@lazerdave
Copy link

Same issue today. Started after a host system shutdown by my UPS.

@lazerdave
Copy link

lazerdave commented May 16, 2024 •
edited
Loading

Additional information:

It appears the API has either changed or is malfunctioning.

Getting raw data for all my stations by my token ID works at
https://swd.weatherflow.com/swd/rest/stations?token=[your_access_token]

However, trying to access an individual station at
https://swd.weatherflow.com/swd/rest/observations/station/[your_station_id]?token=[your_access_token]
returns

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>
	<title>Payara Server 6.2023.2 #badassfish - Error report</title>
	<style type="text/css">
		<!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}
		-->
	</style>
</head>

<body>
	<h1>HTTP Status 404 - Not Found</h1>
	<hr />
	<p><b>type</b> Status report</p>
	<p><b>message</b>Not Found</p>
	<p><b>description</b>The requested resource is not available.</p>
	<hr />
	<h3>Payara Server 6.2023.2 #badassfish</h3>
</body>

</html>

I've opened a ticket with Tempest Support.

@briis
Copy link
Owner

briis commented May 21, 2024

The above URL's both work fine for me with my Token and Station ID. Are you sure you have set your Station to Public Access? That is required for this to work.

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

No branches or pull requests
4 participants
@eric @lazerdave @briis @blindguynar