Or maybe indeed the raspian release also? Where did you download that 07-10 release? On this site 09-26 is latest one?
So maybe the solution is HassOs or raspian release…
Or maybe indeed the raspian release also? Where did you download that 07-10 release? On this site 09-26 is latest one?
So maybe the solution is HassOs or raspian release…
With remote GPIO activated, I previously had HassOS 2.12, and now am running 3.5RC. As for the Raspbian release, I downloaded it from the same site. They must have just released a new version several days ago.
No idea then why it works for you, should be pretty straight forward to configure …
An it’s already reported as a bug in gpiozero, seems workaround is to set environment to mock…
issue : gpiozero.exc.BadPinFactory: Unable to load any default pin factory!
WORKING, i think i created a good workaround now , just loaded this component as a custom component, downloaded from here:
then i changed in the manifest.json the requirements, from 1.4.1 to 1.5.1 , like code below
so it downloads a new version for gpiozero
according to this fix; if no pin_factory is defined , it will fallback to mock…
so it should be an easy fix/workaround for now, untill a developer changes the requirements for this component
{
"domain": "remote_rpi_gpio",
"name": "remote_rpi_gpio",
"documentation": "https://www.home-assistant.io/components/remote_rpi_gpio",
"requirements": [
"gpiozero==1.5.1"
],
"dependencies": [],
"codeowners": []
}
more info:
And already a PR :