📝 Update changelog and known-issues

Author: andrei-lazarov

docs/changelog_fw.md

@@ -9,8 +9,21 @@ Please describe what you are working on:
 
 ### Changes
 
-- Bi-stable (latching) relays have been reworked and now use proper pulses instead of continuously driving the coil.
+- **Bi-stable (latching) relays** have been reworked
+  - They now use proper pulses instead of continuously driving the coil
+  - Pressing multiple buttons will toggle the relays with small delays in-between (safe)
+  - Add `SLP;` to the config string for simultaneous toggles (risky, might damage the device)
 
+### Bugs
+
+- **Fixed**
+  - Latching relays not working with off_pin A0
+  - Silabs version updates not working
+  - Telink End_device unreachable from Z2M after a while ([#217](https://github.com/romasku/tuya-zigbee-switch/issues/217))
+  - AC noise affecting Telink GPIO
+  - Changing device type breaks Silabs NVM data
+- **New**
+  - SONOFF ZBMINIL2 version updates broken?
 
 ------------------------------------------------------->
 
@@ -60,7 +73,7 @@ Please describe what you are working on:
   - Can't change device imageType in config string
   - Option 'Relay indicator - manual on' is not kept after reboot
   - Relay indicators sometimes go out-of-sync ([#38](https://github.com/romasku/tuya-zigbee-switch/issues/38))
-  - End_device sleeping? ([#217](https://github.com/romasku/tuya-zigbee-switch/issues/217))
+  - Telink End_device unreachable from Z2M after a while ([#217](https://github.com/romasku/tuya-zigbee-switch/issues/217))
 
 ## v1.0.21
 

docs/known_issues.md

@@ -4,12 +4,22 @@
 
 *Issues affecting the **latest version***
 
-## Bugs
+### Bugs
 
-- End_device sleeping? ([#217](https://github.com/romasku/tuya-zigbee-switch/issues/217))
-- Silabs version updates broken
+- SONOFF ZBMINIL2 version updates broken?
+- Telink Router sometimes unavailable? ([#255](https://github.com/romasku/tuya-zigbee-switch/issues/255))
 
-## Failed to read state of 'Switch' after reconnect 
+### Telink End_device unreachable from Z2M after a while
+- **should be fixed in latest build**
+- work-around: set Z2M 'Availablility check' to 10 mins or use Router firmware
+- discussion: [#217](https://github.com/romasku/tuya-zigbee-switch/issues/217)
+
+### End_device does not respond to Zigbee group commands
+- same issue on stock firmware
+- could be a Zigbee limitation
+- work-around: use Home Assistant groups or Router firmware
+
+### Failed to read state of 'Switch' after reconnect 
 
 - error shows up every time the switch reboots
 - **can safely be ignored**, doesn't mean anything  
@@ -21,14 +31,14 @@
 
 *Some of the already already fixed issues, only present on **old fw versions**.*
 
-## Custom config string bricks unit
+### Custom config string bricks unit
 
 - interacting with the 'device config' field **immediately bricks 3-4 gang devices**
 - fixed in v18 (partly) and v20 (fully)
 - recover: flash by wire
 - discussion: [#77](https://github.com/romasku/tuya-zigbee-switch/issues/77)
 
-## 4-gang devices can't update OTA
+### 4-gang devices can't update OTA
 
 - fixed in v17-18
 - ask for support or flash by wire

docs/updating.md

@@ -23,15 +23,17 @@ This page describes **converting** and **updating** supported devices **wireless
 4. **Apply** the preferred [# OTA index](#ota-index) (not FORCE)
 5. **Restart** HA / Z2M
 6. Bring the device closer to the coordinator, or add routers to **boost signal**  
-(Pairing requires stronger signal than normal usage)
+  (Pairing requires stronger signal than normal usage)
 7. Optionally, tweak Z2M settings for [# Faster OTA updates](#faster-ota-updates)
-8. **Start** the update (can get stuck at 100% - it's ok)
-9. **Permit join** when it's done (LED blinks if mapped correctly)
-10. **Interview** the device **`i`**  
-⤷ option missing from ZHA, remove and re-pair if needed  
-11. **Reconfigure** the device **`🗘`** 
-12. Be aware of [## Version update](#version-update) steps
-13. Read [faq.md](./faq.md) before reaching out for support
+8. **Check** for updates (blue cloud button) 
+9. **Start** the update (red download button)  
+  Progress bar may get stuck at 100% - it's ok
+1.  **Permit join** when it's done (LED blinks if mapped correctly)
+2.  **Interview** the device **`i`**  
+  ⤷ option missing from ZHA, remove and re-pair if needed  
+1.    **Reconfigure** the device **`🗘`** 
+2.    Be aware of [## Version update](#version-update) steps
+3.    Read [faq.md](./faq.md) before reaching out for support
 
 > Hopefully, you now have a working device with custom firmware! 😊  
 > *Consider yourself invited to our [Discord](/readme.md#discord) community!* 

readme.md

@@ -7,7 +7,7 @@
 
 Feature-rich custom firmware for Telink/Silabs Zigbee switches, modules, sockets
 
-- Already **60+** [supported_devices.md](./docs/supported_devices.md)
+- Already **80+** [supported_devices.md](./docs/supported_devices.md)
 - Port new devices: [contribute/porting.md](./docs/contribute/porting.md)
 
 ## 🤔 Why?