Hmm, I've just tested this on the gentoo box and it works just as it is supposed to. The raspbian device is not available, as it went into the PiGI test. Did you install the packages (bottle/gevent) via apt-get or via pip? Do you know which versions of gevent/bottle are installed? Also, could you test if it works with chromium, so that we can exclude any client induced issues.

from picoreflow.

I installed via pip, I checked and none is installed via apt in parallel.
pip gives this version info for the installed packages:

root@egpi:~# pip freeze
Warning: cannot find svn location for distribute==0.6.24dev-r0
RPi.GPIO==0.5.7
argparse==1.2.1
bottle==0.12.7

# FIXME: could not find svn URL in dependency_links for this package:

distribute==0.6.24dev-r0
ez-setup==0.9
gevent==1.0.1
gevent-socketio==0.3.6
gevent-websocket==0.9.3
greenlet==0.4.5
kr-gevent-websocket==0.4
numpy==1.6.2
pifacecommon==4.0.0
pifacedigitalio==3.0.4
pygame==1.9.1release
pygobject==3.8.2
pywsgi==0.9.0
websocket==0.2.1
wsgiref==0.1.2

from picoreflow.

I've tested on gentoo and on raspbian on the pi, both times I could not reproduce the error. Both times simulation mode only. I don't believe that it will behave differently but I'll have to rig the other pi with the new image to be sure that the results are the same while interfacing real hardware .

This is the pip freeze from raspbian with some older deps (working):

root@raspberrypi:/opt/picoReflow# pip freeze
RPi.GPIO==0.5.3a
argparse==1.2.1
bottle==0.11.6
distribute==0.6.24dev-r0
ez-setup==0.9 
gevent==0.13.8
gevent-websocket==0.3.6
greenlet==0.4.1
leveldb==0.191
numpy==1.6.2
pifacecommon==3.1.2
pifacedigitalio==2.1.0
pygame==1.9.1release
wsgiref==0.1.2

After upgrading all required deps to present pip delivery (still working).

RPi.GPIO==0.5.3a
argparse==1.2.1
bottle==0.12.7
distribute==0.6.24dev-r0
ez-setup==0.9
gevent==1.0.1
gevent-websocket==0.3.6
greenlet==0.4.5
leveldb==0.191
numpy==1.6.2
pifacecommon==3.1.2
pifacedigitalio==2.1.0
pygame==1.9.1release
wsgiref==0.1.2

Now, being no python expert and not being able to reproduce locally, I would go with a hunch:

In your pip freeze I find kr-gevent-websocket. This reads awfully close to gevent-websocket (required) and I don't know or have this one on any of my test or production systems. If you can, could you try to temporarily remove it (depending on why you have it there in the first place) and see if it works then? That would at least move us forward to isolating the issue.

from picoreflow.

I've also updated the README to make the installation process a bit more clear (for your reference as well)

from picoreflow.

Thank you for the kr-gevent-websocket tip. I removed it, than gevent-websocket was not found anymore. Than I also removed gevent-websocket and reinstalled it! Now it seems to work.
The only missing things are some hardware parts, which are on there way from china (-:

from picoreflow.

Sweet :)

from picoreflow.