Smb 1 ??? I think it’s time you update your storage :+)
6 Likes
GSzabados
(Gábor Szabados)
July 6, 2023, 8:25pm
113
How much time is it until it will be the latest/stable? As I see it is already released (about 2 hours ago), but the latest/stable still points to 7.0.
Flagun
(Marek)
July 6, 2023, 8:31pm
115
I have problems with Hyperion integration. I cant control my instances. The status in HA changes but not really.
nickrout
(Nick Rout)
July 6, 2023, 8:47pm
116
Yes it seems to be the case. Not sure whether it is a change in ha or esphome.
so other than creating that image in the /www folder, id love to be able to create the image template sensor in media, and not ip ban the instance when browsing locally.
can this really only be done using all kinds of reverse proxies etc to create a https connection when using the local ip address?
in which case writing that snapshot to the www folder might be the simple solution indeed…
although even that image does indeed not update upon rewrite of a new capture. The image file is overwritten to capture the latest shot, but the template image does Not update at all. As a matter of fact, I can only get it to update reloading the complete template config… not even a page reload/cache clear/refresh makes the last image appear
dinth
(Michal)
July 6, 2023, 9:34pm
120
Same problem here. Seems that the HA switch is switching on/off the effect not the light itself. Unfortunately i temporarily dont have access to my yubikeys and cannot login to GitHub to log an issue
This is weird as there’s no mention of any hyperion changes in the changelog, not to mention a breaking one.
Could you post the link to that issue? Would love to follow that
Updated to 2023.7 bumps resources usage:
Memory use (%)
Processor use (%)
updog
July 7, 2023, 2:54am
123
Where’s the changelog for 2023.7.1?
tom_l
July 7, 2023, 2:56am
124
Kertz1954
(Kertz1954)
July 7, 2023, 5:25am
125
Heads up for Dutch users who are using the buienradar integration.
If you are seeing “unknown ” in your weather related dashboards this morning, don’t worry, it’s not an HA problem. Since late yesterday evening, there has been no weather stations listed in the Buienradar JSON file. The 5 day forecast is still present and available.
You can follow this link to see the current JSON contents.
https://data.buienradar.nl/2.0/feed/json
2 Likes
After update to last version 2023.7.1, my recorder still freezing. System must be restarted, again, again.
Installed MariaDB
recorder:
purge_keep_days: 90
db_url: mysql://****:****@core-mariadb/homeassistant?charset=utf8mb4
Not acces to system page
Many thanks for the great work!
In the previous versions, the switch would control the “LED output” switch located in the hyperion interface under “remote control”.
Since the output to the LEDs is off also the light would turn off.
I can raise an issue on github…
so is it a bug, when using a unique_id:
, but not a name:
the new template image entity is NOT getting the object_id and name based on the unique_id
?
- image:
- unique_id: test_name_template_image
# name: Test name template image
url: 'http://<server>.local:<port>/local/images/bonen.jpg'
while ‘regular’ templates get it applied correctly, with the prefixed template_
:
- sensor:
- unique_id: test_name_template_sensor
state: >
{{states('input_boolean.test')}}
opened 07:29AM - 07 Jul 23 UTC
integration: template
### The problem
opposed to the other template platforms, the new image template… does Not use the unique_id for setting entity_id and name, but sets it to be `image.template_image`
<img width="420" alt="Schermafbeelding 2023-07-07 om 08 28 33" src="https://github.com/home-assistant/core/assets/33354141/f8225dd6-23ce-4dc8-a163-ecc888a83202">
other template platforms, like sensor in following example:
```
- sensor:
- unique_id: test_name_template_sensor
state: >
{{states('input_boolean.test')}}
```
correctly set it to be `sensor.template_test_name_template_sensor`:
<img width="580" alt="Schermafbeelding 2023-07-07 om 08 29 47" src="https://github.com/home-assistant/core/assets/33354141/92e9719d-5870-48b7-9803-3f6b7f5bbbd5">
### What version of Home Assistant Core has the issue?
2023.7
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
template image
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/template/#image
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
- image:
- unique_id: test_name_template_image
# name: Test name template image
url: 'http://<server>.local:<port>/local/images/bonen.jpg'
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
nickrout
(Nick Rout)
July 7, 2023, 6:39am
130
Are you guys perhaps running into this change?
home-assistant:dev
← Sab44:add-hyperion-entity-to-clear-source-when-off
opened 05:44PM - 17 Oct 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
The behavior of hyperion lights has changed:
Turning off the light entity will only clear the priority you have configured during integration setup. Other HA-independent light sources in Hyperion might still be active and cause light to be emitted. In order to turn the light output off entirely regardless of active light sources, you can enable the `switch.[instance]_led_device` entity that acts as a global switch. Subsequently, external effects that are unrelated to the Hyperion light source (such as USB capture) have been removed from the light entity. To control them, enable the respective disabled-by-default switch entity. See the updated [documentation](https://www.home-assistant.io/integrations/hyperion/) for more details.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
The current state of Hyperion light entities makes custom configurations very hard because there is inbuilt **strong coupling** between the different components:
- the default light entity will actually control 3 different things:
- when turning on:
- the overall Hyperion instance state (`switch.my_instance_all`)
- the LED device state (`switch.my_instance_led_device`)
- create a light source at the configured priority
- when turning off:
- it will only switch off the LED device state (`switch.my_instance_led_device`)
- **it will not clear** the opened light source at the configured priority - it will stay active and there is **absolutely no way** of clearing it from HA. I consider this a bug.
- this behaviour has multiple disadvantages:
- other light sources, e.g. a constant background "ambient" light will not be shown anymore. Another example is you want to watch a movie on your HTPC but the light from the HTPC screen grabber's configured priority will not be shown as your LED device has been turned off.
- if you turn the LED device back on because you want other light sources being able to connect and light up, the previous HA priority will still be there and can take priority over other sources.
![Screenshot 2022-10-17 at 19 23 28](https://user-images.githubusercontent.com/64696149/196242923-59b545ae-f597-4647-8027-0cf0f6f5c035.png)
![Screenshot 2022-10-17 at 17 18 57](https://user-images.githubusercontent.com/64696149/196242405-74e1aca6-ea3e-4d89-8ab5-47a5aae9d494.png)
Proposed Change ✅:
- remove strong coupling between light entity, LED device and overall Hyperion state
- light entity will create a priority channel light source in Hyperion when turned on and will clear that channel when turned off - nothing else
- full customization: the previous behaviour can now be partially or entirely reconstructed by using automations or a template light (if you want even the state of the entity to represent multiple entities' states)
- **all the entities are decoupled and can be individually controlled**
Note: during https://github.com/home-assistant/core/pull/45410 an additional "Priority Light" was introduced that would send a black color when being turned off. As this results in the priority being ignored by Hyperion it had the same effect as clearing the priority but would maintain an active connection on that priority channel. Clearing the priority is the proper thing to do, therefore this light is not required any longer. The priority light entity has therefore be unified with the main entity.
As a positive side effect, the code of this integration is simplified significantly.
@dermotduffy your feedback is welcome and highly appreciated!
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [x] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes https://github.com/home-assistant/core/issues/77020
- This PR is related to issue: https://github.com/home-assistant/core/issues/41892
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/24604
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
this seems to work alright:
template:
- trigger:
- platform: state
entity_id:
- binary_sensor.oprit_vehicle_detected
- binary_sensor.oprit_person_detected
to: 'on'
# below triggers are required to prevent broken image placeholders
# do cause the state to show the last triggered time, end not perse the time the image was shot
- platform: event
event_type: delayed_homeassistant_start
- platform: event
event_type: event_template_reloaded
image:
- unique_id: last_snapshot_oprit_camera
name: Last snapshot oprit camera
url:
though one has got to bear in mind the date in the picture-entity shows the dat of the last triggered, and not necessarily the date of the moment the image was taken.
taking the trigger on the template reload and homeassistant start events out of the trigger template would solve that, but then would result in a broken image placeholder upon restart, or template reload…
trigger template image does not restore state ?
opened 07:21AM - 07 Jul 23 UTC
integration: template
### The problem
as title (and opposed to the other trigger template platforms… )
when using below trigger to create the template image, the dashboard shows a broken placeholder when HA starts, or template integration is reloaded
(we can add some extra triggers for those events, but that updates the template entity, and makes the picture-entity card show a dat of the last trigger, and not the date/time of the last snapshot creation)
### What version of Home Assistant Core has the issue?
2023.7.1
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
template image
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/template/#image
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
template:
- trigger:
- platform: state
entity_id:
- binary_sensor.oprit_vehicle_detected
- binary_sensor.oprit_person_detected
to: 'on'
image:
- unique_id: last_snapshot_oprit_camera
name: Last snapshot oprit camera
url:
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
<img width="540" alt="Schermafbeelding 2023-07-07 om 08 56 32" src="https://github.com/home-assistant/core/assets/33354141/82db58a7-063d-4ca0-9920-a4b7b0874e34">
I follow a morning routine where, after my alarm goes off and I am detected by a specific motion sensor, I want my calendar to be read out to me. The blueprint created by @allenporter works as a notification on my smartphone, but it doesn’t function as a voice output. How can I resolve this issue?
2 Likes
will report in the Plugwise topic too, but since this is a first discovery in 2023.7.1, I figured maybe other people experienced it too:
No idea what vn/a might be, and my Plugwise integration is working fine. tbh, I am a bit wary clicking Configureer there, as I dont want to mess up the other integration sections…