Where “some_hook_id” can be anything but in this case is the id generated automatically by the motionEye integration when configuring a camera.
When running this command with “some_hook_id” the curl command returns a response of
Missing webhook parameter: device_id
and an Automation trigger with “some_hook_id” as the Webhook ID is never triggered. The implication is that the Webhook Post failed based on the curl response received and that the failure is due to a missing “device_id” parameter of which the Webhook documentation makes no mention.
To be clear, motionEye plays no part in this issue as the curl command is being run from the command line according to the Webhook documentation which has nothing to do with motionEye. It is just implementing motionEye that has brought light to this apparently glaring bug in Webhook. According to the documentation one can use any arbitrary “web_hook_id.”
Btw, I have tried appending "?device-id= and the same message occurred. I haven’t yet tried to figure out a valid device id in the system to try to use just as a test. According to the doc, device IDs play no part so I shouldn’t have to go down this rabbit hole.
Before this is turned in as a bug does anyone have any idea why this is failing in this manner?