-
|
Dear all, I do have an ESP32 with Tasmota flashed (with MCP23017 support for Mode 1 and 2) and three connected MCP23017 in a chain which are fine from HW perspective and addresses (0x21; 22; and 23) are also recognized by Tasmota No more I2C devices are used (just the three MCP ones), with an Atmel uC I could access them with same physical setup. and stored in on the file system. It seems to detect the mcp23x.dat file, but switching to Mode 1 anyways. And the MCP on 0x22 and 0x23 are ignored, instead 0x23 is detected as an BH1750 sensor. What am I doing wrong? How could I get the two other MCP working? |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 12 replies
-
|
maybe just a part of the interessting solution: what´s about command "I2Cdriver" to find aditional blocking I2C-Driver for I²C Adresses 0x21,0x22,0x23 in file "my_user_config.h" One the BH1750 is found as driver Nr.11 registrated and use I²C Adress 0x23 and 0x5C and can be deactivated by command "I2Cdriver11 0" An additional way is not to allow unwanted drivers in your build. and now one more compile and install. Oberfränkische Grüße |
Beta Was this translation helpful? Give feedback.
-
|
While I've not used those chips, to me it looks like your config file is broken, not being valid JSON - looks more like you expected the JSONL format with multiple lines. AFAIK, a single template can cross multiple chips. For readability do wrap text blocks in triple backtick, instead of single backtick. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I did too much and disabled all, now the I2C seems to be broken... Went back to just eliminating only the 11, but still the same. Could neither scan the bus, nor get any I2C communication (and no, no HW was changed in the meantime). Need to cehck it tomorrow more deeply. I took the examples from here https://tasmota.github.io/docs/MCP230xx/#mode-2 therefore I just for every MCP one line. And I used the code tag the HMI here is offereing, now changing manually to three and looking much better. Thanks (even if it's now completely broken...) |
Beta Was this translation helpful? Give feedback.
-
|
OK, I2C is up an running again. After disabeling modules via I2CDriver, the device config is changed: Tasmota has re-assigned GPIO21 and 22 to none, hence SCL and SDA were not assigned any longer. Assigned them back and I2C is working again: However: still no MCP is recognized, nothing is working on I2C (beside address scanning) If I re-enable the 11, I do get again back the BH1750. But still no MCP |
Beta Was this translation helpful? Give feedback.
-
|
Maybe disable I2CDriver 22, as mode 2 is I2CDriver 77 instead. When that driver initializes, you should see a MCP: message if you have log level enabled for debug. |
Beta Was this translation helpful? Give feedback.
-
|
You made it: yes, its the module 77 for Mode 2 and hence needs to be activated. Great one, wasn't checking that. Thanks a lot for the quick help!!! |
Beta Was this translation helpful? Give feedback.
-
|
Why disabling all I2Cdrivers ? take a look to file "my_user_config.h" to find blocking I²C drivers with I²C Adress 0x21,0x22,0x23 This is the Driverlist I allow. Oberfränkische Grüße |
Beta Was this translation helpful? Give feedback.
-
|
It is no problem disabling all I2CDriver except the specific one(s) you want to use. Most of the time it makes no difference, except with certain drivers not able to reliably detect if "their" address is taken up by another chip type. When I do a build, I use build time settings to explicitly have all I2CDriver disabled, where I than can enable the one(s) I want. |
Beta Was this translation helpful? Give feedback.
-
|
As I need to make custom build anyways for having the MCP inside, for me it's good to not have dead code inside. It's just never used and could cause only trouble. And no, on this device no other sensors or actors will be used, in fact I only need a I2C MQTT bridge. Even the ESP32 IOs are not needed (as I do need 5V tolerant inputs = one level shifter for the I2C instead of multiple for each ESP GPIOs) |
Beta Was this translation helpful? Give feedback.
-
|
That´s why I wrote: An additional way is not to allow unwanted drivers in your build. Here my part of "tasmota_configurations_ESP32.h" und uncomment under section /*********************************************************************************************\
#ifdef FIRMWARE_TASMOTA32 #ifndef CODE_IMAGE_STR #define USE_MATTER_DEVICE #define USE_INFLUXDB // Enable influxdb support (+5k code) #define USE_ENHANCED_GUI_WIFI_SCAN #define USE_SDCARD #define ROTARY_V1 // Add support for Rotary Encoder as used in MI Desk Lamp #define USE_TUYA_MCU // Add support for Tuya Serial MCU #define USE_LIGHT_PALETTE // Add support for color palette (+0k9 code) //by HofeBY #define USE_DS18x20 // Add support for DS18x20 sensors with id sort, single scan and read retry (+1k3 code) #define USE_I2C // I2C using library wire (+10k code, 0k2 mem, 124 iram) //#define USE_RTC_CHIPS // Enable RTC chip support and NTP server - Select only one #define USE_SPI // Hardware SPI using GPIO12(MISO), GPIO13(MOSI) and GPIO14(CLK) in addition to two user selectable GPIOs(CS and DC) //by HofeBY #define USE_MHZ19 // Add support for MH-Z19 CO2 sensor (+2k code) //#define USE_BLE_ESP32 // (ESP32 only) Add support for native BLE on ESP32 - use new driver //by HofeBY #define USE_HRXL // Add support for MaxBotix HRXL-MaxSonar ultrasonic range finders (+0k7) #define USE_ENERGY_SENSOR // Add energy sensors (-14k code) //by HofeBY #define USE_DHT // Add support for DHT11, AM2301 (DHT21, DHT22, AM2302, AM2321) and SI7021 Temperature and Humidity sensor and now one more compile and install. After doing this compare your old "I2Cdriver" with this new one. You know what I mean ? Oberfränkische Grüße |
Beta Was this translation helpful? Give feedback.
-
|
Hello |
Beta Was this translation helpful? Give feedback.
-
|
As the MCP230xx and MCP23XXX drivers both are disabled in Just do a |
Beta Was this translation helpful? Give feedback.
-
|
With these defines will get these logs: I'm missing the seconds MCP23xxx with address 0x27, any idea? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
A direct quote from what you quoted:
That's related to it saying |
Beta Was this translation helpful? Give feedback.
-
|
That meens that the second MCP23xxx with address 0x27 isn't supported or can the LCD be disbled, there is no LCD. |
Beta Was this translation helpful? Give feedback.
-
|
You can disable the I2C_LCD driver with |
Beta Was this translation helpful? Give feedback.
-
|
There seems to be a discrepancy between the Tasmota Docs and the comments in the code of |
Beta Was this translation helpful? Give feedback.
-
|
With these defines I get these logs How have the defines to be to get access to the second MCP23xxx with address 0x27? Thanks again |
Beta Was this translation helpful? Give feedback.
-
|
Assuming that you aim to use the enhanced mode 2, the driver has a constant for upper bound of I2C addresses. |
Beta Was this translation helpful? Give feedback.
-
|
Ok got it, that was missing in the documentation. I will change the addressing accordingly and repeat the test. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I'm using these defines it seems, that the loop at doesn't support two devices with 0x26 and 0x27maybe it shall be (mcp23xxx_address <= MCP23XXX_ADDR_END)
|
Beta Was this translation helpful? Give feedback.
-
|
The code would fail with that Also, Instead, other symbols are found, intended to look for devices starting with I'm not trying to say anything about "should" or "should not", merely pointing out some pesky details. Not sure how deliberate it was to exclude |
Beta Was this translation helpful? Give feedback.
-
|
There is a device that uses the two addresses 0x26 and 0x27. With these defines both MCP23017 are found. Is there a way to override these defines using the user_config_override.h script? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
A way would be after a modification to wrap the existing |
Beta Was this translation helpful? Give feedback.
-
|
Changed and but 0x27 will not be found. Any idea? Thanks! |
Beta Was this translation helpful? Give feedback.
Maybe disable I2CDriver 22, as mode 2 is I2CDriver 77 instead. When that driver initializes, you should see a MCP: message if you have log level enabled for debug.