COMPONENTNAME_NOT_FOUND when sending update
Okay, I am running out of ideas on this... I am trying to develop a driver that exposes different devices of the same type, discovered via callback passed into enableDiscovery. The device itself has registered a few text labels which I want to update dynamically. From time to time, this seems to work, but most of the time it doesn't, and I am getting a "Error: COMPONENTNAME_NOT_FOUND <my_label_id>" error, for components that worked before.
Having debugged into this a little bit, it seems as if `_fetchDataFromBrain` is unable to retrieve the correct data from the brain - when I run the corresponding GET request from the command line - something like `curl "http://NEEO-7f8fef5b.local:3000/v1/api/notificationkey/src-d44c95152c88baebd73222b0f68b3066fce993a3/apt-f92962c314d1743f462f6016aab202bb6eae92e8/1601c0d699a6d6c6ec4084c473fbc58d1f08"`- I get back a 200 OK with an empty response.
Any suggestions?
-
Boris Pruessmann
I have a similar problem mentioned here https://planet.neeo.com/t/x1ppnc/componentname_not_found
-
Are you sure it's working for you with just one component, Paul ?
-
Boris Pruessmann
I define two different types of WeMo switches. If I pass back the definition of one device, either one, the code works perfectly. If I pass back both, I get this error.
The error always refers to the component in the first device even when I only add the second device on the Brain.
-
Okay. Found a solution to my problem: restarting the brain...
-
Boris Pruessmann
Was that with the devices already added or did you do the discovery and added the devices after you rebooted the Brain?
Did you restart the server (SDK) after rebooting?
-
Paul Spee
Deleted the device, rebooted the brain, restarted the SDK, and re-added the device. Afterwards things behaved as expected.
-
Boris Pruessmann
Interesting. I will give it a try.
-