added possible bias issue in readme

README.md

@@ -131,8 +131,12 @@ Key | Required | Default | Type | Description
 `state_active_low`|no | `false`| boolean| invert output for state pin
 `invert_state`|*backwards compatibility*| |boolean|see `state_active_low`, might be removed in the future
 `unique_id` | no | generated | string | An ID that uniquely identifies the switch. Set this to a unique value to allow customization through the UI, auto generated when not set manually in config
-
-## Add Debug info and issue reporting
+
+# Possible issues
+- in v1.2.5, the Added functionality: read GPIO states at homeassistant restart (not reboot of host/machine!), keeping state over restart, can have a possible side effect: Devices returning wrong state eg due to floating (not biased) might be set incorrectly at initialization. Eg floating to `on`. This 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)
+
+
+# Add Debug info and issue reporting
 *Before* reporting issues please add this to your `configuration.yaml` `logger` section, check logs and report issue adding logging.
 ```yaml
 logger: