Centralized sensor init
Full Changelog: v1.4.6...v1.4.7

Full Changelog: v1.4.5...v1.4.6

fix for cover issue

Full Changelog: v1.4.0...v1.4.5

• (2024-09-29) <6884662+jdeneef> HEAD -> main, origin/main, origin/HEAD, github/main
  | fixed version in manifest
• (2024-09-29) <6884662+jdeneef> tag: v1.4.3
  | remove commented code
• (2024-09-28) <6884662+jdeneef> tag: v1.4.2, tag: v1.4.1
  | fix to remove state error
• (2024-09-28) <6884662+jdeneef> tag: v1.4.0
  |\ Merge branch 'add-persistence'
  | * (2024-09-28) <6884662+jdeneef> origin/add-persistence, add-persistence
  | | updated readme for persistence over reboots
  | * (2024-09-28) <6884662+jdeneef>
  | | updated sensor reading at startup
  | * (2024-09-28) <6884662+jdeneef>
  | | removed previous persistence via gpiod
  | * (2024-09-25) <57483589+tomer-w>
  | | Make the persistent example more relevant
  | * (2024-09-23) <57483589+tomer-w>
  |/ Add persistentcy support for switches
• (2024-08-25) <6884662+jdeneef> tag: v1.3.0

Full Changelog: v1.3.0...v1.4.3

• (2024-09-28) <6884662+jdeneef> HEAD -> main, tag: v1.4.1, origin/main, origin/HEAD, github/main
  | fix to remove state error
• (2024-09-28) <6884662+jdeneef> tag: v1.4.0
  |\ Merge branch 'add-persistence'
  | * (2024-09-28) <6884662+jdeneef> origin/add-persistence, add-persistence
  | | updated readme for persistence over reboots
  | * (2024-09-28) <6884662+jdeneef>
  | | updated sensor reading at startup
  | * (2024-09-28) <6884662+jdeneef>
  | | removed previous persistence via gpiod
  | * (2024-09-25) <57483589+tomer-w>
  | | Make the persistent example more relevant
  | * (2024-09-23) <57483589+tomer-w>
  |/ Add persistentcy support for switches
• (2024-08-25) <6884662+jdeneef> tag: v1.3.0

Added functionality: read GPIO states at homeassistant restart (not reboot of host/machine!), keeping state over restart.
Possible side effect: Devices returning wrong state eg due to floating (not biased) might be set incorrectly at initialization. Eg floating to on can result in initialization to on even though it was off before restart. In my case I had to add bias: PULL_DOWN for my buzzer GPIO in order to avoid alarm at every homeassistant restart (on my dev rpi)

* (2024-08-25) HEAD -> main, tag: v1.3.0, origin/main, origin/HEAD, github/main
| added possible bias issue in readme
* (2024-08-21) tag: v1.2.5
| typo in changelog git line
* (2024-08-21)
| read initial status from gpio status (check bias on errors)
* (2024-08-04)
| removed changelog, added generation howto to README-DEV, generate from there
* (2024-08-04) tag: v1.2.4, tag: v1.2.3
| changelog creation from git

Changelog

• v1.2.0; found a solution to drop the loop waiting for gpio events!
• v1.2.2; config validation cleanups