Heartbeat publication set sets wrong parameters using interactive pyaci

RE: Heartbeat publication set sets wrong parameters using interactive pyaci

a.wallwitz — Tue, 24 Apr 2018 11:53:32 GMT

Thanks it works 🙂

Answer was marked as solution.

RE: Heartbeat publication set sets wrong parameters using interactive pyaci

Thomas Stenersen — Tue, 24 Apr 2018 06:49:13 GMT

Hi Andrej,

Inspecting the heartbeat_publication_set() method, I see you’ve uncovered a small bug. I’ve reported (and fixed) this internally, here’s the diff:

modified   scripts/interactive_pyaci/models/config.py
@@ -387,7 +387,7 @@ class ConfigurationClient(Model):
                                   feature_bitfield=0, netkey_index=0):
         message = bytearray()
         message += struct.pack(
-            "<HBBBHH", dst, log2b(count), log2b(count), ttl, feature_bitfield, netkey_index)
+            "<HBBBHH", dst, log2b(count), log2b(period), ttl, feature_bitfield, netkey_index)
         self.send(self._HEARTBEAT_PUBLICATION_SET, message)

Notice that this method takes count and period and packs them according to spec (p. 147 of the Mesh Profile specification v1.0) using the log2b() function. This limits the list of valid values to only be those that is a power of 2. Your 0xdd (221) is rounded down to 0x80 (2^(8-1) = 128). In the data sent to the mesh device, you’ll see that the count and period is sent as 0x08 and 0x08, this gives 2^8-1 = 128.

Please let me know if anything is unclear.

Hope this helps,
Thomas

RE: Heartbeat publication set sets wrong parameters using interactive pyaci

a.wallwitz — Fri, 20 Apr 2018 07:11:52 GMT

No it's not. I just added the information to let you know that the opcode is correct and which sdk version I'm using. The problem itself still exists.

RE: Heartbeat publication set sets wrong parameters using interactive pyaci

Susheel Nuguru — Thu, 19 Apr 2018 11:40:27 GMT

is it working ok in the latest release? if that is the case, then i can mark your reply as valid answer.

RE: Heartbeat publication set sets wrong parameters using interactive pyaci

a.wallwitz — Wed, 18 Apr 2018 13:00:17 GMT

I'm using Mesh SDK 2.0 that got released today.

And the OpCode I receive on the device side is:
<t: 8134821>, access.c, 291, RX: [aop: 0x8039]
which is Config Heartbeat Publication Set and looks ok.