4. Troubleshooting

Mermaid is not detected

Mermaid might not be detected by Apple Home. It can happen if accessory files are corrupted of if you unpaired Mermaid from your Home.

To fix the issue, simply delete the whole content of <mermaid-install-path>/accessory/ folder and restart Mermaid.

Events of Mermaid server are logged in the logs/server.log file using the node-syslogger module.

Each events are flagged by a Level and a Module.

Logs use the the following format:

Date - LEVEL - Module - Message

For instance:

Sat, 27 Jan 2024 16:49:46 GMT - INFO - SERVER - Debug level set to INFO

The module reveals the module name where the event occured.

The level reveals the event's severity.

Available levels (sorted by descending severity) are:

fatal: Unrecoverable error, the process stops
error: Error recovered by the process without crashing, features and/or actions may not have been performed properly
warn: Unexpected event recovered by the process without crashing, features not impacted, default settings have been applied
info: Informational event
debug: Detailed event used to trace process calls

Note

By default, Mermaid log level is set to info (so all events with severity equal or above info will be logged).

Tip

You can change the default log level by changing the value of the LOG_LEVEL constant in mermaid.js file

If running Mermaid in a docker container, use

docker compose logs -f --tail 50

Start Mermaid Stack:

docker compose up -d

Stop Mermaid Stack:

docker compose stop