Data flows between Indigo and Home Assistant?

Posted on
Tue Oct 27, 2020 10:00 am
nathanw offline
Posts: 108
Joined: Sep 05, 2011
Location: Boston, MA

Data flows between Indigo and Home Assistant?

For my understanding and mental modeling, can the flow of information and control via HassBridge be explained by someone who understands better than I do?

I know that HassBridge has a direct channel to Home Assistant (which is why it needs the auth token), and there's also publishing via MQTT. What's the flow, each direction, for:

- observing the current state of devices
- changing state with commands (sending off/on/set level operations, etc)
- publishing events like level changes or new sensor values

Thanks.

Posted on
Tue Oct 27, 2020 10:16 am
WonderSlug offline
Posts: 77
Joined: Sep 08, 2017

Re: Data flows between Indigo and Home Assistant?

Yeah there are two different flows into and out of Home Assistant.

First there is the MQTT connection. It is the tight integration for all the devices in Indigo. It allows the two way control of devices. It also does all of the setup of the types of devices that are being exposed from Indigo, including all of the device class parts and capabilities of a device (number of fan speeds etc)

The direct connection with the authentication token is an HTTP rest based connection that allows HassBridge to submit events to Home Assistant from Indigo. Things like an Insteon Double click on or off do not have an equivalent in Home Assistant MQTT and need to be exposed as an event that can be caught and handled by Home Assistant automations. Information about entity names and such are also pulled into Indigo via the direct HTTP connection.

Posted on
Tue Oct 27, 2020 10:20 am
WonderSlug offline
Posts: 77
Joined: Sep 08, 2017

Re: Data flows between Indigo and Home Assistant?

- observing the current state of devices:

This comes from MQTT and is published by Indigo to the MQTT state_topic

- changing state with commands (sending off/on/set level operations, etc)

This is called command in the MQTT discovery context. and is sent back to Indigo via the command_topic. Things like brightness and fan speed etc all have different command topics based on the device type.

- publishing events like level changes or new sensor values

These do not get published as events from Indigo. The state changes happen via MQTT publishing and HA creates its own events when they do.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest