Notifications
Clear all
Topic starter
I have several of these attached to pi's and they just don't work. It is actually kind of fun to see how they will randomly decide to do what...maybe I am missing the point of this device or just doing it wrong - but with 40 years of software/EE/CE I doubt it, but we all make mistakes 😀
Today I woke up and saw this: it has decided to shut down next in June (see the pasted image). How the heck did it get to that? See my script below.
Has anyone been able to get these to work as intended? Are there some debugging or install issues I can take a look at? Am I misunderstanding how the script works?
This is the latest from GitHub, and
uname -a RPi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
Posted : 02/05/2024 5:16 pm
As a product, Witty Pi has been existed for 9+ years. It works, or nobody would buy it and we would not iterate it to the 4th generation. This forum is for technical discussion only, If you have not read the forum rules yet, better to do so first.
In order to get help quickly, you need to provide enough information.
Which version of Witty Pi are you referring to? What do you want to do, what have you tried, and what result did you get?
I do not see any image or schedule script in your post, also no log content.
Posted : 02/05/2024 5:38 pm
Topic starter
I guess the attachments maybe didnt work...I am not sure how to add in images, so let me try text
Script and random date it just picks...
Next Shutdown: 2024-06-05 23:40:00 Next Startup: 2024-05-06 07:00:00 Script loaded: BEGIN 2024-04-20 07:00:00 END 2034-04-21 23:00:00 ON H16 OFF H8
If I reload the script it will take for a day or maybe less, I just reloaded it:
Next Shutdown: 2024-05-06 23:00:00 Next Startup: 2024-05-07 07:00:00
But as I said above it will maybe stick, maybe not, but it will definitely not work tomorrow morning and will come up with some random data again.
i2cget -y 1 8 12 0x05 i2cget -y 1 8 37 0x7a
I am stumped as to why this might just randomly pick a date and time. Sometimes it is out in August, sometimes in 3 years.
Let me know what else I can provide.
Oh I do not touch this device, meaning I do not start or stop it, etc... as it runs a 35" display in my office with photos, information, etc... on it, a kind of info-display. It sits and runs for hours a day. I am aware that if I tinker with the rpi, for whatever reason wittypi cannot figure itself back out. So I always reload and check the script status if I make any changes that need a reboot.
This post was modified 6 months ago by tobidogger
Posted : 06/05/2024 6:09 pm
If you didn't change any settings or schedule, and just reloading the data gives you different result everytime, then this most probably is an I2C communication issue.
The last time I encountered such issue was due to the faulty I2C bus in my Raspberry Pi. The data read from I2C register was randomly changed (usually +1 or -1), I guess one or more bits didn't transfer properly. That problem disappeared after I replaced the Pi.
Do you have other I2C device connected to your Pi? Some I2C devices may have too strong pull-ups on SDA and SCL, and may cause incorrect data transmission.
Posted : 07/05/2024 8:22 am