0.2.6

Version 0.2.6

• Closes #32 - Fixed leaking unencrypted messages during startup
• Closes #34 - Fix connection state logic

0.2.4

Version 0.2.4

• Can now configure a room on the invite-room node (instead of having to pass it in on the msg)
• Changed how the connection event was handled by nodes
• matrix-synapse-join-room node was broken (was trying to access a variable that was never defined).
• olm library updated to 3.2.1 to hopefully fix "account.generate_fallback_key is not a function" Fixes #26
• Added description to the server configuration node that describes how to create a user for use with this module
• Update link to create room api for matrix-create-room.html
• Fixed guests param for synapse user list node
• Formatted html message wasn't converting to a string.

0.2.1

Another awesome update!

In this release we add support for accessing the raw matrix client object globally. This way you can do whatever you want with the matrix client from within a function node.

You need to enable this from within your client configuration. Once enabled you can use the following global variables within a function node for each client you have configured:

let matrixClient = global.get("matrixClient['@bot:example.com']"),
    matrixOnline = global.get("matrixClientOnline['@bot:example.com']");

This way you are no longed limited by what nodes we have created. If you do think we need to add a node for something please do let us know.

0.2.0

I recommend backing up your matrix-local-storage folder if you are using e2ee and are upgrading from a previous version. This version will perform an upgrade to a new directory structure. Reason for this change is described in #15

Changes:

• Fixed various node docs (closes #9 & closes #14)
• localstorage is now split between each client based on the userId (copied from ./matrix-local-storage to ./matrix-client-storage/<user_id_with_special_chars_replaced_with_underscores> for each server configuration you have. The original folder is then renamed to ./matrix-local-storage-backup just-in-case something goes wrong.
• Fixed issue with Node-RED crashing if an error is thrown during the start client phase.

0.1.8

Quickfix for e2ee not enabling

0.1.7

The only thing you need to watch out for in this release is to make sure that your server nodes have the e2ee either enabled or disabled depending on how you want it. Since this wasn't saving correctly you may need to go in and enable it now.

Updates:

• Fixed: Unchecking e2ee support from server config was not saving properly and was always enabled
• Session.logged_out events are now processed and send out errors from the server config node
• Readme & Examples updated
• Node descriptions updated
• Fixed: Invalid auth token would cause Node-RED to crash