I'm using the DeviceNotesHelperRK to fetch configuration for my devices. It was working fantastically for months, then last week (i think) something happened. I don't think on my end as i haven't touched that part of the code. But when ever a device goes to fetch DeviceNotesGet it will go to any or all devices. which has broken all of my deployed devices. with them getting random configs. It took a while but i think i found that issue with the webhook from the portal.
According to the documentation you can specify that only trigger device will receive a response. which is set by default. Something has unset it for me, and i cant seem to reset it.
I don't see how this ever worked properly before. I uploaded version 0.0.3 with a fix to the subscription code.
Also make sure your responseTopic is {{{PARTICLE_DEVICE_ID}}}/DeviceNotesResponse, including the Device ID and a slash.
However you should not use this library. You should use Ledger which is built into Device OS and the Particle platform and is a much better way to store configuration settings.
Thanks, i wrote this my code pre ledger. I managed to include the Device ID in the return message and do a ID validation. but V0.0.3 will help alot. but i will look into migrating to ledger Thanks
@Alont I would second the Ledger use for configuration - it by far a better approach but does require different design thinking.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.