Closed fmarzocca closed 1 year ago
Maybe this has something to do with the battery camera waking up? The camera usually sends a bunch of messages such as the capabilities after login so maybe I should wait for some of those
I notice that 212 fails if it sends before these capability messages
I think you are right
Maybe you should wait for the capability messages before sending the command.
I'm working on creating something to properly parse tha capability. Since we can use it to give useful error messages such as this camera dosent support pir
Ok. Thank you. Just let me know if you need more tests.
After many tests, I can confirm this: your neolink is correctly working only if I keep the connection alive (either through Client on computer or App on smartphone).
Ok next test build will be here: https://github.com/QuantumEntangledAndy/neolink/actions/runs/4606409632
It waits for ability information and checks that we have rfAlarm_rw
premissions.
the build failed
Ah sorry forgot to commit the new file and not just the modified ones.
It works! Great job!
Are we all good? If so I'll close this and merge
Randomly, it happens that upon a request the connections fails and it responds with:
Error: Unable to get camera PIR state
Caused by:
Camera responded with Service Unavaliable
I need to send the command twice in order to get it working everytime. It seems that first command needs to set the camera alive (failing) and the second goes through. Sometime one command is enough, but mostly not.
Ok then, since the error code is always 400. I will see about retrying the messages if we get that error code.
Ok retry build is here https://github.com/QuantumEntangledAndy/neolink/actions/runs/4615033288
Reties every 0.5s for 2.5s
Perfect! This is very good, no failures. Yes, you can merge this. I will keep using this build.
Merged in #53
My camera is an Argus Eco. I am trying to switch OFF the PIR: