Heartbeat in IOS app with proxy node ( node alive )

[Nabil]

Hello,

I need to have connection status at the application level (IOS). 

I'm working with the example "light switch server proxy" where the heartbeat profile is working.

In the IOS application I have already implemented the message "heartbeat publication set message". With this message I can have my embedded module send its status periodically to 0xFFFF (all nodes). 

But the application does not receive the return status. I receive a unique return status when I configure the publication of the heartbeat.

Is it possible to configure the node to send the heartbeat value to the ios application ? It seems that the application is not in the destination nodes

My current step is : 

1. Configure the node with " CONFIG_OPCODE_HEARTBEAT_PUBLICATION_SET"

2. On the node in heartbeat.c -> 
static void heartbeat_publication_timer_cb(timestamp_t timestamp, void * p_context) is called periodically. 

3. On the app in AccessMessageParser I added the status in the switch case. But no status comes after the configuration.

Thank you very much. 

[Aleksander Nowakowski]

Hi,

This looks like a Proxy Filter thing. Are you using the latest version of the iOS library on version2 branch? If so, since few days the app is automatically subscribing to FFFF address (and unicast addresses of all elements on the local node) after connecting to the proxy.

Please, check the latest version. Together with this feature there came some updates to the API (delegates, sending messages, ...), but I hope they will not be a big issue for you.

BR,

Aleksander

[Nabil]

Hello, 

Unfortunately I use version 1.

I had to do an intermediate library to use it in C ++ with Qt.

Is there a migration guide from version 1 to version 2? The library look so different.

Thank you !

[Aleksander Nowakowski]

We don't have such guide yet, as the second version in under development. But as we're getting close to release, there will be docs on GitHub.

We highly recommend to migrate. Please, let us know what features do you miss.

[Aleksander Nowakowski]

Or, if you don't want to migrate, you may just add proxy configuration messages to version 1. You have to send them using type 0x02 (Proxy Configuration), not 0x00 (Network PDU).

[Nabil]

Hello, 

Thank you for your quick reply. 

Theoretically, that seems to be the solution. I have to try now to implement with version 1. I'll let you know.

[Nabil]

Hello, 

On the version 1 SetFilterTypeMessage.swift is already implemented. When I try to send a packet with ControlMessagePDU the packet is rejected by the embedded. 

In proxy.c config_packet_in(..) is called but config_packet_decrypt(&net_meta, p_data, length, decrypted_packet) return false. 

I have the same behaviour with my custom message : AddAddressToFilterMessage.swift

Was version 1 working with type 0x02 (Proxy Configuration) messages ? 

Thank you very much. 

[Aleksander Nowakowski]

Are they encrypted with the right nonce? The nonce type is different for proxy conf messages. I don't know had it work on version 1...

[Nabil]

Hi,

Unfortunatlty filter is not working .. maybe it's not possible on version 1...

[Aleksander Nowakowski]

Also, what you may find interesting, Add Addresses to Filter works only with maximum 5 addresses in the list. You may add more in following commands, but max 5 per message. Assuming you'll make this work at some point.

[Nabil]

Hello, 

Do you have a migration guide now ?