Closed andersdd closed 5 years ago
Hi @andersdd,
Do you have any other programs / cronjobs / daemons that are trying to access the blink(1) device? Or, could the cable or USB hub the blink(1) is plugged into be faulty? If Blink1Control2 cannot access the blink(1) because another program like blink1-tool
is controlling it, then it will show as disconnected.
You may be able to see some error messages by opening up Developer Tools by going to the "Blink1Control2", choosing "Toggle Dev Tools", and then clicking on the "Console" tab. Check this after a disconnect and see if anything obvious is printed out.
Thanks for the near-immediate response. I do have blink1-tool triggering on a regular basis but that turns a pattern on then off after a second or so.
Further testing indicates as soon as a bash script calling blink1-tool runs, the device is immediately disconnected from the Control application.
Is there no way for the Control application to retain the connection?
If you're running the Blink1Control2 app, then you can use either blink1control-tool
command-line program that works almost identically to blink1-tool
and uses the HTTP REST API in Blink1Control2. Or you can issue those REST calls yourself.
The REST API is documented here:
And you can get blink1control-tool
in the releases page. It's not changed recently, so the last release is here:
Thank you for the explanation and offering a potential solution. Closing issue.
BTW absolutely love my blink1 devices
Installed Blink1Control2 on Ubuntu 18.04 without issue. I already have blink1-tool setup and scripts talking with the blink1 device so udev rules and everything else works.
On initially plugging the blink1 into a USB port, the Blink1Control recognises the device and the sample buttons and patterns work. I have also connected Alexa and got that working.
However after a few minutes the Control application loses connection (?) with the blink1 device and I see "no device connected". The blink1-tool can still send commands to the blink1 device successfully. Unplugging and replugging the device means it shows up in Control for a few more minutes until disconnecting again.