I have setup 1 wire on an R-PI before, and when I upgraded to HA 17.1, all keeps working. Now i’m setting up another R-Pi running HA OS with the “Raspberry Pi 1-wire via sysbus” integration from HACS and I am tearing my hair out getting the 1 wire bus overlay on the Pi to work. The method described in the integration (move SD to laptop, edit the config file with overlay there and reinsert into the Pi) won’t work, it seems that HA OS 17 doesn’t create the overlay when starting, I tried putting the file on a USB stick and ha os import from there, no go. Any way to activate 1 wire through an overlay or do I have to go to a DS2482 adapter? Thx
I would ask there.
The custom integrations need to chase HA, not the other way around.
My suggestion is get an esp32c3 and use that in ESPHome…
substitutions:
name: "furnace"
friendly_name: Furnace Room
frame_type: esp-idf
board: esp32-c3-devkitm-1
packages:
device_base: !include /config/esphome/packages/cottage_base.yaml
esp32:
variant: ESP32C3
wifi:
manual_ip:
gateway: !secret cottage_gateway
subnet: !secret cottage_subnet
static_ip: !secret firebox
esphome:
name_add_mac_suffix: false
bluetooth_proxy:
active: true
spi:
miso_pin: GPIO5
clk_pin: GPIO4
sensor:
- platform: max6675
name: "Cottage Gas Furnace"
cs_pin: GPIO7
update_interval: 64s
- platform: dht
pin:
number: GPIO3
mode:
input: true
pullup: true
model: AM2302
temperature:
name: "${friendly_name} Temperature"
accuracy_decimals: 1
humidity:
name: "${friendly_name} Humidity"
accuracy_decimals: 1
update_interval: 75s
Thank you. Well, yes and no, I understand the point. But it’s not the integrations fault as HA doesn’t allow to expose the 1 wire interface to the integration, HA has locked down the access by the look of it.
Well, yes it is. The purpose of the custom integration is to make that work, would be my assumption.
You state it is no longer doing that.
The CI found a likely undocumented (from HA’s standpoint) way of making something work, which is fine, but it is not HA’s responsibility to make sure that keeps working. The CI has to chase and adapt.
is clearly not a supported HA method and was always subject to failing at some point.
(Actually sounds like a possible security problem to me…)