The reboot loop usually happens when the wifi is configured but the connection does not succeed for some reason. It behaves like a software watchdog, resetting the system in case of connection issues. Make sure you:
(a) have a supported wifi adapter (i.e. you're seeing it as wlan0 when issuing an iwconfig)
(b) you have a WPA-enabled network (as opposed to WEP)
(c) you have correctly set your wifi network details (check the /data/etc/wpa_supplicant.conf)

Of course you'll need to do all these using your working Ethernet connection and a remote login with SSH/putty.

htfb wrote:Like the look of this.

Have had software running from fresh image on SD card, with Ethernet connection. When I try to enable wifi from within software using web page, I add SSID and key, then click on Apply button. I then end up with endless loop where from watching RPi indicator lights, it looks like it is rebooting all the time. Am I missing something? (I've had wifi working with Raspian on another SD card, so the dongle is ok). Thanks

Following on from my failure to get wifi working, I have just re-read an older post in this thread that mentions that the SSID name should not have spaces - is that correct? My router has a name that contains two words with a space between them. This has worked with everything else since I got it!

Does the Wireless Network feature in the Advanced Settings section of the config work? I tried that but got into the endless reboot loop - maybe because of my SSID name containing a space?

Thaui - the response I hoped for would be for someone to confirm that a space in the SSID can be a problem. I do not want to change my SSID to test this because it then means my current setup would become unavailable to my family while I mess about with my RPi.

I have used my wifi USB dongle successfully with my RPi and Raspbian, using my SSID containing a space. To me, I should be able to use the same SSID with this software.

htfb wrote:Thaui - the response I hoped for would be for someone to confirm that a space in the SSID can be a problem. I do not want to change my SSID to test this because it then means my current setup would become unavailable to my family while I mess about with my RPi.

I have used my wifi USB dongle successfully with my RPi and Raspbian, using my SSID containing a space. To me, I should be able to use the same SSID with this software.

An SSID with a space does not work for me.
Without a space works perfectly!

I have released a new version. Here's what's new:
* full-screen camera frame fix when viewing a remote motionEye camera
* camera frames now indicate motion detection visually by turning to a redish color
* added minimum motion frames option support (in motion detection settings)
* max. motion threshold setting is now 20%, default event gap is now 10 seconds and default movie quality is now 85%
* added a visual feedback when shutting down from UI
* libjpeg turbo is now used to improve performance (thanks go to https://github.com/jjrojoc for the tip)
* logging and console login are now enabled on tty1 over the framebuffer (console on HDMI, in other words)
* SFTP is now enabled for easier access, using the root account
* the PI is rebooted if ethernet connection is lost for 20 seconds
* kernel updated to 3.12.34
* rpi-firmware & rpi-userland updated to latest versions

Updating to this version using the Software Update function is possible only from 20141123. Users of older versions need to write the image on their SD cards manually.

You have sufficient space and you can include the USB power supply as well in the box. This will avoid losses in the power supply cable. You also have sufficient space for a wifi adapter with external antenna. The second hole in the casing you can fix the antenna with some silicon. Another article is here but wih some other firmware which never worked reliable

If you have a Raspberry pi camera module, you might want to capture images using the 2592x1944 resolution. Currently, the highest selectable resolution in motionPie is 1600x1200. To enable the highest resolution, follow these steps:

1) Login to the Pi using Putty or similar software. User name: root, password: the last eight numbers or letters in the Pi name displayed in the top left corner of the motionPie interface.

6) Wait a minute or two, and when you log into the motionPie interface again the higher resolution should be available.

I have tested this using a Raspberry Pi model B with a wired connection, set to save a still image every 60 seconds. It works very well, with the preview window refreshing every other second or so. Thanks to ccrisan for providing me with the necessary information to test this. Hopefully the 2592x1944 resolution can be included in later versions of motionPie!

Santa's been busy working on a new version of motionPie: 20141228 has been released. I've been meaning to have it ready for Christmas but it seems I have underestimated the required work. The following changes have been made since the last stable version:
* The authentication mechanism has been completely rewritten and is now based on a request signature, rather than the good old HTTP Basic Auth. This not only improves security but also makes it compatible with most of the platforms and devices used these days.
* The v4l2-ctl program has been patched to work again. One of the users noticed it had been broken for a while. Real time video controls should work again.
* Drivers for the various USB ethernet adapters are now included.
* There's an FTP server enabled by default that accepts anonymous logins and allows easy downloading of media files.
* The writeimage.sh script has been enhanced to allow tweaking of SSH, SMB and FTP services. More precisely, it is now possible to enable/disable any of these services, make them require authentication or allow remote write access.
* When changing the admin password in the UI, the root password of the system is updated accordingly (by default it is still the S/N of the PI). This applies to all types of administrative logins and has been introduced for security reasons.
* The reboot button is back (some users seem to find it useful).
* The automatic brightness option is back as well (but don't blame me if it does not work as you expect).
* The number of files is now shown on the group button in the media browser.
* It is now possible to remove an entire group of media files using a big red "delete" button.
* The timelapse function has been rewritten to overcome some issues. It now works well for remote motionEye cameras and displays a progress bar to help estimating the remaining time to completion.

You will need to manually download and install 20141228, since it's marked as "prerelease". Santa might have had a few drinks while working on it and chances are that stability issues and other errors appear. Please test it as much as you can and come back with your feedback so I can fix any problems and release a stable version.

I'm having issues with the Samba setup on my Motionpie install. I've set it up to connect to my main PC (Ubuntu 14.10) which has an SMB directory set up, but the Motionpie install doesn't appear to mount it until I go into the admin page, make a superficial change to the config, apply it, then revert it back to the working config (very strange). It will then quite happily write to the directory on my PC (until I reboot either the Pi or the PC).

It's difficult to tell what the problem might be in these cases. There's one thing though, you have both "guest ok = yes" and "valid users = ben". Do you plan to use this share authenticated or not? What is your "map to guest" setting's value?

You can try to manually mount the share (from an SSH on your PI) and see what happens:

Make sure the mount succeeds and that the resulted mount at /data/media/some_dir is writable. Let me know of any errors that might be printed by the command.

130mbit wrote:Hi ccrisan, good work on motionpie!

I'm having issues with the Samba setup on my Motionpie install. I've set it up to connect to my main PC (Ubuntu 14.10) which has an SMB directory set up, but the Motionpie install doesn't appear to mount it until I go into the admin page, make a superficial change to the config, apply it, then revert it back to the working config (very strange). It will then quite happily write to the directory on my PC (until I reboot either the Pi or the PC).

Have only {"prompt": true, "error": "unauthorized"} text on firefox when trying to watch live feed on full screen window, whats wrong?
IE gives prompt do you want open or save frame.json from (ipaddress)