Nothing is missing, per se. I’m only using it for lux input to a couple of rules. I have it set to publish every 15 minutes, with “don’t publish” when illuminance is minimum.
Up until the 2.1.3 update, it worked as I expected it to. Now it stops publishing lux around sunset, but doesn’t start up again in the morning until I manually hit “poll.” Then it works again until evening.
I’ve changed the preferences to publish every 30 minutes when illuminance is minimum. I’ll see if that helps tomorrow.
Oh man, I’m sorry. The Luxuriant-Driver is actually the one I’m having problems with. Posted in the wrong thread I guess. I’ll go pound my head on the keyboard for a while.
@bangali added the Day+1 forecast data as one of the last features to his code. After observing the day[0] and day[+1], his concerns are indeed valid (they are always the same). @csteele - would you look into advancing the day[+1] and day[+2]? Thank you!
for my zip code, the next 3 months of forecast precip is:
totalprecip_mm 0
totalprecip_in 0
I'd be happy to shift my development hub to a different zip.. one that gets rain. Should I just use Oregon?
May have to invent my own Zip Code... Oregon has zero forecast for the next 3 days, I tried Rochester NY, America's rainiest city.. only one day of forecast precip. But I'll try and watch to see if it "rolls" through the day+x attributes.
Try KMCO. It doesn't necessarily rain every day in central Florida, but the forecast is always for rain in the summer months. The below is not apixu, but you get the idea:
I noticed this morning that I am getting the following error with this driver. Don't know how long it has been going on, but I just noticed it just now.
I have been noticing that lux is not updating unless I hit save preferences and then run a poll. This was working at some point, but I seem to need to do this almost daily. I am using the the wx-ApiXU driver, not the Luxuriant-Driver.
Well I am not seeing the errors in the logs now. Before I went to work this morning, I did change the minimun luminance interval to 5 minutes (was no selection) and saved preferences. Then I did a Poll and Refresh command.
Maybe I just needed to do that after updating the driver a few days ago.
Anyways, I will monitor the logs and if the error pops again, I will let you know.
@csteele
Ive been using your lux only driver since you released it. Its working great for my use cases. Ive been in contact with support over a corrupt data base that took down my zigbee network this past Sunday. Bobby went through my hub and noticed errors coming from my envisalink integration as well as the lux driver. Just wanted to let you know of the errors. Thx
ApiXU weather api did not return data: hubitat.scheduling.AsyncResponse@a1acf0
groovy.json.JsonException: Lexing failed on line: 1, column: 181, while reading 'S', no possible valid JSON value or punctuation could be recognized. on line 238 (apixuHandler)
Yeah...I am getting these now too. They just started today. Did anyone have any idea how to fix this? Although it does seem to have resolved itself for me about an hour ago. Maybe APIXU was down.
That error is disappointing, but accurate. Code checks that the site says "OK" (code 200) and then tries to parse the JSON. As is clear: "hubitat.scheduling.AsyncResponse@a1acf0" isn't json. Perhaps ApiXU did their own code upgrade and is returning defective data?
I've been getting wx-ApiXU-driver ready for a 1.4.0 release and I'm getting correct data.
I looked at my production hub and yes, I see the errors too.
First occurred at 11:30pm (yesterday) here... was intermittent til 9:32am when it pretty much became useless... then cleared up about 42 minutes ago. I've had 9 good returns in that period.
i'm seeing those same errors. It started at 9:20 AM PDT, and cleared up at 2:10 PM PDT. It's been fine since then.
Prior to that, I've been getting the error: ApiXU weather api did not return data: hubitat.scheduling.AsyncResponse
Intermittently for the last couple of days.