Auto connect after new code flash or bluetooth disconnect

[sloppycoffee]

I have been trying out this package on my raspberry pi3 and having a terrible experience.

First, it looks like after each flash, I have to kill bluz-gateway and restart it for Bluz to connect again.

The startup script doesn't seem to work and keeps crashing about some port bind error.

I wasn't sure if there is a forum or better spot to get some help with these items but wasn't to see if others are experiencing the same things.

I am going to order an official gateway from Bluz but would have liked to get it working on my pi.

[mumblepins]

Hey, sorry to hear that you had a bad experience. The bind port error is a result of the port that the GW is trying to open for the info server already being used by another program, either the gateway itself that may still be running or Linux hasn't fully cleaned up, or another server entirely. The port can be changed in ~/.bluz-gw/config.json. In addition, while in the config file could you change the logging level to debug, and then upload a copy of the log file? If you're running off the startup script, it should log to /var/log/bluz-gateway.log, if you're just running it directly, it just writes to stdout and stderr.

[sloppycoffee]

I have been doing my development with the official gateway and about to finish up. Week or so. I will then move back and work with the Pi and provide you with a log file.