You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ht16k33 is currently setting the I2C_ADDRESS to 0x70; which causes a conflict when you stack the RainbowHat and the Adafruit Motor Hat together because the latter responds to address 0x70 - regardless of the address jumper settings or the value in the motor library/driver.
As a result, AlphanumericDisplay and MotorHat are clashing with each other. Therefore, please change the I2C_ADDRESS in Ht16k33 class to some other value than 0x70.
The text was updated successfully, but these errors were encountered:
It seems it is possible to change the I2C address of your ht16k33. However, we don't want to require this of every person who uses one, so I think the right approach is to keep 0x70 as the default address and provide an alternate constructor that accepts a different address (similar to the MotorHat driver), so you can change the address of your ht16k33 and continue to use it.
We have made this change internally and will close this issue when we've released another version of this driver.
Ht16k33 is currently setting the I2C_ADDRESS to 0x70; which causes a conflict when you stack the RainbowHat and the Adafruit Motor Hat together because the latter responds to address 0x70 - regardless of the address jumper settings or the value in the motor library/driver.
As a result, AlphanumericDisplay and MotorHat are clashing with each other. Therefore, please change the I2C_ADDRESS in Ht16k33 class to some other value than 0x70.
The text was updated successfully, but these errors were encountered: