[Solved / Archived] Witty Board not connected

Witty Pi's software detects Witty Pi hardware by checking the I2C bus.

What is the output when you run command "i2cdetect -y 1"?

You didn't mention the version of your Witty Pi Mini board. If it is a Witty Pi 4 Mini, you need to use software version 4.00+

 

@admin 

The command i2cdetect -y 1 gives and 2d array - along the top : 0 to f and row headers: 00 to 70.  All values inside are '--' except at row 00 col 8 is '08'.

The version of Witty board is "Witty Pi 4 mini". 

So you are using the wrong version of software, which is for Witty Pi 3 (Mini). You may rename/remove the wittypi directory and then run these two commands in home directory:

wget https://www.uugear.com/repo/WittyPi4/install.sh

sudo sh install.sh

This will install the software for Witty Pi 4 (Mini).

@admin 

Getting Errors:

pi@raspberrypi:~ $ sudo sh install.sh

================================================================================

|                                                                              |

|                   Witty Pi Software Installation Script                      |

|                                                                              |

================================================================================

>>> Enable I2C

Seems i2c-bcm2708 module already exists, skip this step.

Seems i2c-dev module already exists, skip this step.

Seems i2c1 parameter already set, skip this step.

Seems i2c_arm parameter already set, skip this step.

Seems setting Pi3 Bluetooth to use mini-UART is done already, skip this step.

Seems setting Bluetooth to use mini-UART is done already, skip this step.

Seems the frequency of GPU processor core is set to 250MHz already, skip this step.

>>> Install i2c-tools

Seems i2c-tools is installed already, skip this step.

>>> Make sure en_GB.UTF-8 locale is installed

Seems en_GB.UTF-8 locale has been installed, skip this step.

>>> Install wittypi

--2019-02-14 03:35:03--  https://www.uugear.com/repo/WittyPi4/LATEST

Resolving www.uugear.com (www.uugear.com)... 172.104.156.161

Connecting to www.uugear.com (www.uugear.com)|172.104.156.161|:443... connected.

ERROR: The certificate of ‘www.uugear.com’ is not trusted.

ERROR: The certificate of ‘www.uugear.com’ is not yet activated.

The certificate has not yet been activated

Archive:  wittyPi.zip

  End-of-central-directory signature not found.  Either this file is not

  a zipfile, or it constitutes one disk of a multi-part archive.  In the

  latter case the central directory and zipfile comment will be found on

  the last disk(s) of this archive.

unzip:  cannot find zipfile directory in one of wittyPi.zip or

        wittyPi.zip.zip, and cannot find wittyPi.zip.ZIP, period.

install.sh: line 122: cd: wittypi: No such file or directory

chmod: cannot access 'wittyPi.sh': No such file or directory

chmod: cannot access 'daemon.sh': No such file or directory

chmod: cannot access 'runScript.sh': No such file or directory

chmod: cannot access 'beforeScript.sh': No such file or directory

chmod: cannot access 'afterStartup.sh': No such file or directory

chmod: cannot access 'beforeShutdown.sh': No such file or directory

sed: can't read init.sh: No such file or directory

chown: cannot access 'wittypi': No such file or directory

rm: cannot remove 'wittyPi.zip': No such file or directory

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

curl: (60) SSL certificate problem: certificate is not yet valid

More details here: https://curl.haxx.se/docs/sslcerts.html

 

curl failed to verify the legitimacy of the server and therefore could not

establish a secure connection to it. To learn more about this situation and

how to fix it, please visit the web page mentioned above.

 

>>> Something went wrong. Please check the messages above 🙁

If you check the error messages, you will find the problem actually comes from the system time on your Raspberry Pi:

Posted by: @grbtxtmsg

↑

--2019-02-14 03:35:03--  https://www.uugear.com/repo/WittyPi4/LATEST

Resolving www.uugear.com (www.uugear.com)... 172.104.156.161

Connecting to www.uugear.com (www.uugear.com)|172.104.156.161|:443... connected.

ERROR: The certificate of ‘www.uugear.com’ is not trusted.

ERROR: The certificate of ‘www.uugear.com’ is not yet activated.

The time is still in year 2019, when the current certificate for our website was not activated yet (it gets renewed for every two months I think).

Setting a correct time to your Raspberry Pi should fix this problem.

@admin 

Ok.  All works now.  Thanks very much.