Skip to content

Describe the RMI timeout, error codes 45 and 52, and the CAN request counter #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michaelarnauts merged 1 commit into from
Oct 20, 2026
Merged

Describe the RMI timeout, error codes 45 and 52, and the CAN request counter #178

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/PROTOCOL-RMI.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,8 @@ If an error occurs the reason can be one of the following:
| 32 | The property can't be read (get) or written (set) |
| 40 | The reply doesn't fit |
| 41 | The request is too short, e.g. a missing property id, value or argument |
| 45 | The node didn't answer within 1 second (set by the bridge) |
| 52 | The bridge is still busy with another RMI to that node (set by the bridge) |

## General commands

Expand Down
8 changes: 5 additions & 3 deletions docs/PROTOCOL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -403,8 +403,10 @@ message: "ComfoAir Q450 B R RF ST Quality\000"
```

When the RMI itself fails, the bridge answers with `result: RMI_ERROR` and puts the error code in the `result` field
of the `CnRmiResponse` (see [Error codes](PROTOCOL-RMI.md#error-codes)). The official app sends a request a second time
when the first one failed or got no answer, also after an `RMI_ERROR` †.
of the `CnRmiResponse` (see [Error codes](PROTOCOL-RMI.md#error-codes)). When the node doesn't answer within 1 second,
the bridge answers with `RMI_ERROR` and error code `45`. The bridge handles up to 4 RMI requests at the same time; more
requests wait until one is done. The official app sends a request a second time when the first one failed or got no
answer, also after an `RMI_ERROR` †.

For an overview about the known RMI Requests, check [PROTOCOL-RMI.md](PROTOCOL-RMI.md)

Expand Down Expand Up @@ -453,7 +455,7 @@ RMI-Commands are sent and received using extended-IDs:
1F000000
+ SrcAddr << 0 6 bits source Node-Id
+ DstAddr << 6 6 bits destination Node-Id
+ AnotherCounter <<12 2 bits we dont know what this is, set it to 0, everything else wont work
+ AnotherCounter <<12 2 bits request counter: the bridge adds 1 (0 to 3) for every request to a node, copied over to the response
+ MultiMsg <<14 1 bit if this is a message composed of multiple CAN-frames
+ ErrorOccured <<15 1 bit When Response: If an error occured
+ IsRequest <<16 1 bit If the message is a request
Expand Down
Loading