This repository was archived by the owner on Jul 1, 2025. It is now read-only.
add mqtt triggering and reporting - #19
Open
frankenbubble wants to merge 1 commit into
Open
Conversation
you can publish as message to trigger and update of an image, publish the image number to homeassistant/screenshot/update , send a screen number of 0 (zero) to trigger all when it's completed writing the image it will respond on homeassistant/screenshot/updated with the image number and timestamp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This update adds support to triggering updates via mqtt and receiving messages when complete.
you can publish a message to trigger an update of a single image, just publish the image number to homeassistant/screenshot/update. Send a screen number of 0 (zero) to trigger all images to be updated
when an image is completed being written, a message will be published on homeassistant/screenshot/updated with the image number and timestamp
This means you can use events to update images, instead of (or with) cron. My use case is openHASP and it will time out receiving and image before it's created, so I was using cron. This way when I need to update an image on openHASP I trigger the update in hass-screenshot, and when the message is received it's complete, then trigger openHASP to update the image.