12.3. Integration with FireBrick opperations

12.3. Integration with FireBrick opperations
	Chapter 12. MQTT (experimental)

The FireBrick allows integration of MQTT with a number of internal operations.

Messages for internal operation all use a JSON payload. The exception is where a message is to be generated to send to some other device, e.g. a ligting control, where the message can be specified as a topic, a space, and a text payload.

12.3.1. Profiles

A profile can be set with a topic, and a payload for on and off. This causes an MQTT message to be sent when the profile is activated or de-activated. You can set this to be treated as MQTTS, so not set to MQTT clients (depending on configuration for relaying MQTT/MQTTS). You can also set this as a retained message.

The plan is also to allow a profile to be changed by an MQTT message.

12.3.2. VoIP

More on this will be added in due course.

The plan is to report call states as they happen.

The plan is also to allow calls to be directed in certain ways by MQTT message.

12.3.3. DHCP

Each DHCP pool can be set to report allocations and renewals via MQTT on a specified topic. This reports a JSON payload with details of the allocation.


12.2. Features		Chapter 13. Tunnels