I am constantly getting this error when running the Bird Buddy Postcard Collection Blueprint. Any ideas as to how i can resolve getting this error? The integration seems to be working as it should.
Thank you for the help. I have installed the most current version and now I am waiting for the birds. Question: have you been able to access the live-stream with HA yet. I was just reading an AI response that says it is working in this HA integration.
No, there is no plan to access the live stream in HA - that was an AI hallucination.
The Bird Buddy is not designed for 24/7 live streaming. The ability to check the live camera from the BB app is only for troubleshooting purposes, so you can confirm connectivity and visual placement. While in this mode, the BB will not function as it usually does; and it will drain the battery if you try to leave it streaming.
Iâve never seen this, as I didnât edit the blueprint in VS Code since creating it.
If you look at the blueprint selectors documentation, it appears that, e.g. sort: false, IS valid. Though it also looks like sort=false is the default, so you could also just remove that.
To resolve the first error, it looks like it wants a list:
Generic Camera (especially with the UI config flow) does not work nicely with template URLs. And especially if the template does not currently resolve to a usable URL. Test your template in the developer tools screen, and check if it evaluates to a real URL and that you can view the image using that URL. If itâs reporting None or some other non-URL, then the generic camera config flow will NOT accept it. Thatâs because the config flow will show the image from that URL and requires that you confirm the image before you can finish setup.
Alternatively you could try to add it directly to configuration.yaml, which used to work, but not sure if it still does.
Finally, the image entity is still sitting in an open PR, because Iâm not entirely happy with it yet. When the recent visitor entity_picture is working, the image entity also appears to be working. Itâs just a little unpredictable, particularly when there hasnât been a visitor in several days. If youâre interesting in testing out the PR, you can run the action yaml mentioned here. That will install the PR version, and when you restart HA you should have a new image entity, and you wonât need the Generic Camera workaround anymore.
Generic Camera (especially with the UI config flow) does not work nicely with template URLs.
Do you have an example of a template URL that is not working correctly with generic camera? It is intended to handle these.
When you enter URLs during the config flow, the following checks happen:
Templates are rendered, and a check is done to make sure that there is a valid image or stream at the other end of the resulting URL.
The config flow attempts to load a preview of the image and/or stream. You can ignore these if you like by clicking âeverything looks goodâ, even if it doesnât. This will finish the config flow.
But you are correct that 1. will not succeed if the URLs are not valid. This logic is to catch problems caused by people entering the URL of an HTML page which embedded an image/stream rather than the actual raw image/stream URL. In a lot of cases users did not understand the difference.
configuration.yaml setup of cameras is not supported any more. I donât know what happens if you try it.
If you have a specific use-case that isnât working, please describe it or raise as a bug ticket and I will help where I can.
Nope, thatâs exactly what I was referring to. Since the template wonât evaluate to a valid URL unless there is an image to show, so if you try to enter the template while the attribute is not set or after the signed URL has expired, then it prevents you from setting it up. Once thereâs a valid image URL in the attribute then it will work and will remain valid from then on. Thatâs what I meant by that.
Would be nice if there were a âyes I know this isnât a valid URL, but save it anywayâ override.
Anyway, the right solution here is the image entity, which is whatâs in progress now and will be released eventually