-
-
Notifications
You must be signed in to change notification settings - Fork 2
Retrieve messages
[Note: this is new functionality that will be included as of v2024.04.1 of the integration]
The latest message from the Studer devices is available via the 'Latest Message' entity (sensor.studer_4001_xcom_99022). Related sensors will provide info about the source device the message originated from and the message timestamp.

This functionality requires that the Xcom-LAN/232i device is discovered. For existing integration configurations, go to Settings -> Integration -> Studer-Innotec and press the gear icon to triger discovery of new devices.
The xcom protocol will clear the 'Is message pending' entity (binary_sensor.studer_4001_xcom_99000) whenever the latest message (message #0) is retrieved. This is not something the integration is actively doing, it is behavior within the Xcom / RCC devices.
As a result, the 'Is message pending' entity will always show as Off when the 'Latest Message' entity is also present. These two entities should not be used together. Either:
-
Just use the 'Latest message' entity; Home Assistant will indicate when the value was last changed and you can have automations triggered when its value changes.
-
Just use the 'Is message pending' entity and when set use a call to the 'get-message' service to retrieve the message (see below)
A service call is available to retrieve any message in the system. Index 0 will retrieve the latest message (and reset the 'is message pending' flag), subsequent indexes will retrieve older messages.
