PyACI Serial Configuration and Model Subscription

RE: PyACI Serial Configuration and Model Subscription

timvan — Thu, 13 Jun 2019 12:10:14 GMT

I found that the messages coming in doing the above process are Subscription and not Unicast. Therefore to forward the data onto the Server model (or any model in that case) needs the following change to Access.__event_handler() in access.py line 212. [Mesh SDK v3.10]

# old
if event._opcode == Event.MESH_MESSAGE_RECEIVED_UNICAST:

# new
if event._opcode == Event.MESH_MESSAGE_RECEIVED_UNICAST or event._opcode == Event.MESH_MESSAGE_RECEIVED_SUBSCRIPTION:

RE: PyACI Serial Configuration and Model Subscription

Simon — Mon, 03 Dec 2018 15:17:53 GMT

I was able to receive the the events from a Generic OnOff Client model (external chip) by executing the same steps as you, except for one additional command:

cc.model_publication_set(db.nodes[0].unicast_address+1, mt.ModelId(0x1001),mt.Publish(db.groups[0].address, index=0, ttl=1))

This will make the Generic OnOff client model publish its event to group address 0 (from example_database.json). Then, if an interactive python session is running, you will receive a message similar as below:

2018-12-03 15:16:52,996 - INFO - COM7: {event: MeshMessageReceivedSubscription, data: {'src': 17, 'dst': 1, 'appkey_handle': 0, 'subnet_handle': 0, 'ttl': 1, 'adv_addr_type': 1, 'adv_addr': bytearray(b'L\x9e\xfe \x83\xd4'), 'rssi': -60, 'actual_length': 6, 'data': bytearray(b'\x82\x02\x01\t\x01\n')}}

I am not sure how to correctly forward the events to the Generic OnOff Server model, but here is my guess: Add the GenericOnOffServer class to interactive_pyaci.py, and create an object, then modify the event handler in the Interactive class to forward the events to the GenericOnOffServer class.

I will ask somebody with more knowledge about this, and give you an update if needed.

Best regards,

Simon

UPDATE (12.10.2018):

In addition to what I have mentioned (i.e. to see the events in the pyACI log), you will need to add the event filter to forward these events.

RE: PyACI Serial Configuration and Model Subscription

Simon — Tue, 27 Nov 2018 10:05:59 GMT

I am currently looking into your problem and will try to provide you with an answer by Thursday.

RE: PyACI Serial Configuration and Model Subscription

AdamWaterman — Thu, 22 Nov 2018 16:05:40 GMT

sorry, accidentally posted before finishing the last question.
if this is the expected behavior then how are events addressed to different models in the PyACI because it clearly works for the ConfigurationClient Model.

Thankyou.