Testing now. FWIW, so far I get errors, but it’s not preventing HA from starting.
def prevents starting for me. If I do a config check it says config invalid because illuminance is calling darksky. If I do a core restart I get an error in the log. If I restart the container (using portainer) it restarts and runs but with errors. It’s not possible to do a normal restart from the GUI
Released 4.0.1
Should now handle DarkSky no longer being available in HA (as of 2023.4.0b6.)
2 Likes
Release 4.0.1 is working for me.
Many thanks for the fix.
1 Like
Released 4.1.0
Previous release was designed to allow installations using an older version of HA to continue to use a Dark Sky weather entity. Now that I’ve had a chance to confirm that the Dark Sky API is, indeed, shut down, this release removes all remnants of Dark Sky support.
1 Like
This is awesome — just sat down the past few days to set up HA again. I was not very deep before, but I’m stunned by how far its come in the past two years that I’ve been away.
Quick question: I’m curious if anyone here would know where to start with integrating some sort of shadow mapping… it seems like it would be a bit (or a lot) more complex, but for anyone who lives near buildings (or mountains) the outside light is contingent on another pretty big variable…
I believe that the Forecast.Solar integration has some sensors, but there are also other APIs that provide information based on surrounding obstructions to sunlight (like ShadeMap.app). Anyone have any thoughts? Sorry its such a broad question, just got excited when I found this… currently sitting in about 5500K lights, while it’s pouring rain and looks like night outside the window.
Released 5.0.0
Add config flow, service info & translations
Support adding & configuring illuminance sensors via the UI. Change YAML configuration from platform under sensor: (which is now deprecated) to illuminance: . Add YAML reload service for illuminance integration.
1 Like
Nice work as always Phil. Switched to GUI config with no issues
1 Like
Hmm, seems like I forgot to post a few updates…
Released 5.2.0
Provide Polish translation
Released 5.3.0
Provide Italian translation
Released 5.4.0
Change minimum scan_interval to 0.5 minutes
Released 5.4.1
Fix for frozen EntityDescription, again
Released 5.4.2
First noticed in 2024.3.0b1, either something unexpected changed, or timing has changed, because a config entry reload that worked ok before is now running while the config entry is still being set up. This change prevents reloads from being started when the config is not in the correct state.
Released 5.4.3
Clamp cloud coverage values to 0 - 100 without logging error
1 Like
Released 5.5.0b0
- Make weather entity optional.
- Fallback default is 1 if no weather entity selected, or 10 when one is selected (as before.)
- The astral package uses pytz which does file I/O when it sees a new time zone. Force this file I/O to happen in an executor.
Starting w/ HA 2024.6, the scan interval option doesn’t work, and all illuminance sensors will update every 30 seconds. This will be fixed in 5.5.0b1.
Released 5.5.0b1
- Add irradiance mode option.
- Fix scan interval broken by HA 2024.6.
Released 5.5.0
- Make weather entity optional & add irradiance mode option by @pnbruckner in #69
- Make weather entity optional.
- Fallback default is 1 if no weather entity selected, or 10 when one is selected (as before.)
- Add irradiance mode option.
- Fix scan interval broken by HA 2024.6.
- The astral package uses pytz which does file I/O when it sees a new time zone. Force this file I/O to happen in an executor.
20241029 5.6.0
- Don’t require attribution attribute