commit e6ce7ba538264c607e64f8c7835019d13ec2f928
Author: Joseph Crowell <joseph.w.crowell@gmail.com>
Date: Wed Dec 24 23:38:29 2025 +0000
add note about fixing encryption if bot was in a room before encryption was enabled on that room
Signed-off-by: Joseph Crowell <joseph.w.crowell@gmail.com>
diff --git a/docs/protocols/matrix/README.md b/docs/protocols/matrix/README.md
index 966793c..8e08ab1 100644
--- a/docs/protocols/matrix/README.md
+++ b/docs/protocols/matrix/README.md
@@ -664 +6610 @@ MxID, Token and DeviceID are required for encryption even though they are option
5. Restart the bot and enjoy encrypted messaging
-Note: If you enable encryption on a channel after enabling encryption on the bot, you may need to regenerate your RecoveryKey, Token and DeviceID before the bot can send encrypted messages
+##### Notes
+
+- If you enable encryption on a channel after enabling encryption on the bot, you may need to regenerate your RecoveryKey, Token and DeviceID before the bot can send encrypted messages
+- If Matterbridge was present before encryption was enabled on a channel, it will not initialize crypto correctly and will continue sending unencrypted messages.
+ 1. Kick the bot from the room or leave the room with the bot's account (e.g in Element or some other client).
+ 2. Re-invite the bot to the room.
+ 3. The bot will get the encryption flag and start sending encrypted messages.
