Invalid timestep: current about ha-climacell-weather HOT 7 CLOSED

hi, I totally did not see that timestep option. I will try to implement this but it will take some time.

from ha-climacell-weather.

Of course the instant I post this I realize my error. The correct format is:

timestep: "[0,0]"

from ha-climacell-weather.

Turns out that doesn't work either.

Nor does:

timestep: "0,0"

or:

timestep: "0"

from ha-climacell-weather.

@Hilo4321 I just created a new pull-request with the support for "current" timestamp. Could you please test this and give feedback. Thanks

from ha-climacell-weather.

I don't know how to do this properly, so I created the files and uploaded the 2 relevant changed files into the folder. Can you download a pull directly vs copy/paste into a file?

I was able to set it up using "current" without seeing the invalid timestep error in the log (there are others), but sensors were showing "unknown" for data. I am getting data for daily forecasts (only other I am using).

Full startup log

Side note: it looks like climacell docs suggest that "0" is the correct timestep, am I reading that wrong?

from ha-climacell-weather.

hi @Hilo4321

I use the following config for my "current" test timeline and it seems to work fine:

    - fields:
        - temperature
      timestep: "current"
      scan_interval:
        minutes: 30
      update: auto
      name: "current"

regarding your setup: it seems that your are using fields which are currently not supported. Line 13 of your log says ".query.fields[10] should be equal to one of the allowed values". It seems that your are using the fields epaHealthConcern,roadRiskScore,roadRiskConfidence and roadRiskConditions which are not in the core data layers.

from ha-climacell-weather.

I appreciate the follow up. With those adjustments I am no longer seeing errors.

from ha-climacell-weather.