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.

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

Question on new API #38

Open
julianrinaldi opened this issue Jan 21, 2021 · 8 comments
Open

Question on new API #38

julianrinaldi opened this issue Jan 21, 2021 · 8 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@julianrinaldi
Copy link

I spent the morning setting up a Road Risk conditions card, and then updated to the new version, and they all broke. I now realize the API has changed. I'm looking at the API documents and I'm not seeing anything for road conditions. Is this now gone?

@mfabiani53
Copy link

I think we need to know all the breaking changes after the latest update of the integration.... I will wait these before updating....

@r-renato
Copy link
Owner

Is this issue still there?

@r-renato r-renato self-assigned this Jan 25, 2021
@r-renato r-renato added the help wanted Extra attention is needed label Jan 25, 2021
@julianrinaldi
Copy link
Author

Yes. Actually all of my sensors are throwing errors and showing up as "Unknown"
2021-01-25 16:12:12 WARNING (SyncWorker_27) [custom_components.climacell.sensor] TimelineSensor.update - Provider has no data for: cc Climacell Precipitation 0d

I have signed up for and am using the V4 API Key

- platform: climacell
  api_key: !secret climacell_api_key
  name: Climacell
  timelines:
    - name: ""
      fields:
        - temperature
        - wind_direction
        - precipitation
        - precipitation_type
        - wind_speed
        - wind_direction
        - weather_condition
        - pollen_tree
        - pollen_weed
        - pollen_grass
        - road_risk
        - road_risk_conditions
        - road_risk_confidence
      update: auto
      forecast_observations: 5
      timestep: "15m"
      scan_interval:
          minutes: 5

@InToSSH
Copy link

InToSSH commented Jan 26, 2021

I have exactly the same problem. It worked for a bit, but only some sensors. The log is full of errors:

2021-01-26 01:14:02 WARNING (SyncWorker_6) [custom_components.climacell.sensor] TimelineSensor.update - Provider has no data for: cc Home Daily Temperature 0d
2021-01-26 01:14:02 WARNING (SyncWorker_2) [custom_components.climacell.sensor] TimelineSensor.update - Provider has no data for: cc Home Daily Temperature 1d
2021-01-26 01:14:02 WARNING (SyncWorker_4) [custom_components.climacell.sensor] TimelineSensor.update - Provider has no data for: cc Home Daily Temperature 2d

UPDATE: It started working after the latest update from HACS. Also make sure your fields are correctly set, it looks like if there is any, that's not supported, it won't load the rest aswell (had one myself)

@cbergmann
Copy link
Contributor

@InToSSH that is correct. One timeline is one request to the API with all the fields. This is to reduce the number of requests as this is the limiting factor of the free tier. But if the request fails for some reason there is no data for any field of that timeline.

@julianrinaldi is the problem still there with the current version?

@julianrinaldi
Copy link
Author

@cbergmann It is working now, but I think it was due to having old sensors still in my configuration. As I said earlier, the road conditions entities seem to have been removed, but I had left them in the configuration. Once I removed them, it worked correctly. Hopefully they come back at some point since that's the main reason I used this integration.

@jazzyisj
Copy link

@julianrinaldi

ClimaCell has removed everything but these core data layers from the free API in v4. I doubt any of the premium features will ever be added back to the core layers again. They gotta make money somehow!

https://www.climacell.co/data-catalog/core

@cbergmann
Copy link
Contributor

Hi, unfortunately that is correct but furthermore road risks seem to be available in no data layer. Despite the fact, that they mention it in the Overview. Therefore my PR #46 removes them completely. That should print a invalid field error and just skip the field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

6 participants