Best way to detect LR device in driver?

So two fold question. I just discovered (duh) that associations don't work if the device is in LR mode, the ZEN37 literally wont even accept association group settings. Is there any other things that might need to change in a driver when paired as LR?

Main question, what the best way to detect this? The easy way seems like it would be to just check the DNI and if its > 255 then its LR. Seems like a hack to me though, but might be the only way. Might be hidden in command class as well.

1 Like

Why? Mesh will never be >255, and LR will never be <255. Seems like a perfectly valid way of doing it.

I try to avoid relaying on data that can be modified or missing, but really that DNI should be pretty safe since if someone messes with it, they break the device. I just was not sure if there was a better proper way built into the hub. Otherwise just going to make my own function Boolean isLongRange()

Its sort of like relying on the clusters to determine if a device is battery, multichannel, or power reporting. Far better to just ask the device directly using the proper command classes.

1 Like