Sunoo / homebridge-ftp-motion

Converts FTP uploads into HTTP motion alerts that homebridge-camera-ffmpeg understands
BSD 2-Clause "Simplified" License
7 stars 1 forks source link

Setup instructions #161

Open P-Mass opened 2 years ago

P-Mass commented 2 years ago

Hello, and thank you so much for this plugin.

Being very new to GitHub, I hope that I am communicating this "issue" in the correct way.

I'm using the Homebridge Camera FFmpeg plugin with the "Enable motion sensor" selected, but even though I have set up an automation in HomeKit (using the camera motion sensor) the motion detection is not communicated to homeKit through this plugin.

I am now trying your FTP Motion plugin, but it is not yet working for me. I have a few questions regarding the settings which are not clear for me. Your help would be greatly appreciated.

1) I cannot use the default HTTP port because it is in use. I have set "override HTTP port" to 8085 in the ftp motion plugin. Does this HTTP port number have to be the same as in "Global Automation" in the Camera FFmpeg plugin?

2) For the "remote ftp server path" : When I use a ftp client such as FileZilla, the ftp server path is simply "/" since my user is automatically directed to the appropriate directory on the unraid server (using ProFTPd). Is this an appropriate path to use in the FTP Motion plugin? or is it necessary to give the full path explicitly?

3) It appears that the IP camera is successfully communicating with the ftp motion plugin, but communication to the ftp server fails?? I get the following error in the homebridge log. The "target" directory should be read/write!!

[9/26/2022, 3:53:40 PM] [FTP Motion] [FTP Server] [Bunyan] Satisfy Parameters Error { error: 'Socket not writable' } [9/26/2022, 3:53:41 PM] [FTP Motion] [FTP Server] [Bunyan] operation timed out

Any help you could provide would be greatly appreciated.

Thanks,

PM.