-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Update onewire component #31419
Update onewire component #31419
Conversation
Added three attriubtes for each sensor, DEVICE_FILE, RAW_VALUE and SENSOR_TYPE Added some comments. Updated to get config values for owserver to get owport and owhost.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest reverting all changes except the device sensor and sensor type constant additions.
I now think I have resolve all comments. |
There's still one commit with the unlinked email. See the bot message above. |
Now I've managed to get rid of the faulty mail. |
…file as attribute that takes its data from Entities unique_id-.
…rom the self._device_file member variable of the entity.
This time tests failed without any significant changes have been made. |
The test failure is unrelated to the changes here. Don't worry about it. Please change to debug logging per above, then we can merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good!
@MrDadoo please update the documentation for this integration accordingly by opening a PR in home-assistant/home-assistant.io :) |
Please advise me where to start/find/continue documentation. |
Here is a guide on how to contribute to the home-assistant.io documentation. |
I've found documents here I can add some lines to describe my update. But do you want me to update in directly in git, in current or next branch, or create a pull request from a clone? I also see that the document searching on the home-assistant page finds the term "1-wire", not "onewire". Is there a way to add some kind of search tags so that integration documents can be found for both terms ? Even "ofws" would be a decent search term. |
That is the right one! You can edit this page by clicking on
Yes, please add some lines describing your update. It is up to you whether or not you want do it on Github directly or via git. You will need to create a PR nevertheless. Please use the next branch since you are adding a feature to HA, see the developer documentation for reference:
To answer your last question:
Please take a look at this issue home-assistant/home-assistant.io#11682 |
Am I supposed to do something else with these pull requests? |
I think we're good. |
Proposed change
For family 26, there are a couple of other measurable values that wherer not previously retreived. This PR includes grabbing the voltages VDD, VAD and the current IAD from the device.
I also added two attributes for each sensor that might be of interest for the user.
Device file name (part of owfs path) and the raw_value that is not rounded or truncated. Example.
device_file: /28.FF5C68521604/temperature
raw_value: 28.3125
Some debug outputs were added to simplify development and fault finding.
Type of change
Checklist
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
The code has been formatted using Black (
black --fast homeassistant tests
)Tests have been added to verify that the new code works.
Added documentation Update onewire integration docs home-assistant.io#12071
The integration reached or maintains the following Integration Quality Scale: