dgrant / eyefiserver2

A standalone Eye-Fi server in Python, for Linux

eyefiserver2's Issues

credits where credits due

the original post of Jeff Tchang is still here
http://returnbooleantrue.blogspot.nl/2009/01/eye-fi-standalone-server.html

Eye-Fi Mobi working?

Hi,
is the new Eye-Fi Mobi Card working with this tool?
There is no upload-key.

where is getting started?

I was curios the info page says to read the getting started but I do no see this? Also want to ask, can this py code be built on a windows box or is everything here for linux.

Direct Mode

Are you aware if the SOAP messaging is the same over standard WiFi or the "Direct Mode"? It seems that Direct Mode is a little less flaky than standard WiFi so I would like to use that but I don't want to waste time trying something that isn't implemented.

Also, do you know if there is a call that can be made from the server to the card, sort of like a ping, that might be able to tell the card that it's time to sync up?

Permission of folders

When new folders need to be created, the ownership is of the user running the server, not what is entered as uid and gid in the config file.

Here's the config from /etc/eyefiserver.conf:

upload_dir:/path/to/pictures/%%Y/%%m/%%d

I wanted my images to be organized in subfolders, as you can see. But only the last part (%%d) has the right ownership (65534 in my case). %%Y and %%m both have 0, the user under which the server is running.

I'm using a QNAP SS-439 if that's of any relevance.

.deb/.rpm packages

Upload stops in middle of POST

I'm trying to configure a Pro/x2 16gb card to connect to my Synology Diskstation 410j. I got the software installed and the card is able to connect to the diskstation, but it keeps freezing in middle of POST. Any suggestions welcome.

Here is the log file

[12/25/13 10:38AM][runEyeFi] - Eye-Fi server started listening on port 59278
[12/25/13 10:40AM][get_request] - Incoming connection from client 192.168.1.10
[12/25/13 10:40AM][do_POST] - POST /api/soap/eyefilm/v1 HTTP/1.1
[12/25/13 10:40AM][do_POST] - Headers received in POST request:
[12/25/13 10:40AM][do_POST] - content-length: 412
[12/25/13 10:40AM][do_POST] - soapaction: "urn:StartSession"
[12/25/13 10:40AM][do_POST] - connection: Close
[12/25/13 10:40AM][do_POST] - accept: text/xml, application/soap
[12/25/13 10:40AM][do_POST] - user-agent: Eye-Fi Card/5.2010
[12/25/13 10:40AM][do_POST] - host: api.eye.fi
[12/25/13 10:40AM][do_POST] - Attempting to read 412 bytes of data
[12/25/13 10:40AM][do_POST] - Finished reading 412 bytes of data
[12/25/13 10:40AM][do_POST] - Got StartSession request
[12/25/13 10:40AM][startSession] - Delegating the XML parsing of startSession postData to EyeFiContentHandler()
[12/25/13 10:40AM][startSession] - Extracted elements: {'transfermode': u'33314', 'macaddress': u'001856630ce9', 'cnonce': u'883403605e33f4393654e82a4b84b20f', 'transfermodetimestamp': u'1387850540'}
[12/25/13 10:40AM][startSession] - Got MAC address of 001856630ce9
[12/25/13 10:40AM][startSession] - Setting Eye-Fi upload key to 87aabac93bf48dd147d3fb0322137ea0
[12/25/13 10:40AM][startSession] - Concatenated credential string (pre MD5): 001856630ce9883403605e33f4393654e82a4b84b20f87aabac93bf48dd147d3fb0322137ea0
[12/25/13 10:40AM][do_POST] - StartSession response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">SOAP-ENV:Bodyfab405b1f04dd6e282fa1f1dd4d3492499208c155fc1883579cf0812ec0fe6d221230268824false/SOAP-ENV:Body/SOAP-ENV:Envelope
Eye-Fi-630ce9.home - - [25/Dec/2013 10:40:14] "POST /api/soap/eyefilm/v1 HTTP/1.1" 200 -

Install problem on Synology NAS (DS214play)

Hi, just followed the howto on the wiki to install on my new NAS.
I get to the point where I start the daemon with
/usr/local/bin/eyefiserver.py start /etc/eyefiserver.conf /var/log/eyefiserver.log
It shows in /var/log/eyefiserver.log that [12/10/13 10:52PM][runEyeFi] - Eye-Fi server started listening on port 59278

However, no activity, even when taking pictures, taking the eye fi card on and off.
Any help ?

Log file rotation should be taken care of by logrotate

See comment from here: https://code.google.com/p/eyefiserver/issues/detail?id=5#c1 which I agree with: "I'm not sure I want that here. IMHO log rotating should be done by the server maintainance scripts, like logrotate."

It was me who originally committed the log rotation but I agree, that using logrotate is better.

Need to add SigUSR1Handler so that we can handle the SIGUSR1 signal that logrotate uses (this is too avoid using copytruncate option of logrotate which can potentially lead to loss of somes lines of the log).

Changing Listen Port

I have tried to change the Listening Port but if I change from the default one (59278) the images are not downloaded.
Anyone ha any hint in solving this problem ?
Thank you
Luca

Card does not connect to the Eyefiserver2

Hi,

Apart from retreving the mac ID and the uppload key from the Windows xml settings file and close down the windows server is there anything more that has to be done for the card inorder to have it work with eyefiserver2? E.g. where does one configure the card to comunicate with the machine that runs the eyefiserver2?

The only thing that I see in the log file is that the eyefiserver2 is started and listening on the port 59268. No connections from the card or upploading of pictures.
B.t.w I'm running the eyfiserver2 on linux mint 17.3, running python 2.7.6.

Optware

I just upgraded my QNAP & had to reinstall the Eye Fi server (0.0.17). but it appears that Optware isn't in the QNAP App Center anymore. Do you know if there is anyplace to get it, or if there is a substitute?

Incompatible with latest QNAP firmwares

Optware was removed from the app center and therefor can't be installed anymore. This makes this incompatible.

As an alternative this should better rely on the newer Qnapware: http://apps.qnap.community/11-community/10-qnapware which still has to be installed manually, but the packages are more up to date.

Also optware isn't available for manual installation anymore as well.

EyeFi Mobi Pro Support?

Hi there,

I have both the original EyeFi Pro X2 as well as the newer EyeFi Mobi Pro cards. While the eyefiserver2 works with the original EyeFi Pro X2 card, it does not work at all with the EyeFi Mobi Pro card, as far as I can tell.

I assume this is expected behavior, since Mobi uses the EyeFi Helper software for the EyeFi Pro X2 cards, while they use the newer EyeFi Mobi software for the newer cards.

Can you confirm this is the case? If it is there any potential for getting this to work with the newer Mobi cards?

Thanks!

Eye-Fi ending pre-2015 products

Eye-Fi is ending support for all pre-2015 products. They are claiming it's due to security issues, but since there have not been any changes in https nor WiFi encryption, no one belives them. It's more likely an attempt to restructure their revenue model in light of their sale to Ricoh. Basically, the MBA-types trying to force people into their cloud services.(paid Eyefi Premium accounts)

After September 16, 2016, the servers that Eye-Fi Helper needs to access when you configure these cards will be shut down. That means, after September 16, 2016, you won't be able to reconfigure any pre-2015 cards, and they will only be able to direct download to your local Eye-Fi server. (i.e. Direct Mode) I'll reproduce their email with the list of end-of-life products below.

So my main question is, do you know how to reconfigure cards? I've looked at the card configuration files (REQC, REQM, RSPC, RSPM) and can't make heads or tails of them.

What the Eye-Fi community can really use is

1. A stand alone card configuration utility for Windows & Mac.
2. The porting of your server in this github repository to Windows & Mac.

Anyway, here's the email the sumbags at Eye-Fi sent out:

o Our Eye-Fi X2 and Earlier Generation Product Customers
View this email in your browser

June 30, 2016

To Our Eye-Fi X2 and Earlier Generation Product Customers:

This message is for customers that purchased an Eye-Fi Pro X2 or earlier generation products prior to March 2015. Effective today, June 30th 2016, we will no longer be offering support for our legacy product lines, a complete list of which appears below. This notice formally begins the final stage of the “end-of-life” (EOL) process started in mid-2015 for the affected products. It’s very important that customers cease using these products no later than September 16, 2016 as some key services these products rely on will be shut down at that time. All customers who have a Mobi or Mobi Pro products purchased since 2013 are not affected by this announcement.

We began EOL on these product lines in 2015 largely driven by technological obsolescence of some of the key technologies included in these products. The primary technologies relate to Internet security and authentication mechanisms that were state-of-the-art in 2007 when we built them into our products but have since proven to be vulnerable. Since mid-2015 we have been offering migration services free of charge for Customers who have paid Eyefi Premium accounts. We will continue to offer this service migrating your Eyefi View data to Eyefi Cloud. You can request a migration here. For those customers that wish to use an Eyefi Mobi Pro card in place of their earlier generation products, we have also made a limited quantity available at a deep discount, see details here if you wish to take advantage of this offer.

Please note that we will maintain our customer service Web site and content for all customers. The support site includes detailed explanations for how to accomplish migration to Eyefi Mobi/Mobi Pro and Eyefi Cloud services. We are grateful to all the customers around the world that used Eye-Fi products in the past as well as for our newest customers. The EOL of a product line is always difficult and we have made every effort to minimize the impact of this change on our customers. Thanks for your loyalty and understanding.

