Can you access this orbiter using the Web Orbiter interface in a browser? Go to /lmce-admin/weborbiter.php

There are three points where weborbiter_command.php says 404:

- if the device_id is not given or empty- if the device given doesn't exist or isn't a proxy orbiter- if the Proxy_Orbiter DCE device can't be contacted (i.e. it's not running, it died, this kind of thing)

In addition to these, weborbiter_image.php says 404 if the image contents couldn't be retrieved.

I'd be looking to see if the Proxy_Orbiter device is running. It may have died 50 times. If a device dies 50 times, it will stay dead until you do one of these: 1. reboot or 2. delete the Generic Proxy Orbiter device number from /usr/pluto/locks/pluto_spawned_local_devices.txt and reload the router. Note how this is the child device's number. It's a bit confusing, but you get the hang if it.

Also, make sure you have the latest pluto-proxy-orbiter package. This package creates the /usr/pluto/orbiter/bits directory. Without this directory Proxy_Orbiter will die.

Good work, can't wait to update and have a play.Also just an FYI, the Dianemo app appears to not play nice with iOS5 :/

Slampt

Hi Slampt,

We new about the iOS5 issues but wanted to get the App out while we investigated them. We now have a build that fixes all of the known iOS5 beta3 issues and are testing that now. We will push that out to Apple for Approval later today if we're happy with it.

With v1.2 under iOS5 Beta3 you should find the display glitch is fixed by opening the connections screen and then returning to the Orbiter view using the Orbiter tab.