Trying to run light lightness application

RE: Trying to run light lightness application

Hung Bui — Thu, 22 Aug 2019 12:23:27 GMT

Which destination address you used to send the data to ? Have you made sure the server subscribed to the address you sending to (unless you are sending to the unicast address). They should be provisioned in to the same network.

I would suggest to use the access layer directly to send test message. This mean you ignore the model layer. You can enable logging inside the access layer to see if the packet arrive at the destination.

I assume you have tested the generic onoff example ? You can do your test (sending packets on access layer) on the generic on off example first before continue.

RE: Trying to run light lightness application

shreyab — Thu, 22 Aug 2019 09:19:01 GMT

light_lightness_actual_set() gave a timeout error true, but set_unack() message also didn't the server.

how can we debug server not receiving any client commands? i don't get any RX either on the server side, are the packets being dropped? is the server not recieving them at all?

RE: Trying to run light lightness application

Hung Bui — Wed, 21 Aug 2019 08:58:23 GMT

You mean only the lightness_actual_set() caused timeout error ? If it's the case, most likely it's the server didn't reply to the client. Please make sure you implement the code to reply when you receive a set command. Please refer to the generic on off model.

Also you need to check if the server is actually received the set command.

RE: Trying to run light lightness application

shreyab — Tue, 20 Aug 2019 16:29:59 GMT

no, sorry my bad didn't write that correctly, set message gives the timeout error

RE: Trying to run light lightness application

Hung Bui — Tue, 20 Aug 2019 14:11:10 GMT

I would suggest you to get familiar with the generic on/off model first.

You can find out if a packet is sent by enabling log level to DBG1: LOG_LEVEL_DBG1 and allow logging from ACCESS library: LOG_SRC_ACCESS. You should be able to see if the packet is sent (look for "TX:" ) and when a packet is recevied ("RX")

An unack message shouldn't cause a transfer timeout, I'm not sure why that happens, could be related to how you implement your model. What exact function throws that error ?