Replies: 7 comments 1 reply
-
|
Sure/happy to support, just make sure it is optional, support config flow (configuration.yaml not a must), defaults to current bus and doesn't break existing configflow/configuration.yaml configurations. There are two options wrt bus number configuration:
|
Beta Was this translation helpful? Give feedback.
-
|
Please take a look at PR: #35 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your PR, it looks good/started review |
Beta Was this translation helpful? Give feedback.
-
|
Once f7971e1 tested OK from you side, I'll publish a new 1.3.0 release to make it available to everyone (HACS will pick it up as well) |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks so much for tackling this issue. I just deployed this version on my home assistant running on a RPi 4 and it works great. Means I can now remove my patch 🌈 . Note: I did not run the migration, since I configure through .yaml. |
Beta Was this translation helpful? Give feedback.
-
|
Even with .yaml should go thru the migration code, i.e. if you look at files below, you should see for mcp23017 instances IDs with bus information prefix:
Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
I just released v1.3.0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, thanks a lot for this custom component. I realized that
custom_components/mcp23017/const.pydefines a constant number for the bus being used/dev/i2c-#. In my case this is not sufficient and I would think it would be best to let this be configured.Would you accept a PR that makes this a config?
Beta Was this translation helpful? Give feedback.
All reactions