DjJoakim
(Joakim)
February 11, 2024, 9:58pm
1
Hey!
I am using a pyscript that gets the CPU temperature from my Raspeberry PI 4.
After 2023.6 update, the vcgencmd changed place from /opt/vc/bin/vcgencmd to /usr/bin/vcgencmd, so the last time this broke - i just replaced this path and it started working again.
But since 2024.2 update it seems to be moved/replaced again, and i can’t find the path for it.
I have tried which, locate, find etc in the terminal but with no luck.
Does anyone have some suggestion to where it may have been moved?
Or, if it’s possible to use another way to read the CPU temperature.
Here is the pyscript i am using - https://pastebin.com/raw/TM3vLrS0
Thanks!
cmartens
(Corne Martens)
February 12, 2024, 9:49pm
2
DjJoakim
(Joakim)
February 12, 2024, 10:21pm
3
Oh! Thank you for the information, I will follow the issue there.
DjJoakim
(Joakim)
February 13, 2024, 11:03am
4
Thanks to @agners on GitHub for finding the issue and making a request.
This issue will be fixed in 2024.2.2 as frenck just approved.
More info can be found here
home-assistant:dev
← agners:install-raspberrypi-utils
opened 10:03AM - 13 Feb 24 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.
-->
## 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.
-->
In Alpine 3.19 most Raspberry Pi utilities got removed from the raspberrypi-userland package. This package was based on the deprecated Raspberry Pi userland repository.
The replacement package is raspberrypi-utils, which contains the newer version of the same utilities. More specifically, it depends on packages which contains those utilities.
## 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)
- [ ] 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 #109913
- This PR is related to issue:
- Link to documentation pull request:
## 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.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] 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/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
@DjJoakim how did your script look like?
Until 2023.5 I used this:
- platform: command_line
name: CPU Clock
unique_id: 0ac68efe-6a23-4622-acc1-1085002168a5
command: "/opt/vc/bin/vcgencmd measure_clock arm | cut -c15-24 | rev | cut -c 7- | rev"
unit_of_measurement: "MHz"
scan_interval: 30
command_timeout: 15
value_template: "{{ value }}"
which is now not working anymore for command line sensors. I noticed the move from /opt/vc/bin/vcgencmd
to /usr/bin/vcgencmd
as well, but this now seems to be only available from inside the HA container (I’m running HA OS) while the former /opt/vc/bin/vcgencmd
was available to the CL sensor without any issues.
For sure some new restrictions kicked in with 2023.6, I could neither find which nor a solution to this.
Edit: nevermind, seems I found the solution (I use similar ones for other parts). I transfered the command_line sensor to a MQTT sensor. I use the advanced SSH addon’s init_commands
like this:
- >-
while [ 1 = 1 ]; do docker exec homeassistant /usr/bin/vcgencmd
measure_clock arm | cut -c15-24 | rev | cut -c 7- | rev | mosquitto_pub -t
homeassistant/sensor/system/cpu_clock -r -u 'mqtt_username' -P 'mqtt_password'
-l -i 'SSH-addon_init-command_7' && sleep 60; done &
and continue to use the sensor this way:
- name: CPU Clock
unique_id: 0ac68efe-6a23-4622-acc1-1085002168a5
#entity_id: sensor.cpu_clock
unit_of_measurement: MHz
icon: mdi:cpu-64-bit
state_topic: "homeassistant/sensor/system/cpu_clock"
state_class: measurement
entity_category: diagnostic
value_template: "{{ value }}"
This is a working solution for all HA OS users.
Unfortunately this undocumented 2023.6 change/restriction costs me more than 1 hour to only fix this single sensor.
DjJoakim
(Joakim)
July 20, 2024, 9:50am
6
Glad you sorted it out.
You can see the script I am running in my main post.
I saw it, but running HA OS it has no benefit unfortunately. I guess you run supervised or even Core only.