RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user8164 — Mon, 13 Jun 2022 13:44:27 GMT

Hi,

I have looked further into the PyACI. Based on the descriptions of your setup, this is what seems to be the issues:

When you use db.nodes[0].unicast_address, this is the unicast_address registered in the database file for node 0. This may or may not be the case (it is hard to tell from the log, but you can check the database file at <mesh SDK folder>/scripts/interactive_pyaci/database/example_database.json in order to figure out). This is most likely OK as is, but checking the json database file does not hurt. Alternatively, you should be able to use the unicast address manually.

When configuring the (local, PyACI side) Generic On Off Client, setting the publish address, you should set app key handle 0 and the address handle for the node. It is such: "publish_set(<appkey_handle>, <address_handle>)" For your example, where you use the app key with index 0 for both nodes, it should be "gc1.publish_set(0, 0)" and "gc2.publish_set(0, 1)".

Finally I must correct a previous statement, in that it actually is the unicast address of the element that should be used as address argument to model_app_bind(), since the addressing of the message itself is handled by the previous publish_set() on the configuration client. For your example, though, with two nodes having one element each, using the unicast address of the node (as you corrected your code to) is correct. Adding to the primary unicast address is only correct when there are multiple elements on the node.

Regards,
Terje

RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user115760 — Mon, 13 Jun 2022 11:22:48 GMT

I shall wait for the answers..Thanks for your kind reply...

RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user8164 — Mon, 13 Jun 2022 11:02:14 GMT

Hi,

You will get answers, but please note that Nordic Aplication Engineers are usually only responding during Norwegian office hours. You may get answers from the community outside business hours, but please do not expect answers from employees during weekends.

Regards,
Terje

RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user115760 — Mon, 13 Jun 2022 05:04:36 GMT

Can someone please answer my question......

RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user115760 — Sat, 11 Jun 2022 07:02:17 GMT

I have changed the code as you said,

bb.model_app_bind(db.nodes[1].unicast_address , 0, mt.ModelId(0x1000)) // First One
bb.model_app_bind(db.nodes[0].unicast_address , 0, mt.ModelId(0x1000)) // Second One

I have done all the above mentioned steps with these two codes , one by one in two tests.

Both of the time , I get to control the LED of the first connected node only ( Address - 0010).It won't control the LED of secondly connected node ( Address - 0011).I have included the output values from PyACI as follows :

In [1]: send(cmd.Echo("123"))

In [2]: 2022-06-11 11:54:19,267 - INFO - COM13: {event: DeviceEchoRsp, data: {'data': '123'}}
In [2]: db = MeshDB("database/example_database.json")

