Update onewire integration docs

[MrDadoo]

Changes to go along with pull request #31419 for the onewire component.

Proposed change

Changes made to describe platform better, how to use it, what it provides and what kind of devices it supports.

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase:
  Update onewire component core#31419

• This PR fixes or closes issue:

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[MrDadoo]

Am I supposed to do something else with these pull requests?
One of the tests seems not willing to complete.

[klaasnicolaas]

You must first resolve the merge conflict 😉

[MrDadoo]

Actually I don't understand why there was a conflict, but its resolved anyhow.

Can I in some way see who wrote the original docs... There are some things I dont really understand and would like to ask.

[klaasnicolaas]

I see that @fabaff originally made the documentation of this integration, but you can just ask your questions here. Maybe I can help you?

[MrDadoo]

There is a section about "multiple sensors" and "updating database using SQL" and "discontinuity in measurements".
I don't understand why this happens. Is it something related to the TAI-8570 device.

[MrDadoo]

One other question @klaasnicolaas. I am not up to date with new naming of home assistant.
I tried in the doc to discuss hass.io and Docker, but the linter didn't like that.
What is the correct terminology for the softwar package containing docker, supervisor, and homeassistnat that previously was called hass.io.
And the home assistant software that nowadays run within the docker container, what is that called?

[frenck]

Wat previously was called "Hass.io" is now called "Home Assistant".
"Home Assistant" is the full suite of projects we run.

Wat previously was called "Home Assistant" is now called "Home Assistant Core".
You can run Home Assistant Core in a Python virtual environment, or, using Docker.

There is also a variant "Hass.io on a generic
Linux installation", in which people run the Supervisor on e.g., Ubuntu or Debian. This is now called "Home Assistant Supervised".

[MrDadoo]

Thanks allot for the clarification @frenck. I'll keep that in mind. I'll use that when updating the docs

[MrDadoo]

On the 1-wire bus, sensors might come and go.
A sensor that has been available might disappear for a while, especially on unstable networks.
I've found last_changed and last_updated attributes (sounds quite similar to me).
But what is best practice to note if a sensor is present or not. On 433 sensors, battery might go low or obstacles may appear in radio transmission and sensors might be away for a while.
In other systems, this can be shown by the sensor being dimmed or having a ! mark.
What is the preferred way of implementation in HA?
Also, if new 1-wire devices appear on the network. Is it then good practice to dynamically add them?
For disappeared sensors, removing them is not a good solution in my opinion, but marking them as not available.
I miss a "last_seen" property handled by ha inherently.

[MrDadoo]

@frenck and @klaasnicolaas ,in Home Assistant (and … Core and ...Supervised), is it really possible to access the GPIO pins on the Raspberry Pi for example. The doc has descriptions on how to use w1-gpio kernel module. Is that module available on HassOS? (I myself run Home Assistant Supervised on a Linux OS so I cannot check) As HA nowadays run in virtualized python or docker or on HassOS, shouldn't that part be removed from this document?
We can run the onewire platform using owserver over network or install an add-on that runs some os that can read the I2C or USB busses and expose owfs over network. Even if we in an add-on can run owfs and populate an /mnt/1-wire folder, this onewire integration cannot read that containers file system.
Am I completely off track here, or does the document need a bigger revision?