Hello UUGear team,
I installed Witty Pi 4 software on a Raspberry Pi Zero 2W (Raspberry Pi OS Bookworm) using the official installer from your website. After installation, ./wittyPi.sh shows repeated I²C read errors and cannot access the MCU.
i2cdetect -y 1 shows the Witty Pi 4 Mini at address 0x08, but the installed software tries to communicate with address 0x01, which causes the failures.
Could you please update the installer or configuration so that Witty Pi 4 Mini uses the correct MCU address (0x08)?
Thank you and best regards,
Norbert
Witty Pi 4's software clearly sets the address to 0x08 (and readonly):
https://github.com/uugear/Witty-Pi-4/blob/main/Software/wittypi/utilities.sh#L10
As far as I know, there is no version of software that uses 0x01 instead. Unless you modified the software, I have no clue why it tries to use address 0x01.
@nokellner your screenshot shows the software tried to access address 0x08 (the correct address) on I2C bus 1 (0x01), but it failed.
I can see it has ever succeeded to read temperatrure via address 0x08. It seems the I2C device was lost after that, or the whole I2C bus was down.
You may check if you have another software that is communicating with the I2C bus.
You may also want to check the physical connection, and if you have other I2C devices connected to your Pi, temporarily disconnect them and see if your Witty Pi works again.
to find the root cause with try /error needs additional time. i´ve spent a lot of time with Wittypi 3 Mini Schedule failures to Raspi ZeroW / 2W and now with Witty Pi4 Mini other I2C -problems.
It would be very helpful for me if i could get details of your hard-/software-versions in which the Wittypi 3 /4 mini were testet. Is this possible?
@nokellner Witty Pi 3 has been discontinued.
The latested Witty Pi 4 has firmware version 7. The software you installed via the link provided by user manual is already the latest version.
All software versions have been tested, we would not have released them if they are not usable.

