esphome / esphome/feature-requests
Support for MCP 23018 (similar to MCP 23017)
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
`MCP23107` is a very popular IO port expander, but recently it has been discovered a bug that reduce the ports to 14 (for input)
There is a very similar working alternative: `MCP23018`
MCP23018 Datasheet: [link](https://ww1.microchip.com/downloads/aemDocuments/documents/APID/ProductDocuments/DataSheets/MCP23018-Data-Sheet-DS20002103.pdf)
MCP23017 Datasheet: [link](https://ww1.microchip.com/downloads/aemDocuments/documents/APID/ProductDocuments/DataSheets/MCP23017-Data-Sheet-DS20001952.pdf)
**Please describe your use case for this integration and alternatives you've tried:**
I am working on two projects where I need 16 IOs:
A centralized light (and others) control system: [link](https://github.com/crgarcia12/electronics-homeassistant-lightscontroll)
A workbench controller: [link](https://github.com/crgarcia12/electronics-workbench-controller)
**Additional context**
Currently, ESPHome supports MCP23008, MCP23016 and MCP23017: [link](https://esphome.io/components/mcp230xx.html)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing ESPHome's existing MCP23017 support and the mcp230xx component documentation, then compare the MCP23018 and MCP23017 datasheets linked in the issue. Done means ESPHome supports the MCP23018 with its 16 I/O ports and the existing MCP230xx behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100