Open guysoft opened 7 years ago
Ok, bluez now reconnects on connection fails, however it seem like after a few minutes the beddit stops working and timeouts, and the only way to fix it is restarting. In the README there is a documentation about a CONT variable, will try that.
Merged auto_connect branch to devel, its better than what was there
ok, good news - I gave up on making the remote connection stable, we are going to use a relay to turn the beddit on and off. Its been running for over 24 hours, so I merged the relay branch to devel.
The current solutions are either using a ORVIBO WiWo-S20, which has several implementations to be controlled, or just have an RF connection to the pi. I am using the Pi GPIO now to test, while I ordered a ORVIBO WiWo-S20. There is a new config.ini which lets you set which relay is being used.
Ok, added support to ORVIBO WiWo-S20, a web service, and db all check out. This should be deployable at the need-knower's house. However setup has some requirements. So we will need to figure that out. cc @arnonzamir
Continuing the talks at #1 Started with @arnonzamir The proof-of-concept it working nicely, however we need the pi to handle communication exception and basically crash as little as possible.
work is done in the auto_connect branch
The main issues at the moment are:
Migrate from python-serial to python-bluezdoneHandle "device resource is busy" errorsDoneHandle "invalid CRC" messages that are a result of not all the packets arriving on timedoneHandle "Host is down" errors that happen when the bluetooth device (beddit) is not visible to the piDoneHandle beddit diying after 30-60 mins and require restartHave a running service on the piDone