LISTING OF IMPACTED PRODUCTS

Customers with Eye-Fi 1.0 product line and Eye-Fi Premium subscriptions will be impacted by this EOL process. Effective September 16, 2016 the following products may no longer operate:

Eye-Fi 1.0 Products:

All original pre-X2 products (Original, Home, Share, Explore, Video Share, Video Explore, Pro)
4GB Geo X2
4GB Connect X2
8GB Explore X2
8GB Mobile X2
8GB Pro X2
16GB Pro X2
Visioneer X2
Sandisk X2
Eye-Fi Windows desktop software (Eye-Fi Center)
Eye-Fi Mac desktop software (Eye-Fi Center)
Eye-Fi app for iOS
Eye-Fi app for Android
Eye-Fi Center web app (center.eye.fi)

The Mobi, Mobi Pro and Eyefi Cloud products and applications are unaffected and will remain operational with continued future developments.

Frequently Asked Questions

I just purchased an X2 card, why isn’t it supported?

Eye-Fi began phasing out sales of the X2 product line in 2012. The last version produced by the company were sold through authorized channels in the United States in March, 2015. Although Eye-Fi stopped shipments of these products via authorized channels, some units were still available from third party sellers and after-market resellers. Eye-Fi’s warranty period for the affected products purchased through our authorized channels has expired.

Will I still be able to create an Eye-Fi Center account after September 16th?

No, you will not be able to create an Eye-Fi Center account or log in to an existing Eye-Fi Center account.

Can I still download and install Eye-Fi Center applications after September 16th?

The Eye-Fi Center applications can be installed, but since account creation and logging in will no longer work, these applications will not be functional.

Will I be able to use my Eye-Fi 1.0 card after September 16, 2016?

Certain functions, such as Direct Mode, may not be directly impacted by our end of life process. If you wish to try Direct Mode you will need to set it up prior to the end of life date. You can find instructions on how to set up direct mode here for Android and here for iOS. Please note that while Direct Mode may not be directly affected, Eye-Fi applications will no longer be updated for operating system updates, and their functionality is not guaranteed - additionally, no support will be provided either for the setup or functionality of Direct Mode. THERE IS NO GUARANTEE THAT DIRECT MODE CONFIGURATIONS WILL CONTINUE FUNCTIONING AFTER THE SEPTEMBER 16, 2016 SHUT DOWN.

For an extended FAQ, please see here. http://x2migration.eyefi.com/hc/en-us/articles/216741158

Python Version

Seems to be it doesn't like python version 3 or greater?

way to improve script to detect new python version not supported? or update code to be python 3 compatible?

Communication seems to work but no upload

Hi,

I'm a newbie in Linux and with this anyway. My Eyefi card ain my camera seems to communicate but it doesn't seem to upload any picture, not in the default directory nor any other.

This is the screenshot from the Server - what am I doing wrong ?

s1:StartSession>/SOAP-ENV:Body/SOAP-ENV:Envelope
[11/26/15 09:21AM][do_POST] - Got StartSession request
[11/26/15 09:21AM][startSession] - Delegating the XML parsing of startSession postData to EyeFiContentHandler()
[11/26/15 09:21AM][startSession] - Extracted elements: {'transfermode': u'16418', 'macaddress': u'00185621140b', 'cnonce': u'c166667ce6dba80a7281b17bd75fe55e', 'transfermodetimestamp': u'1448406154'}
[11/26/15 09:21AM][startSession] - Setting Eye-Fi upload key to c686e547e3728c63a8f78729c1592757
[11/26/15 09:21AM][startSession] - Concatenated credential string (pre MD5): 00185621140bc166667ce6dba80a7281b17bd75fe55ec686e547e3728c63a8f78729c1592757
[11/26/15 09:21AM][do_POST] - StartSession response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">SOAP-ENV:Body5d1382e08a89c2a367b2d1095a1df8c93b7674c8e07db92df6c098d9fcd742b2164181448406154false/SOAP-ENV:Body/SOAP-ENV:Envelope
192.168.1.110 - - [26/Nov/2015 09:21:07] "POST /api/soap/eyefilm/v1 HTTP/1.1" 200 -
[11/26/15 09:21AM][get_request] - Incoming connection from client 192.168.1.110
[11/26/15 09:21AM][finish_request] - Creating instance of main.EyeFiRequestHandler to service request from ('192.168.1.110', 8578)

Latest eye-fi firmware doesn't play nice with eyefiserver2?

See this bug on eyefiserver project:

https://code.google.com/p/eyefiserver/issues/detail?id=8

Can't stop server

