I've programmed buttons on a Hub LR with an Internet Request posting a JSON message to one of our servers. It worked as intended.
Came back a few weeks later, didn't work anymore (no changes). Added a second button with similar programming, also not working.
I reset the hub, programmed one, working again. Programmed 29 more in a similar fashion, moved the hub out to production within 10 minutes (so with a power cycled), and none of them worked anymore.
Thinking the hub is bad, I tried the same with another hub, and first it's working, programmed 10 buttons, after power cycle again not working. Tried "jump starting" it with various methods, like adding more buttons, removing, changing settings, no luck, The hub itself seems to register the button push as the LED flashes and the button icon in the app wobbles.
When using the SDK to submit a similar request on a "working" hub (essentially the example from the SDK tutorial at https://hubsdk.flic.io/static/tutorial/), it also works fine and I get status code 200 back, as expected.
When I run the same code in the SDK on a "malfunctioning" hub I get this error as a result:
TypeError: cannot read property 'statusCode' of undefined
at [anon] (duktape.c:56634) internal
at [anon] (root/test1/main.js:37)
at handleResponse (http.js:62)
at handlePacket (pipe_communication.js:56)
at readCallback (pipe_communication.js:93) preventsyield
Anybody experienced something similar to this?
We have a bunch of other flic hubs in use that do not seem to have that problem. I'm not sure if it's something I am doing, but the only action between it working and not working is a power cycle. Quite annoying and ready send 16 packs of buttons back to them.