I am looking for getting the following setup working:
- physical watch
- "phone" part running on a server instead of phone.
The closest thing that I could find is running pebble install --emulator <name>. This runs the phone part of the app on the server via pypkjs but (I think) this is hardcoded to be running with a simulated watch via QEMU.
What I would love to have is a setup that allows for a physical watch instead (eg using a serial port).
I think that this scenario would be very useful both for development and live scenarios since then no phone needs to be involved.
I have been scanning through the code a bit and it looks like it shouldn't take too much changes to support this. The main thing that seems to be different is that it needs to manage connections whereas the QEMU variant does not (although it would be useful in this variant too).
Would love to hear your feedback on this. (Also it's very well possible that this is already possible and that I simply haven't come across it yet.)
I am looking for getting the following setup working:
The closest thing that I could find is running
pebble install --emulator <name>. This runs the phone part of the app on the server viapypkjsbut (I think) this is hardcoded to be running with a simulated watch via QEMU.What I would love to have is a setup that allows for a physical watch instead (eg using a serial port).
I think that this scenario would be very useful both for development and live scenarios since then no phone needs to be involved.
I have been scanning through the code a bit and it looks like it shouldn't take too much changes to support this. The main thing that seems to be different is that it needs to manage connections whereas the QEMU variant does not (although it would be useful in this variant too).
Would love to hear your feedback on this. (Also it's very well possible that this is already possible and that I simply haven't come across it yet.)