-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have the ability to use API/MQTT to change which waypoint to view #835
Comments
Does the Or would it be more like what |
Pan Cruise will switch waypoints automatically every 10 seconds. That K11012_setCruisePoints sounds more like what I'm looking for. |
This one is a little tricky because we need to send a list of positions, so it will probably need to be a json-based request. something like: [{"vertical":"20","horizontal":"40","time":"10"},{"vertical":"20","horizontal":"120","time":"15"},{"vertical":"20","horizontal":"300","time":"10"}] open to suggestions or ideas. |
I'm using something similar to move the cameras left/right in home assistant with MQTT. If there's an option to just send the waypoint that is configured in the Wyze app that would be ideal. I'm not sure how to see what gets passed to the camera's from the app, or I would see whats happening to hopefully share more details. |
hmm maybe GET @jhansche might have some suggestions? |
How do you find the commands that Wyze uses with the cameras? |
Yeah I'm pretty sure this is how the manual waypoint selection works. I don't think it's just a "set position to waypoint 1", etc. You have to get the waypoints and then set the position. At least that's my assumption. I didn't trace what it does when doing that, but I didn't see any command that selects the waypoint by index. |
Updated GET
most of the commands can be found by decompiling the wyze app and/or firmware. |
This should now be available in v2.3.0. Also updated the wiki with additional info. |
Just a suggestion/idea. It would be really beneficial if the bridge had the capability to act as a proxy for standard onvif ptz commands. That is to say, in people's software of choice, they could just select onvif and the generic PTZ commands could be sent to Wyze PAN cams, the bridge acting as the intermediary. I believe the generic onvif commands look something like this.
I just quickly copied this from marklagendijk/node-onvif-ptz-cli If it's possible to standardize them, so they could be used in other apps, that would go a long way. And I believe the Onvif protocols pretty much have standardized pretty much everything. The usefulness of this would be a big deal for many, I believe. Imagine being able to use any of the software that's out there and use some of the many functions within the bridge. |
I believe onvif uses SOAP, however, I don't think there are any python-based onvif or soap libraries that can act as a server. Open to suggestions or ideas! |
Finally getting around to testing this, and it looks useful @mrlt8. A couple notes, not sure if intentional?
Unfortunately the weirdly encoded response/value string makes it harder to work with something like the RESTful integration, or the MQTT integration where we're already getting the parsed JSON object and maybe don't have an easy way to re-parse the string after we extract it from e.g. Re (2) and (3), what I was expecting would be for at least one of those 2 response fields to be fully JSON-path addressable:
This way we can address those values using This would also make it more reliable if all we want to do is, say, adjust the horizontal value for one waypoint. We could easy do that if the value is already valid JSON:
Unrelated, but the response from my camera highlights: the wiki page says |
Will try to work on this.
|
Obviously if it's a lot of effort then maybe it's not worth it - we can still parse the value, splitting it by More than likely though, if it's not coming back as accessible JSON, then most people would probably just ignore this command entirely, and make their own script to just set Or if the goal is specifically to set the camera to a specific configured waypoint (which appears to be the original ask in this ticket), a much more approachable solution would be I guess it comes down to weighing the value added vs level of effort. I can see an argument for this being not worth the effort, and an easier proposal being to configure your own HA scripts to move to exact coordinates, and don't even worry about waypoints at all. |
@jhansche Could you try out the latest dev branch? I added a SET |
@mrlt8 It's a little slow to react (about 5.5 sec each time), but it works 👍 |
* cache build * Catch and disable MQTT on name resolution error * Doorbell quick response * Set camera time zone #916 * Set timezone on camera #916 * OSD toggle for logo/timestamp * Add K10006 auth #742 * Fix /time_zone/get and return offset #916 * convert TZ offset to hours #916 * custom video filter #919 * Resend discovery message on HA online #907 #920 * Revert K10006 for WYZEDB3 #742 * Add more MQTT entities #921 #922 * Return json response/value for commands #835 * Fix threading issue on restart #902 * Fix SET cruise_points over MQTT * SET cruise_point #835 * split into multiple jobs * changelog
* Start from index 1 for cruise_point/waypoint #835 * update_snapshot via MQTT * fix camera status always online #907 #920 * Additional MQTT entities #921 * QSV related changes * i965-va-drivers #736 * FIX power status #921 * Fix cruise_point type #921 Thanks @jhansche * return index from command payload #921 * Update docker-image.yml * Monitor and set preferred bitrate #929 * Default to `-` for cruise_point #921 * clear out stale entities #921 * changelog
I know this is piggy-backing on a different topic, but I too am interested in ONVIF server support. I found this recent Python Soap Server library that I thought I’d pass along in case it would help. It might be too simple or more of a POC; I’m not sure. https://github.com/esmaily/python-soap-server If it would be better for me to open a separate ticket for this enhancement request, I’m happy to do that. Thanks! |
With the wyze cam pan v3 you can create up to 4 waypoints to see different views. Looking to have the ability to use API and/or MQTT to change which waypoint to view on the pan cam.
The text was updated successfully, but these errors were encountered: