couriersud

Would love to help you ... but this seems to be WSL limitation: https://github.com/microsoft/WSL/issues/5158 USB devices don't work in WSL - at least that is what I read.

Can you please run `./msigd --debug --info --query > out.txt` and upload `out.txt` here? I need the file to get the exact character code for `s140`. Thanks a lot!

Ok, great, the string representation is `"\x30\x30\x85"`. Hex `85` is not a valid UTF8 character :-( Need to change the code to use a hex dump.

I added support for the monitor in this branch: https://github.com/couriersud/msigd/tree/43-mag274qrx-support You will not be able to modify monitor settings. We first need to ensure that `./msigd --debug --info --query` works.

Thanks a lot! on stderr I am missing a line like `msigd: Error querying device on `**`navi_up`**` ...` Can you please confirm you get this line?

I finally managed to get a WIN10 VM up and running. That caused the delay coming back to this issue. Are you able to control your monitor settings with one...

i have submitted a proposal for this issue in PR #141

> One thing I possibly didnt check was if the recording creates a temporary file that we could pick up, prior to details being written into the db on completion....

> Is this file created in real-time as the motion event is detected? or does it have the same 30-40sec lag as the current database trigger has? As soon as...

I have added inotifyd to busybox. The directory structure of alarm_record is a challenge, since sub folders are created. However, I made some observations in `/tmp`: ``` [root@ipcam_dgf]# inotifyd ./test.sh...