So it seems I've cracked it now. There were two problems. One is that I'm using the VAMP image as a base, and had to upgrade the Debian distro from Debian 6 to 7 to get all the Bluetooth utilities. This changed the behaviour of the network interface up script, so it was getting called twice, therefore kicking off the VAMP startup script (and my Bluetooth and SqueezeLite scripts) twice. That meant changing the script logic a little so it would only run once at startup.
The second was just allowing time for the connection before starting SqueezeLite, so I added a sleep command to sleep for 5 seconds before bluez-test-audio connect and then 1 second afterward before getting into the SqueezeLite monitoring loop, and now it seems pretty robust. Thanks for all the help. Two track 1's and no track 2 after a scan for new and changed? Please vote for serious scanning bug '17782' (http://bugs.slimdevices.com/show_bug.cgi?id=17782) Receiver stuck at blue LED state after reboot? Please vote for bug '17462' (http://bugs.slimdevices.com/show_bug.cgi?id=17462) ------------------------------------------------------------------------ paulster's Profile: http://forums.slimdevices.com/member.php?userid=23073 View this thread: http://forums.slimdevices.com/showthread.php?t=101872 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