eyefiserver2 can't be stopped using init.d script (needs to be -9'd). This only seems to apply after a photo has been uploaded. If not uploading has occurred then it will shut down.

after eyefi server down

hello,
can this used after eyefi shutingdown the server?

QNAP Python 2.7 Package vs. Optware

Hi,

I tried to instal 0.0.17 on my QNAP NAS.

I'm getting an error message telling that Optware is needed. I already have the Python 2.7 packages installed is that not sufficient?

Thanks
Jan

EyeFiServer 0.0.17 installation failed. The following QPKG must be installed and enabled: Optware | opkg, Python >= 2.5 | OPT/python, Optware | opkg.

Movies will not upload fully

I use my camera with an Eye-Fi card to take pictures and movies. The pictures seem to upload but the movies don't see to fully upload. The log file looks good but the file is way too small.

Here is a snippet from the log..

[01/31/16 02:12PM][do_POST] - Attempting to read 2124548035 bytes of data
[01/31/16 02:12PM][do_POST] - Finished reading 2124548035 bytes of data
[01/31/16 02:12PM][do_POST] - Got upload request
[01/31/16 02:12PM][uploadPhoto] - multipart/form-data; boundary=---------------------------02468ace13579bdfcafebabef00d
[01/31/16 02:12PM][uploadPhoto] - ['multipart/form-data', ' boundary=---------------------------02468ace13579bdfcafebabef00d']
[01/31/16 02:12PM][uploadPhoto] - Extracted boundary: ---------------------------02468ace13579bdfcafebabef00d
[01/31/16 02:12PM][uploadPhoto] - Available multipart/form-data: ['SOAPENVELOPE', 'FILENAME']
[01/31/16 02:12PM][uploadPhoto] - SOAPENVELOPE: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:
[01/31/16 02:12PM][uploadPhoto] - Extracted elements: {'macaddress': u'00185648f664', 'filename': u'00178.MTS.tar', 'filesize': u'2124547072', 'filesignature': u'35310000
[01/31/16 02:12PM][uploadPhoto] - Using uid/gid 1024/100
[01/31/16 02:12PM][uploadPhoto] - Using file_mode 442
[01/31/16 02:12PM][uploadPhoto] - Using dir_mode 509
[01/31/16 02:12PM][uploadPhoto] - Generated path /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][uploadPhoto] - Opened file /volume1/apps/tmp/00178.MTS.tar for binary writing
[01/31/16 02:12PM][uploadPhoto] - Wrote file /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][uploadPhoto] - Closed file /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][uploadPhoto] - Extracting TAR file /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][uploadPhoto] - Creating folder /volume1/Photos/Eye-Fi/2015/Dec 25, 2015
[01/31/16 02:12PM][uploadPhoto] - imagePath /volume1/Photos/Eye-Fi/2015/Dec 25, 2015/00178.MTS
[01/31/16 02:12PM][uploadPhoto] - Closing TAR file /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][uploadPhoto] - Deleting TAR file /volume1/apps/tmp/00178.MTS.tar
[01/31/16 02:12PM][do_POST] - Upload response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-E
192.168.1.171 - - [31/Jan/2016 14:12:45] "POST /api/soap/eyefilm/v1/upload HTTP/1.1" 200 -

It was first writing to /tmp which I thought maybe there isn't enough space so I now have a tmp directory on my /volume1
I commented out where the script deletes the tar file and I see that it is only 34kb (34,304) in size and I am unable to open the tar file

Any help would be greatly appreciated.

File mode in decimal

The file mode in configuration file is noted in decimal... It took me quite a while to figure this out as in all other unix applications filemode is noted in octal (e.g. 755, 644, ...) or a character representation (u+rw).
At the least it should be documented in the example configuration so that an octal->decimal conversion can be made by the user.

Cheers!
-Robin-

how to set file/folder rights?

Hi,
I set up a debian box on raspberry pi for that purpose. pics upload nicely to a local folder on the raspbian box.
I tried to mount a NAS folder, which seems to work fine when browsing, using /etc/fstab

Should eyefiserver be run with the same user ? root ?
the thing is that the pics get dropped in /tmp but not to the final destination ...

FIle owner problem

Just noticed, if file UID=0, it is not set, properly.
I have by default admin/admininstrators (UID/GID=0),
The owner/group for .jpg and .log became eyefi/administrators (UID=502/GID=0). but XMP have no this rights issue. As soon as GID/SID changes, all three files get the correct GID.

In-memory TAR file management

This was reported on the original eyefiserver project:

A simple enhancement to avoid some filesystem and disk IO using cStringIO to manage TAR file in-memory (and extracts images only, avoding embedded logs)

See diff here:
https://code.google.com/p/eyefiserver/issues/detail?id=3