I'm unhappy with the removal of GPIO

Social
593

Hacs is certainly not being removed.

The gpio support is being removed from ha core. It can be installed as a custom component. Via hacs is easiest.

594

Is there any chance of someone picking up Raspihats and moving it to HACS similar to rpi_gpio? It’s slated to disappear in the April release…

595

Are they even still alive?

Our new site will be online on 01.07.2019

596

I have no idea, but mine certainly is :wink:

1 Like
597

I suggest you copy the code over to your custom_components directory and add a version key to manifest.json. At least it will survive 2022.4.

As for ongoing maintenance, you’ll have to do it yourself or hope someone picks it up.

598

Thanks for the tip.
Had to perform the following operations:

  1. Comment out the raspihats config lines in config.yaml
  2. Upgrade HA Core
  3. Download the raspihats component files from HA Core github (link below)
  4. Move the component files to custom_components/raspihats directory
  5. Add a version number to the manifest.json
  6. Reboot
  7. Uncomment the raspihats config lines
  8. Reboot

Now it works again :tada:

Location for files to copy:

Home Assistant Core v2022.3.8 Raspihats

Move files into:

<config_dir>/custom_components/raspihats

Edit manifest.json and add "version": "1.0" (version number not important).

Example manifest.json:

{
  "domain": "raspihats",
  "name": "Raspihats",
  "documentation": "https://www.home-assistant.io/integrations/raspihats",
  "requirements": ["raspihats==2.2.3", "smbus-cffi==0.5.1"],
  "codeowners": [],
  "version": "1.0",
  "iot_class": "local_push"
}

Hope this helps someone.

2 Likes
599

Bollox

Moved over to Home Assistant so all my smart meters were working in one location

to find out your pulling support for commonly used thermal probes …
I have hundreds of fish tanks I monitor with 1 - wire sensors like the ds18b20

why the heck would I want to use ESPHome wifi is flaky

600

Don’t use wifi then. ESPhome supports wired ethernet.

Besides 1 wire isn’t being removed, it is still accessible via owserver.

601

I have owserver installed using

but I can not get it to find any devices because I have no way to enable 1wire ?

 OS Version:               Home Assistant OS 7.6
  Home Assistant Core:      2022.4.6

How do I get devices to show up with that OS ?

I have wasted a week now trying to get what should be a simple device working
but as Home assistant supports my meross + sonoff switches I am moving from domoticz

this file no longer exists /boot/config.txt

for adding dtoverlay=w1-gpio

and adding this did nothing

/config/configuration.yaml

sensor:
  - platform: onewire
    mount_dir: /sys/bus/w1/devices/
602

Thanks @tom_l. Have you made the move to the ESP route for your setup yet? I am a a bit of an ESP newb, any chance you can point me to exactly what I would need or a guide that details this out?

603

My initial experiments with Pi GPOI on Home Assistant (four years ago) put me right off using it. I used a separate Pi running Flyte’s MQTT-GPIO software for a while but recently changed that to an Ethernet connected ESP with port expanders running ESPHome. You can find out about ESPHome here: https://esphome.io/index.html There are many excellent tutorials online for example https://frenck.dev/diy-smart-doorbell-for-just-2-dollar/

1 Like
604

Thanks, which ESP board did you go with and which port expanders?

605

https://shop.allnetchina.cn/collections/quinled/products/quinled-esp32?variant=39253005828198

https://www.adafruit.com/product/5346

1 Like
606

Would some kind soul provide me a link to the appropriate Community Forum to enquire how I can get my previously working BH1750 light-sensor using Raspberry Pi GPIO to work using either the community rpi_gpio integration or ESPHome, now that inbuilt GPIO has been deprecated from HomeAssistant? (I just dont know where the right place is to get help on this)

607
608

Hi - thanks for the link, although I rather thought the GitHub page was more for reporting issues rather than general ‘how do I get this working’ requests for support?

However, I think I have since realised that rpi_gpio integration is not what I need - it seems to support only binary sensors, whereas my BH1750 light sensor is an analogue device. That being the case, I think I can add myself to the group of HomeAssistant users, angry at the deprecation of GPIO without an adequate alternative (it’s a bit like Ford Motor Co. suddenly deciding all their new models will ship without engines installed!)

609

How could it have worked before then?

Anyways… using ESP-Home you can use this:
BH1750 Ambient Light Sensor — ESPHome

610

The custom integration that is linked there is the one that home assistant is deprecating. It’s the exact same code. If the custom integration doesn’t work for you, then the build-in deprecated integration wouldn’t have worked either. I.e. There’s no reason to be upset as it wouldn’t have worked for you anyways.

611

Well, it definitely worked in HomeAssistant before. This is the details I had in my configuration.yaml:

sensor:
  - platform: bh1750
    name: boiler
    i2c_address: 0x23
    operation_mode: continuous_low_res_mode
    sensitivity: 254
    measurement_delay_ms: 400
    scan_interval: 30

I was under the impression that the new rpi_gpio integration only provided for binary_sensor, whereas my BH1750 is a ‘sensor’?

I tried ESPHome but started to realise that you need the BH1750 connect to some kind of ESP32 board (not sure if I’ve understood correctly) whereas my BH1750 is wired directly to the GPIO pins on my rpi2b as shown here:

https://www.raspberrypi-spy.co.uk/2015/03/bh1750fvi-i2c-digital-light-intensity-sensor/

612

There’s obviously something I’m missing. The code added to my configuration.yaml used to work:

sensor:
  - platform: bh1750
    name: boiler
    i2c_address: 0x23
    operation_mode: continuous_low_res_mode
    sensitivity: 254
    measurement_delay_ms: 400
    scan_interval: 30

Now I’ve upgraded HomeAssistant to the latest version (with the deprecated GPIO functionality), I’ve installed the rpi_gpio custom integration, and “platform: bh1750” now results in a failed configuration.yaml check.

So how do I get HomeAssistant to recognise “platform: bh1750” using the new rpi_gpio integration? What am I not understanding?