Issue with timebox itself

[TonyFeestneus]

Can you prevent it from displaying the Bluetooth logo continuously?

I have succesfully sent images to the Timebox Mini from Raspberry, but then Bluetooth logo comes on and off.

[ScR4tCh]

Hi I currently have little time to work on this. In my current local development version the script is able to keep the socket open, which should prevent this behaviour. I'll try to commit this soon after reviewing my changes (been some month since I did this ;))

[TonyFeestneus]

That's great (for others: I returned mine since the connection distance was too low for my use, plus the Bluetooth logo was a real issue). Perhaps I'll reconsider if you get that fixed.

But does it allow other BT connections then as well? Or does your script consume the complete bluetooth stack, as in: I can't ping for other devices anymore?

[ScR4tCh]

I have not tried yet, but I bet no other connection is possible when the socket stays connected (Speaking of the timebox, I guess that your local bt device should be able to handle that, maybe depending on the "stack" used). I'll give this a try, now I am courious about it ;).

[Leiknir]

Hi @ScR4tCh,

Thanks a lot for the CLI!

Any news about the update where the socket connection would be kept open? Not long ago I've also purchesed a Timebox, and this issue is a bit annoying.

[ScR4tCh]

@Leiknir
You can keep the connection now "open" at os level using --keepconnected, this speeds up sending to a device multiple times as well.

[ScR4tCh]

Next step could be to keep the cli running and connected ;) till the user aborts execution. This might however be an use case for a service or gui app ;)

[indeed-a-genius]

I get disconnected after ~30 secs (BT icon starts blinking) after running a command, regardless of the --keepconnected option.
I'm considering a cronjob, setting the correct time every 30 secs to avoid that, but BT icon appears every time I send a command, so that's distracting :/

[Yottster]

@indeed-a-genius #13 should give you a hint