In [3]: db.provisioners
Out[3]: [{'UUID': bytearray(b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'), 'allocated_group_range': [{'high_address': feff, 'low_address': c000}], 'name': 'BT Mesh Provisioner', 'allocated_unicast_range': [{'high_address': 7fff, 'low_address': 0010}]}]

In [4]: p = Provisioner(device, db)

In [5]: 2022-06-11 11:55:17,069 - INFO - COM13: Success
2022-06-11 11:55:17,073 - INFO - COM13: Success
2022-06-11 11:55:17,078 - INFO - COM13: SubnetAdd: {'subnet_handle': 0}
2022-06-11 11:55:17,083 - INFO - COM13: AppkeyAdd: {'appkey_handle': 0}
2022-06-11 11:55:17,087 - INFO - COM13: AppkeyAdd: {'appkey_handle': 1}
In [5]: p.scan_start()

In [6]: 2022-06-11 11:55:24,174 - INFO - COM13: Success
2022-06-11 11:55:26,103 - INFO - COM13: Received UUID 6e3b906982b9462ab2a3f84e282b43b6 with RSSI: -30 dB
In [6]: p.scan_stop()

In [7]: 2022-06-11 11:55:32,579 - INFO - COM13: Success
In [7]: p.provision(name="Light bulb 1")

In [8]: 2022-06-11 11:55:39,530 - INFO - COM13: Provision: {'context': 0}
2022-06-11 11:55:39,604 - INFO - COM13: Link established
2022-06-11 11:55:39,677 - INFO - COM13: Received capabilities
2022-06-11 11:55:39,679 - INFO - COM13: Number of elements: 1
2022-06-11 11:55:39,685 - INFO - COM13: OobUse: {'context': 0}
2022-06-11 11:55:41,916 - INFO - COM13: ECDH request received
2022-06-11 11:55:41,931 - INFO - COM13: EcdhSecret: {'context': 0}
2022-06-11 11:55:46,381 - INFO - COM13: Provisioning complete
2022-06-11 11:55:46,384 - INFO - COM13:         Address(es): 0x10-0x10
2022-06-11 11:55:46,389 - INFO - COM13:         Device key: 86a118c392505ab3e18128ca5776c12d
2022-06-11 11:55:46,394 - INFO - COM13:         Network key: 18eed9c2a56add85049ffc3c59ad0e12
2022-06-11 11:55:46,398 - INFO - COM13: Adding device key to subnet 0
2022-06-11 11:55:46,405 - INFO - COM13: Adding publication address of root element
2022-06-11 11:55:46,419 - INFO - COM13: DevkeyAdd: {'devkey_handle': 8}
2022-06-11 11:55:46,424 - INFO - COM13: AddrPublicationAdd: {'address_handle': 0}
2022-06-11 11:55:46,534 - INFO - COM13: Provisioning link closed
In [8]: cc = ConfigurationClient(db)

In [9]: device.model_add(cc)

In [10]:  cc.publish_set(8, 0)

In [11]:  cc.composition_data_get()

In [12]: 2022-06-11 11:56:25,691 - INFO - COM13: PacketSend: {'token': 1}
2022-06-11 11:56:25,713 - INFO - COM13: {event: MeshTxComplete, data: {'token': 1}}
In [12]:  cc.composition_data_get()

In [13]: 2022-06-11 11:56:31,350 - INFO - COM13: PacketSend: {'token': 2}
2022-06-11 11:56:31,367 - INFO - COM13: {event: MeshTxComplete, data: {'token': 2}}
2022-06-11 11:56:31,463 - INFO - COM13.ConfigurationClient: Received composition data (page 0x00): {
  "crpl": 40,
  "vid": "0000",
  "pid": "0000",
  "elements": [
    {
      "models": [
        {
          "modelId": "0000"
        },
        {
          "modelId": "0002"
        },
        {
          "modelId": "1000"
        },
        {
          "modelId": "1004"
        },
        {
          "modelId": "1203"
        },
        {
          "modelId": "1204"
        }
      ],
      "index": 0,
      "location": "0000"
    }
  ],
  "cid": "0059",
  "features": {
    "relay": 0,
    "proxy": 0,
    "low_power": 2,
    "friend": 0
  }
}
In [13]: cc.appkey_add(0)

In [14]: 2022-06-11 11:56:53,658 - INFO - COM13: PacketSend: {'token': 3}
2022-06-11 11:56:53,728 - INFO - COM13: {event: MeshTxComplete, data: {'token': 3}}
2022-06-11 11:56:53,757 - INFO - COM13.ConfigurationClient: Appkey status: AccessStatus.SUCCESS
2022-06-11 11:56:53,768 - INFO - COM13.ConfigurationClient: Appkey add 0 succeded for subnet 0 at node 0010
In [14]: cc.model_app_bind(db.nodes[0].unicast_address, 0, mt.ModelId(0x1000))

In [15]: 2022-06-11 11:57:19,136 - INFO - COM13: PacketSend: {'token': 4}
2022-06-11 11:57:19,160 - INFO - COM13: {event: MeshTxComplete, data: {'token': 4}}
2022-06-11 11:57:19,196 - INFO - COM13.ConfigurationClient: Model app bind status: AccessStatus.SUCCESS
2022-06-11 11:57:19,207 - INFO - COM13.ConfigurationClient: Appkey bind 0 to model 1000 at 0010
In [15]: gc1 = GenericOnOffClient()

In [16]: device.model_add(gc1)

In [17]: gc1.publish_set(0, 0)

In [18]: gc1.set(True)

In [19]: 2022-06-11 11:57:52,903 - INFO - COM13: PacketSend: {'token': 5}
2022-06-11 11:57:52,924 - INFO - COM13: {event: MeshTxComplete, data: {'token': 5}}
2022-06-11 11:57:52,949 - INFO - COM13.GenericOnOffClient: Present OnOff: on
In [19]:  gc1.set(False)

In [20]: 2022-06-11 11:58:04,065 - INFO - COM13: PacketSend: {'token': 6}
2022-06-11 11:58:04,088 - INFO - COM13: {event: MeshTxComplete, data: {'token': 6}}
2022-06-11 11:58:04,116 - INFO - COM13.GenericOnOffClient: off
In [20]: p.scan_start()

2022-06-11 11:59:20,973 - INFO - COM13: SuccessIn [21]:                                                                 
2022-06-11 11:59:22,583 - INFO - COM13: Received UUID 837f06b893b741e2855476a742d516cd with RSSI: -25 dB
In [21]: p.scan_stop()

2022-06-11 11:59:29,100 - INFO - COM13: SuccessIn [22]:                                                                 
In [22]: p.provision(name="Light Bulb 2")

In [23]: 2022-06-11 11:59:37,206 - INFO - COM13: Provision: {'context': 0}
2022-06-11 11:59:37,281 - INFO - COM13: Link established
2022-06-11 11:59:37,335 - INFO - COM13: Received capabilities
2022-06-11 11:59:37,338 - INFO - COM13: Number of elements: 1
2022-06-11 11:59:37,346 - INFO - COM13: OobUse: {'context': 0}
2022-06-11 11:59:37,601 - INFO - COM13: ECDH request received
2022-06-11 11:59:37,614 - INFO - COM13: EcdhSecret: {'context': 0}
2022-06-11 11:59:38,032 - INFO - COM13: Provisioning complete
2022-06-11 11:59:38,035 - INFO - COM13:         Address(es): 0x11-0x11
2022-06-11 11:59:38,038 - INFO - COM13:         Device key: f2440878dd6a711439eacc7d328cc0ed
2022-06-11 11:59:38,042 - INFO - COM13:         Network key: 18eed9c2a56add85049ffc3c59ad0e12
2022-06-11 11:59:38,045 - INFO - COM13: Adding device key to subnet 0
2022-06-11 11:59:38,049 - INFO - COM13: Adding publication address of root element
2022-06-11 11:59:38,063 - INFO - COM13: DevkeyAdd: {'devkey_handle': 9}
2022-06-11 11:59:38,067 - INFO - COM13: AddrPublicationAdd: {'address_handle': 1}
2022-06-11 11:59:38,200 - INFO - COM13: Provisioning link closed
In [23]: bb=ConfigurationClient(db)

In [24]: device.model_add(bb)

In [25]: bb.publish_set(9,1)

In [26]: bb.composition_data_get()

In [27]: 2022-06-11 12:00:43,651 - INFO - COM13: PacketSend: {'token': 7}
2022-06-11 12:00:43,669 - INFO - COM13: {event: MeshTxComplete, data: {'token': 7}}
2022-06-11 12:00:43,766 - INFO - COM13.ConfigurationClient: Received composition data (page 0x00): {
  "crpl": 40,
  "vid": "0000",
  "pid": "0000",
  "elements": [
    {
      "models": [
        {
          "modelId": "0000"
        },
        {
          "modelId": "0002"
        },
        {
          "modelId": "1000"
        },
        {
          "modelId": "1004"
        },
        {
          "modelId": "1203"
        },
        {
          "modelId": "1204"
        }
      ],
      "index": 0,
      "location": "0000"
    }
  ],
  "cid": "0059",
  "features": {
    "relay": 0,
    "proxy": 0,
    "low_power": 2,
    "friend": 0
  }
}
2022-06-11 12:00:43,792 - INFO - COM13.ConfigurationClient: Received composition data (page 0x00): {
  "crpl": 40,
  "vid": "0000",
  "pid": "0000",
  "elements": [
    {
      "models": [
        {
          "modelId": "0000"
        },
        {
          "modelId": "0002"
        },
        {
          "modelId": "1000"
        },
        {
          "modelId": "1004"
        },
        {
          "modelId": "1203"
        },
        {
          "modelId": "1204"
        }
      ],
      "index": 0,
      "location": "0000"
    }
  ],
  "cid": "0059",
  "features": {
    "relay": 0,
    "proxy": 0,
    "low_power": 2,
    "friend": 0
  }
}
In [27]: bb.appkey_add(0)

2022-06-11 12:01:15,531 - INFO - COM13: PacketSend: {'token': 8}
In [28]: 2022-06-11 12:01:15,614 - INFO - COM13: {event: MeshTxComplete, data: {'token': 8}}
2022-06-11 12:01:15,648 - INFO - COM13.ConfigurationClient: Appkey status: AccessStatus.SUCCESS
2022-06-11 12:01:15,664 - INFO - COM13.ConfigurationClient: Appkey bind 0 succeded for subnet 0 at node 0011
2022-06-11 12:01:15,669 - INFO - COM13.ConfigurationClient: Appkey status: AccessStatus.SUCCESS
2022-06-11 12:01:15,685 - INFO - COM13.ConfigurationClient: Appkey add 0 succeded for subnet 0 at node 0011
In [28]: bb.model_app_bind(db.nodes[1].unicast_address , 0, mt.ModelId(0x1000))

In [29]: 2022-06-11 12:02:28,505 - INFO - COM13: PacketSend: {'token': 9}
2022-06-11 12:02:28,532 - INFO - COM13: {event: MeshTxComplete, data: {'token': 9}}
2022-06-11 12:02:28,556 - INFO - COM13.ConfigurationClient: Model app bind status: AccessStatus.SUCCESS
2022-06-11 12:02:28,569 - INFO - COM13.ConfigurationClient: Appkey bind 0 to model 1000 at 0011
2022-06-11 12:02:28,570 - INFO - COM13.ConfigurationClient: Model app bind status: AccessStatus.SUCCESS
2022-06-11 12:02:28,578 - INFO - COM13.ConfigurationClient: Appkey bind 0 to model 1000 at 0011
In [29]: gc2 = GenericOnOffClient()

In [30]: device.model_add(gc2)

In [31]: gc2.publish_set(0, 0)

In [32]: gc2.set(True)

In [33]: 2022-06-11 12:03:41,731 - INFO - COM13: PacketSend: {'token': 10}
2022-06-11 12:03:41,751 - INFO - COM13: {event: MeshTxComplete, data: {'token': 10}}
2022-06-11 12:03:41,776 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:03:41,778 - INFO - COM13.GenericOnOffClient: Present OnOff: on
In [33]: gc3 = GenericOnOffClient()

In [34]: device.model_add(gc3)

In [35]: gc3.publish_set(9, 1)

In [36]: gc3.set(True)

In [37]: 2022-06-11 12:06:37,934 - INFO - COM13: PacketSend: {'token': 11}
2022-06-11 12:06:37,949 - INFO - COM13: {event: MeshTxComplete, data: {'token': 11}}
In [37]: gc3.set(True)

In [38]: 2022-06-11 12:06:41,140 - INFO - COM13: PacketSend: {'token': 12}
2022-06-11 12:06:41,158 - INFO - COM13: {event: MeshTxComplete, data: {'token': 12}}
In [38]: gc3.set(True)

In [39]: 2022-06-11 12:06:43,724 - INFO - COM13: PacketSend: {'token': 13}
2022-06-11 12:06:43,739 - INFO - COM13: {event: MeshTxComplete, data: {'token': 13}}
In [39]: gc3.publish_set(0,0)

In [40]: gc3.set(True)

In [41]: 2022-06-11 12:07:19,260 - INFO - COM13: PacketSend: {'token': 14}
2022-06-11 12:07:19,283 - INFO - COM13: {event: MeshTxComplete, data: {'token': 14}}
2022-06-11 12:07:19,311 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:07:19,314 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:07:19,317 - INFO - COM13.GenericOnOffClient: Present OnOff: on
In [41]: gc3.set(False)

In [42]: 2022-06-11 12:07:26,888 - INFO - COM13: PacketSend: {'token': 15}
2022-06-11 12:07:26,911 - INFO - COM13: {event: MeshTxComplete, data: {'token': 15}}
2022-06-11 12:07:26,944 - INFO - COM13.GenericOnOffClient: off
2022-06-11 12:07:26,949 - INFO - COM13.GenericOnOffClient: off
2022-06-11 12:07:26,952 - INFO - COM13.GenericOnOffClient: off
In [42]: ab = GenericOnOffClient()

In [43]: device.model_add(ab)

In [44]: ab.publish_set(0,0)

In [45]: ab.set(True)

In [46]: 2022-06-11 12:08:35,356 - INFO - COM13: PacketSend: {'token': 16}
2022-06-11 12:08:35,375 - INFO - COM13: {event: MeshTxComplete, data: {'token': 16}}
2022-06-11 12:08:35,400 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:08:35,402 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:08:35,404 - INFO - COM13.GenericOnOffClient: Present OnOff: on
2022-06-11 12:08:35,406 - INFO - COM13.GenericOnOffClient: Present OnOff: on

I have included the video where I control the Dongle with Address - 0010, But I am unable to control the Dongle having Address - 0011 .

www.veed.io/.../3d3935c8-9ffd-474a-b698-6b70bd1bf72b

I want to control the LEDs of these two Dongles separetly from commands using PyACI.Please do some help to achieve that.

Thankyou.

-Vicky

RE: Provisioning and Controlling Two Dongles, which run Mesh Light Switch Server example using Mesh Serial Example

user8164 — Fri, 10 Jun 2022 14:25:30 GMT

Hi,

Configuration of a node is always done using the configuration server model on the primary element, for all models (on all elements) on that node.

For that reason, the address parameter for the PyACI model_app_bind() should be the unicast address of the node that you want to do the configuration on, i.e. the unicast address of the configuration server model, on the primary element of the node.

I do not know what you attempt at using "db.nodes[1].unicast_address + 1", which would either be the second element on node 1 or if node 1 has only one element (the primary element) the first element on node 2, or possibly there are no nodes using that unicast address at all. Removing the "+ 1" should do the trick.

Regards,
Terje