Yes I do have a lot to say, and the difference between what I say and you GPIO people is that what I say makes sense and is not the same thing over and over and over again.
None of you have made any progress what so ever in over a month, it’s still in the whining and crying state.
My kids are more reasonable!
Even when the custom component is here there is still the same crying.
You have the exact same thing, you have got the three step guide to install it, but still there is the same crying.
I don’t get it. Are you people not ever going to move on?
I was caring a few weeks ago. I felt felt sorry for you all, and wanted to help find a alternative route.
Now after all this whining and some people’s hostile comments asking for picture and name I don’t feel anything about this topic anymore.
No I will not step up and help you.
It’s clearly not possible to help a group of people that is reluctant to all changes.
Even when the change is nothing, not sure if that counts as a change then.
In the day and age of excessive power costs in £ & $ it seems strange to be suggesting adding more power draw (no matter how small) for no gain. I already use ESPHOME and yes I could add an ESP to operate the fan for my Pi rack. Seems overly complex and a waste of power.
Can someone tell me if any of the viable GPIO replacement options (HACS and mqtt-io) support input on the Raspberry Pi 4b with a 64-bit kernel? The inputs have never worked for me with 64-bit kernels, which as forced me to use a 32-bit kernel even on my 8GB RPi 4b (which is a waste). Are there other options I should be considering?
ESP isn’t an option for me, unfortunately, as I have a custom board built around the RPi connector and I need a UPS to guarantee that the GPIO works so don’t want to put any more load on the UPS.
My configuration:
Operation system: Home Assistant OS 7.6
stable
supervisor: 2022.04.0
core: 2022.4.6
Python: 3.9.9
Raspberry Pi4
I coppyed whol directories “mcp23017”, “bme280” and “dht”, from relese 2022.3.8, and put to \config\custom_components, with that result:
-Platform error switch.mcp23017 - Integration ‘mcp23017’ not found.
-Platform error sensor.dht - Integration ‘dht’ not found.
-Integration error: bme280 - Integration ‘bme280’ not found.
What I did wrong? please help, at the moment I have to switch back to march version of the core …
You have to restart Home Assistant after you add a custom integration before you can use it in your config.
You’ll also need to add a version to the integration’s manifest.json if you have just copied it from the core.
Yes, I think that should work.
Please use the proper formatting the next time you post json, yaml or code in general.
Among other things, it should prevent accidentally tagging people like you just did in your previous post.
I made a custom integration based on the latest core code for Raspberry Pi GPIO component. It is still very raw, so there is really no documentation yet - it will be a little later. Installation is currently only available manually. You can test…
What exactly is the advantage of your fork over to the first fork from thecode that is available on default HACS ?
Unless they add something substancially new, everybody starting their own little GPIO integration forks is going to be counterproductive, because it’s really confusing for everybody.
- thank you very very much