RE: Mesh Monitor with Heartbeat Messages

Bjørn Kvaale — Wed, 15 Aug 2018 07:31:00 GMT

Sorry for the delayed response.

1) Yes, this should work. You should be able to subscribe & publish to heartbeat messages right after configuration like you have shown above.

2) If I understand this correctly, you want to have a list of all of the nodes & each neighbor to all of the nodes in a list, correct?

3) Yes, you should be able to send & subscribe to heartbeat messages concurrently (not exactly at the same time). It should be quite similar to sending & receiving regular mesh messages.

4) Yes, you can control the on/off state of the light bulbs via PyACI.

5) Update from the developer: "The heartbeat messages are handled at the transport layer level. The heartbeat.c module is the one responsible for handling them & generating appropriate events to the application".

7) Yes

8) The mesh monitor should be running on the PC side of things, correct? As far as I understand, the mesh monitor will be running separately from the provisioner, correct? The mesh monitor will also not be a part of the mesh network, but should be able to read all of the mesh messages in that network, correct?

RE: Mesh Monitor with Heartbeat Messages

smart_life — Tue, 07 Aug 2018 09:53:06 GMT

I am confused about the heartbeat_suscription_set(src,dst,period)

7) this is the function to suscribe to receive heartbeat messages right ?

Heartbeat Subscription Source:
can be the unassigned address or a uni-cast address
If the Heartbeat Subscription Source is set to the unassigned address, the Heartbeat messages are not being processed

Heartbeat Subscription Destination: determines the destination address for Heartbeat messages
unassigned address, the primary uni-cast address of the node, or a group address, all other values are Prohibited.

8) the mesh specification says that source address has to be a unicast address but in a Mesh Monitor I cannot know the uni-cast address of the nodes (which potentially send the heartbeat messages ) which appear randomly in proximity of the node. What do I understand wrong ?