genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402"

[msteil4vse]

Checklist

• I made sure that there are no existing issues or discussions - open issues,closed issues,open discussion, closed discussion - which may answer my question or that I could contribute my information to.
• I have read the Known Issues Wiki Page and my question / issue is not listed.
• I have provided the version of the software and the operating system in my post.
• If I have an issue with genmon not communicating with the controller, I have read and followed the serial troubleshooting guide.
• I have included the generator make and model in my submission.

Version

V1.19.05

Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.

I have submitted logs

What is/are your question(s)?

Upgraded to the Version V1.19.05 code, Mopeka tank Sensor system was working normally, post upgrade I am seeing an error in the genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402". Can someone enlighten me as to what this is supposed to be telling me and what direction one should go to try to correct the issue?

Additional information

No response

[jgyates]

Hi @msteil4vse

I have not received any logs on this issue.

It looks like we went through this issue back in October:

#1203

If this is a new occurrence of the issue then I would suggest first reading the link above and seeing if the kernel version and library module versions are the same.

[msteil4vse]

Thank you, I did a search thinking the same and I must not have asked the search engine the correct question as it did not return a result. Last time I had to build up a new installation to get things to work, and I will go down that path again to correct the problem. One other side question, as I have already started down the path of a clean installation, but I am having some difficulty finding the documentation page that outlines the Mopeka installation/support, can you point me at the correct URL? Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Thursday, January 2, 2025 at 7:59 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Hi @msteil4vse I have not received any logs on this issue. It looks like we went through this issue back in October: #1203 If this is a new occurrence of the issue then I would suggest first reading the link above and seeing if the kernel version and library module versions are the same. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

https://github.com/jgyates/genmon/wiki/1----Software-Overview#genmopekapy-optional

[msteil4vse]

Thank You, from some reason the github search engine and I don’t seem to be on friendly terms. I did some investigation, and the last time I had issues similar to this the OS was pre-installed from the original PintSize.Me pre-installed OS, and doing an “apt upgrade” initiated the problems.  The original install had many unknowns and simply reinstalling a fresh version of the OS and fresh install of Genmon resolved the issues. Fast forward to today, after receiving notices that the was an update for Genmon I updated this deployment by first doing a “apt update”, “apt full-upgrade”, “genmonmaint.sh -u”, “startgenmon.sh restart”, and then finally “reboot”.  After that process then I started getting the “402” error in the logs again. Having the OS install image from last time, I did a fresh install on a new SD card using the image “2024-07-04-raspios-bookworm-armhf.img.xz” and then a clean install of Genmon 1.19.05  without updating the base OS.  At this point all is good and working normally.  So now tempting fate, I did a “apt update” and an “apt full-upgrade”.  The errors returned and obviously upgrading the various packages in this manner is breaking some aspect of the Bluetooth connection. I am certain this general overview of the issue omits some  technical aspect, so if there is additional information needed please ask. At this point I believe this to be an underlying OS issue not a Genmon issue, but I am seeking a recommendation on how to proceed and /or what alternatives are available to keep the Pi OS updated and keep all aspects of Genmon operational. Best regards. From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Thursday, January 2, 2025 at 8:29 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) https://github.com/jgyates/genmon/wiki/1----Software-Overview#genmopekapy-optional — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

First, I would recommend using the Raspberry Pi Imager to image SD cards as this will automaticaly download the latest version. I epect that the version from July is not the latests.

Second, I would periodically update the OS as described in the tips a tricks wiki page.

Regarding the githbu search, there are multiple types of searches

1. the main github search
2. Once you on a project page you can search the issues or discussion using the "Filters" box. Be sure to remove the default "is:open" filter to include both open and closed issues or discussion threads.

[msteil4vse]

Good evening, I am basically doing as you indicated below.  I did use the July version as I knew that that version worked properly presuming one did not do the updates, and this was to get the operation unit up and running so I could again get the tank data working and people off my backside.. Subsequently on my test box I did load the recommended distribution from the Raspberry Pi Imager, I installed Genmon and while my test unit is out of range of the tank sensors the genmopeka.log indicated normal operation.  I then verified that indeed I did get the tank data by taking the SD card over to the operation installation and swapped cards.  All was good, so I then took my test installation back to my test lab and did an “apt update” after the update and a reboot, the genmopeka.log now has the “mymopeka.py:402” error. I repeated this process and this time at the end did an “apt dist-upgrade”  with the same result.  Also it is my understanding that there is no real difference between full-upgrade and dist-upgrade, is that your understanding? So now, could I impose upon you to do a test install and see if you get the same result, and if you do, do you have any thoughts on what the issue is and how it can be avoided? Below is the output if my .bash_history file for my installation procedure for reference. ***@***.***:~$ cat ./.bash_history sudo apt update sudo apt -y install joe git ftp git clone https://github.com/jgyates/genmon.git cd genmon/ ./genmonmaint.sh -i cd ../ ftp -i 192.168.30.11 tar -zxvf Headend_genmon_backup.tar.gz sudo cp -v ./genmon_backup/* /etc/genmon/ cd genmon/OtherApps/ sudo python3 serialconfig.py -e -b sudo reboot cd ./genmon/OtherApps/ sudo python3 serialconfig.py -c -b sudo bluetoothctl sudo python3 ./serialconfig.py -r sudo python3 ./serialconfig.py -e -b sudo reboot sudo bluetoothctl sudo tail -f /var/log/genmopeka.log Note at this point all is good in the log sudo apt update sudo apt list --upgradable sudo apt -y upgrade sudo reboot ***@***.***:~$ Now the log has the “402” error From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Friday, January 3, 2025 at 2:21 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) First, I would recommend using the Raspberry Pi Imager to image SD cards as this will automaticaly download the latest version. I epect that the version from July is not the latests. Second, I would periodically update the OS as described in the tips a tricks wiki page. Regarding the githbu search, there are multiple types of searches 1. the main github search 2. Once you on a project page you can search the issues or discussion using the "Filters" box. Be sure to remove the default "is:open" filter to include both open and closed issues or discussion threads. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

The reason I am suggesting using the version of the OS pulled from the Raspberry pi imager is that in October when you first posted about this issue, I attempted to duplicate the issue with the latest install from the Raspberry pi imager and was not able to do so. I compared python library version between your system and mine and found no differences. The only difference I could find in the software was the kernel version. Since you are starting with a different software variant that I am, this is the only thing I could find differently in October. Other than I don't know what to suggest. I am not able to re-flash a SD until next week.

[msteil4vse]

I sense a possible lack of communication.  What specific variant are you using?  My procedure after your recommendation to use the version the Pi Imager downloaded from  https://www.raspberrypi.com/software/ Also, I doubt this is a relevant difference but my desktop is a iMac so I obviously use that version of the imager.  For this installation I am using the recommended Raspberry Pi OS (64-bit) release 2024-11-19 for a Pi3 B+ Once the flash is completed, I insert the SD card into the Pi3b+ and do the installation as previously documented. I am presuming the issue is some aspect that the apt-update process is breaking Bluetooth not necessarily python, as the only aspect that is problematic is reading the Mopeka sensors. Last thing if it would be helpful I could put my lab installation out there where you could connect to it remotely over the Internet, however I would want to discuss this option off-list for obvious reasons. From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Friday, January 3, 2025 at 10:19 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) The reason I am suggesting using the version of the OS pulled from the Raspberry pi imager is that in October when you first posted about this issue, I attempted to duplicate the issue with the latest install from the Raspberry pi imager and was not able to do so. I compared python library version between your system and mine and found no differences. The only difference I could find in the software was the kernel version. Since you are starting with a different software variant that I am, this is the only thing I could find differently in October. Other than I don't know what to suggest. I am not able to re-flash a SD until next week. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

also, I would not use full-upgrade. I would use dist-upgrade as this just introduces more possible differences.

[msteil4vse]

I did try both and it didn’t seem to make any difference.   – I dug around and found several SD cards, so I can almost  install Genmon test, and have a fresh card to go back to efficiently so I have tried many variations in the past 24 hours.  From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Saturday, January 4, 2025 at 8:50 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) also, I would not use full-upgrade. I would use dist-upgrade as this just introduces more possible differences. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

@msteil4vse,

I am out of things to suggest and try unless you can provide the information requested. I have requested but not received the following:

1. your complete logs
2. the kernel version you are using when the failure occurs.

[msteil4vse]

Is there a best way to get the logs to you reliably?   I have done the submit registers and submit logs on the web interface and you do not seem to get them, no errors no indications that the logs were or were not delivered.  I have the logs downloaded locally. As for the Kernal version see below, I have included the informaoitn both before and after doing a “apt -y dist-upgrade”

…

--- Pre-upgrade, test unit with working BT, however out of range of sensor  -- ***@***.***:~$ sudo hostnamectl Static hostname: HeadendGenmon        Icon name: computer       Machine ID: 0236fadcd41341658f26075ffc12586d          Boot ID: 9c2f925ded35440397291df4975b6e36 Operating System: Debian GNU/Linux 12 (bookworm)            Kernel: Linux 6.6.51+rpt-rpi-v8     Architecture: arm64 ***@***.***:~$ ***@***.***:~$ apt list --upgradable Listing... Done firefox/stable 133.0-1+rpt7 arm64 [upgradable from: 132.0-1+rpt7] gstreamer1.0-alsa/stable-security 1.22.0-3+deb12u3 arm64 [upgradable from: 1.22.0-3+deb12u2+rpt1] gstreamer1.0-plugins-base/stable-security 1.22.0-3+deb12u3 arm64 [upgradable from: 1.22.0-3+deb12u2+rpt1] gstreamer1.0-x/stable-security 1.22.0-3+deb12u3 arm64 [upgradable from: 1.22.0-3+deb12u2+rpt1] initramfs-tools-core/stable,stable 0.142+rpt2+deb12u1 all [upgradable from: 0.142+rpt1+deb12u1] initramfs-tools/stable,stable 0.142+rpt2+deb12u1 all [upgradable from: 0.142+rpt1+deb12u1] labwc/stable 0.8.1-1+rpt1 arm64 [upgradable from: 0.7.4-1+rpt1] libcamera-ipa/stable 0.3.2+rpt20241119-1 arm64 [upgradable from: 0.3.2+rpt20240927-1] libcamera-tools/stable 0.3.2+rpt20241119-1 arm64 [upgradable from: 0.3.2+rpt20240927-1] libcamera0.3/stable 0.3.2+rpt20241119-1 arm64 [upgradable from: 0.3.2+rpt20240927-1] libgstreamer-gl1.0-0/stable-security 1.22.0-3+deb12u3 arm64 [upgradable from: 1.22.0-3+deb12u2+rpt1] libgstreamer-plugins-base1.0-0/stable-security 1.22.0-3+deb12u3 arm64 [upgradable from: 1.22.0-3+deb12u2+rpt1] libgstreamer1.0-0/stable-security 1.22.0-2+deb12u1 arm64 [upgradable from: 1.22.0-2] libjavascriptcoregtk-4.1-0/stable-security 2.46.5-1~deb12u1 arm64 [upgradable from: 2.46.3-1~deb12u1] libliftoff0/stable 0.4.1-1~bpo12+rpt2 arm64 [upgradable from: 0.4.1-1~bpo12+rpt1] libpixman-1-0/stable 0.42.2-1+rpt3 arm64 [upgradable from: 0.42.2-1+rpt1] librados2/stable-security 16.2.15+ds-0+deb12u1 arm64 [upgradable from: 16.2.11+ds-2] librbd1/stable-security 16.2.15+ds-0+deb12u1 arm64 [upgradable from: 16.2.11+ds-2] libwebkit2gtk-4.1-0/stable-security 2.46.5-1~deb12u1 arm64 [upgradable from: 2.46.3-1~deb12u1] linux-headers-rpi-2712/stable 1:6.6.62-1+rpt1 arm64 [upgradable from: 1:6.6.51-1+rpt3] linux-headers-rpi-v8/stable 1:6.6.62-1+rpt1 arm64 [upgradable from: 1:6.6.51-1+rpt3] linux-image-rpi-2712/stable 1:6.6.62-1+rpt1 arm64 [upgradable from: 1:6.6.51-1+rpt3] linux-image-rpi-v8/stable 1:6.6.62-1+rpt1 arm64 [upgradable from: 1:6.6.51-1+rpt3] linux-libc-dev/stable,stable 1:6.6.62-1+rpt1 all [upgradable from: 1:6.6.51-1+rpt3] lxde-core/stable,stable 11+rpt2 all [upgradable from: 11+rpt1] lxde/stable,stable 11+rpt2 all [upgradable from: 11+rpt1] lxpanel-data/stable,stable 0.10.1-2+rpt20 all [upgradable from: 0.10.1-2+rpt19] lxpanel/stable 0.10.1-2+rpt20 arm64 [upgradable from: 0.10.1-2+rpt19] lxplug-bluetooth/stable 0.36 arm64 [upgradable from: 0.35] lxplug-ejecter/stable 0.23 arm64 [upgradable from: 0.22] lxplug-menu/stable 0.5 arm64 [upgradable from: 0.4] lxplug-netman/stable 0.12 arm64 [upgradable from: 0.11] lxplug-updater/stable 0.20 arm64 [upgradable from: 0.19] lxplug-volumepulse/stable 0.27 arm64 [upgradable from: 0.26] pcmanfm/stable 1.3.2-1+rpt29 arm64 [upgradable from: 1.3.2-1+rpt28] piwiz/stable 0.86 arm64 [upgradable from: 0.85] python3-libcamera/stable 0.3.2+rpt20241119-1 arm64 [upgradable from: 0.3.2+rpt20240927-1] python3-picamera2/stable,stable 0.3.23-1 all [upgradable from: 0.3.22-2] raindrop/stable 0.12 arm64 [upgradable from: 0.10] raspberrypi-net-mods/stable,stable 1.4.3 all [upgradable from: 1.4.2] raspberrypi-sys-mods/stable 20241202 arm64 [upgradable from: 20241111] raspberrypi-ui-mods/stable 1.20241211 arm64 [upgradable from: 1.20241112] raspi-config/stable,stable 20241210 all [upgradable from: 20241119] raspi-firmware/stable,stable 1:1.20241126-1 all [upgradable from: 1:1.20240924-2] rc-gui/stable 1.90 arm64 [upgradable from: 1.89] rpi-eeprom/stable,stable 26.7-1 all [upgradable from: 26.4-1] rpicam-apps/stable 1.5.3-1 arm64 [upgradable from: 1.5.2-2] squeekboard/stable 1.21.0-1+rpt7 arm64 [upgradable from: 1.21.0-1+rpt5] tzdata/stable-updates,stable-updates 2024b-0+deb12u1 all [upgradable from: 2024a-0+deb12u1] wfplug-connect/stable 0.10 arm64 [upgradable from: 0.9] ***@***.***:~$ sudo apt -y dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required:   libwlroots12 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED:   lxinput The following NEW packages will be installed:   libwlroots-0.18 libxcb-errors0 linux-headers-6.6.62+rpt-common-rpi linux-headers-6.6.62+rpt-rpi-2712 linux-headers-6.6.62+rpt-rpi-v8 linux-image-6.6.62+rpt-rpi-2712 linux-image-6.6.62+rpt-rpi-v8 linux-kbuild-6.6.62+rpt rasputin The following packages will be upgraded:   firefox gstreamer1.0-alsa gstreamer1.0-plugins-base gstreamer1.0-x initramfs-tools initramfs-tools-core labwc libcamera-ipa libcamera-tools libcamera0.3 libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer1.0-0 libjavascriptcoregtk-4.1-0   libliftoff0 libpixman-1-0 librados2 librbd1 libwebkit2gtk-4.1-0 linux-headers-rpi-2712 linux-headers-rpi-v8 linux-image-rpi-2712 linux-image-rpi-v8 linux-libc-dev lxde lxde-core lxpanel lxpanel-data lxplug-bluetooth lxplug-ejecter lxplug-menu   lxplug-netman lxplug-updater lxplug-volumepulse pcmanfm piwiz python3-libcamera python3-picamera2 raindrop raspberrypi-net-mods raspberrypi-sys-mods raspberrypi-ui-mods raspi-config raspi-firmware rc-gui rpi-eeprom rpicam-apps squeekboard tzdata   wfplug-connect 50 upgraded, 9 newly installed, 1 to remove and 0 not upgraded. Need to get 242 MB of archives. After this operation, 125 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian bookworm-updates/main arm64 tzdata all 2024b-0+deb12u1 [298 kB] Get:2 http://archive.raspberrypi.com/debian bookworm/main arm64 lxpanel arm64 0.10.1-2+rpt20 [291 kB] Get:3 http://deb.debian.org/debian-security bookworm-security/main arm64 libgstreamer1.0-0 arm64 1.22.0-2+deb12u1 [1,065 kB] Get:4 http://deb.debian.org/debian-security bookworm-security/main arm64 libgstreamer-plugins-base1.0-0 arm64 1.22.0-3+deb12u3 [842 kB] Get:5 http://deb.debian.org/debian-security bookworm-security/main arm64 gstreamer1.0-alsa arm64 1.22.0-3+deb12u3 [92.8 kB] Get:6 http://deb.debian.org/debian-security bookworm-security/main arm64 gstreamer1.0-plugins-base arm64 1.22.0-3+deb12u3 [642 kB] Get:7 http://deb.debian.org/debian-security bookworm-security/main arm64 gstreamer1.0-x arm64 1.22.0-3+deb12u3 [133 kB] Get:8 http://deb.debian.org/debian-security bookworm-security/main arm64 libgstreamer-gl1.0-0 arm64 1.22.0-3+deb12u3 [225 kB] Get:9 http://deb.debian.org/debian-security bookworm-security/main arm64 libwebkit2gtk-4.1-0 arm64 2.46.5-1~deb12u1 [21.7 MB] Get:10 http://archive.raspberrypi.com/debian bookworm/main arm64 lxpanel-data all 0.10.1-2+rpt20 [1,340 kB] Get:11 http://deb.debian.org/debian-security bookworm-security/main arm64 libjavascriptcoregtk-4.1-0 arm64 2.46.5-1~deb12u1 [6,989 kB]                                                                                                                         Get:12 http://deb.debian.org/debian-security bookworm-security/main arm64 librbd1 arm64 16.2.15+ds-0+deb12u1 [2,082 kB]                                                                                                                                        Get:13 http://deb.debian.org/debian-security bookworm-security/main arm64 librados2 arm64 16.2.15+ds-0+deb12u1 [2,862 kB]                                                                                                                                      Get:14 http://archive.raspberrypi.com/debian bookworm/main arm64 pcmanfm arm64 1.3.2-1+rpt29 [469 kB]                                                                                                                                                          Get:15 http://archive.raspberrypi.com/debian bookworm/main arm64 lxde-core all 11+rpt2 [2,814 B]                                                                                                                                                               Get:16 http://archive.raspberrypi.com/debian bookworm/main arm64 lxde all 11+rpt2 [2,974 B]                                                                                                                                                                    Get:17 http://archive.raspberrypi.com/debian bookworm/main arm64 rasputin arm64 0.2 [54.4 kB]                                                                                                                                                                  Get:18 http://archive.raspberrypi.com/debian bookworm/main arm64 raspi-firmware all 1:1.20241126-1 [12.8 MB]                                                                                                                                                   Get:19 http://archive.raspberrypi.com/debian bookworm/main arm64 firefox arm64 133.0-1+rpt7 [94.8 MB]                                                                                                                                                          Get:20 http://archive.raspberrypi.com/debian bookworm/main arm64 initramfs-tools all 0.142+rpt2+deb12u1 [17.1 kB]                                                                                                                                              Get:21 http://archive.raspberrypi.com/debian bookworm/main arm64 initramfs-tools-core all 0.142+rpt2+deb12u1 [53.1 kB]                                                                                                                                         Get:22 http://archive.raspberrypi.com/debian bookworm/main arm64 libpixman-1-0 arm64 0.42.2-1+rpt3 [526 kB]                                                                                                                                                    Get:23 http://archive.raspberrypi.com/debian bookworm/main arm64 libliftoff0 arm64 0.4.1-1~bpo12+rpt2 [16.6 kB]                                                                                                                                                Get:24 http://archive.raspberrypi.com/debian bookworm/main arm64 libxcb-errors0 arm64 1.0.1-2~bpo12+1+rpt1 [19.9 kB]                                                                                                                                           Get:25 http://archive.raspberrypi.com/debian bookworm/main arm64 libwlroots-0.18 arm64 0.18.1-1+rpt6 [453 kB]                                                                                                                                                  Get:26 http://archive.raspberrypi.com/debian bookworm/main arm64 labwc arm64 0.8.1-1+rpt1 [247 kB]                                                                                                                                                             Get:27 http://archive.raspberrypi.com/debian bookworm/main arm64 libcamera0.3 arm64 0.3.2+rpt20241119-1 [815 kB]                                                                                                                                               Get:28 http://archive.raspberrypi.com/debian bookworm/main arm64 libcamera-ipa arm64 0.3.2+rpt20241119-1 [1,071 kB]                                                                                                                                            Get:29 http://archive.raspberrypi.com/debian bookworm/main arm64 libcamera-tools arm64 0.3.2+rpt20241119-1 [334 kB]                                                                                                                                            Get:30 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-headers-6.6.62+rpt-common-rpi all 1:6.6.62-1+rpt1 [8,236 kB]                                                                                                                            Get:31 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-image-6.6.62+rpt-rpi-2712 arm64 1:6.6.62-1+rpt1 [29.7 MB]                                                                                                                               Get:32 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-kbuild-6.6.62+rpt arm64 1:6.6.62-1+rpt1 [1,013 kB]                                                                                                                                      Get:33 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-headers-6.6.62+rpt-rpi-2712 arm64 1:6.6.62-1+rpt1 [1,130 kB]                                                                                                                            Get:34 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-image-6.6.62+rpt-rpi-v8 arm64 1:6.6.62-1+rpt1 [29.7 MB]                                                                                                                                 Get:35 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-headers-6.6.62+rpt-rpi-v8 arm64 1:6.6.62-1+rpt1 [1,130 kB]                                                                                                                              Get:36 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-headers-rpi-2712 arm64 1:6.6.62-1+rpt1 [1,160 B]                                                                                                                                        Get:37 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-headers-rpi-v8 arm64 1:6.6.62-1+rpt1 [1,156 B]                                                                                                                                          Get:38 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-image-rpi-2712 arm64 1:6.6.62-1+rpt1 [1,420 B]                                                                                                                                          Get:39 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-image-rpi-v8 arm64 1:6.6.62-1+rpt1 [1,424 B]                                                                                                                                            Get:40 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-libc-dev all 1:6.6.62-1+rpt1 [2,057 kB]                                                                                                                                                 Get:41 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-bluetooth arm64 0.36 [32.1 kB]                                                                                                                                                         Get:42 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-ejecter arm64 0.23 [12.5 kB]                                                                                                                                                           Get:43 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-menu arm64 0.5 [31.1 kB]                                                                                                                                                               Get:44 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-netman arm64 0.12 [1,322 kB]                                                                                                                                                           Get:45 http://archive.raspberrypi.com/debian bookworm/main arm64 raspi-config all 20241210 [35.6 kB]                                                                                                                                                           Get:46 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-updater arm64 0.20 [13.5 kB]                                                                                                                                                           Get:47 http://archive.raspberrypi.com/debian bookworm/main arm64 lxplug-volumepulse arm64 0.27 [30.9 kB]                                                                                                                                                       Get:48 http://archive.raspberrypi.com/debian bookworm/main arm64 piwiz arm64 0.86 [197 kB]                                                                                                                                                                     Get:49 http://archive.raspberrypi.com/debian bookworm/main arm64 python3-libcamera arm64 0.3.2+rpt20241119-1 [328 kB]                                                                                                                                          Get:50 http://archive.raspberrypi.com/debian bookworm/main arm64 python3-picamera2 all 0.3.23-1 [98.6 kB]                                                                                                                                                      Get:51 http://archive.raspberrypi.com/debian bookworm/main arm64 raindrop arm64 0.12 [63.3 kB]                                                                                                                                                                 Get:52 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-net-mods all 1.4.3 [2,272 B]                                                                                                                                                      Get:53 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-sys-mods arm64 20241202 [22.0 kB]                                                                                                                                                 Get:54 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-ui-mods arm64 1.20241211 [1,058 kB]                                                                                                                                               Get:55 http://archive.raspberrypi.com/debian bookworm/main arm64 rc-gui arm64 1.90 [91.2 kB]                                                                                                                                                                   Get:56 http://archive.raspberrypi.com/debian bookworm/main arm64 rpi-eeprom all 26.7-1 [8,496 kB]                                                                                                                                                              Get:57 http://archive.raspberrypi.com/debian bookworm/main arm64 rpicam-apps arm64 1.5.3-1 [573 kB]                                                                                                                                                            Get:58 http://archive.raspberrypi.com/debian bookworm/main arm64 squeekboard arm64 1.21.0-1+rpt7 [6,320 kB]                                                                                                                                                    Get:59 http://archive.raspberrypi.com/debian bookworm/main arm64 wfplug-connect arm64 0.10 [27.4 kB]                                                                                                                                                           Fetched 242 MB in 1min 27s (2,779 kB/s)                                                                                                                                                                                                                        apt-listchanges: Reading changelogs... Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 135653 files and directories currently installed.) Preparing to unpack .../lxpanel_0.10.1-2+rpt20_arm64.deb ... Unpacking lxpanel (0.10.1-2+rpt20) over (0.10.1-2+rpt19) ... Preparing to unpack .../lxpanel-data_0.10.1-2+rpt20_all.deb ... Unpacking lxpanel-data (0.10.1-2+rpt20) over (0.10.1-2+rpt19) ... Preparing to unpack .../pcmanfm_1.3.2-1+rpt29_arm64.deb ... Unpacking pcmanfm (1.3.2-1+rpt29) over (1.3.2-1+rpt28) ... Preparing to unpack .../lxde-core_11+rpt2_all.deb ... Unpacking lxde-core (11+rpt2) over (11+rpt1) ... Preparing to unpack .../archives/lxde_11+rpt2_all.deb ... Unpacking lxde (11+rpt2) over (11+rpt1) ... dpkg: lxinput: dependency problems, but removing anyway as you requested: lxde depends on rasputin | lxinput; however:   Package rasputin is not installed.   Package lxinput is to be removed. (Reading database ... 135653 files and directories currently installed.) Removing lxinput (0.3.5-1+rpt26) ... Selecting previously unselected package rasputin. (Reading database ... 135577 files and directories currently installed.) Preparing to unpack .../00-rasputin_0.2_arm64.deb ... Unpacking rasputin (0.2) ... Preparing to unpack .../01-raspi-firmware_1%3a1.20241126-1_all.deb ... Unpacking raspi-firmware (1:1.20241126-1) over (1:1.20240924-2) ... Preparing to unpack .../02-tzdata_2024b-0+deb12u1_all.deb ... Unpacking tzdata (2024b-0+deb12u1) over (2024a-0+deb12u1) ... Preparing to unpack .../03-firefox_133.0-1+rpt7_arm64.deb ... Unpacking firefox (133.0-1+rpt7) over (132.0-1+rpt7) ... Preparing to unpack .../04-libgstreamer1.0-0_1.22.0-2+deb12u1_arm64.deb ... Unpacking libgstreamer1.0-0:arm64 (1.22.0-2+deb12u1) over (1.22.0-2) ... Preparing to unpack .../05-libgstreamer-plugins-base1.0-0_1.22.0-3+deb12u3_arm64.deb ... Unpacking libgstreamer-plugins-base1.0-0:arm64 (1.22.0-3+deb12u3) over (1.22.0-3+deb12u2+rpt1) ... Preparing to unpack .../06-gstreamer1.0-alsa_1.22.0-3+deb12u3_arm64.deb ... Unpacking gstreamer1.0-alsa:arm64 (1.22.0-3+deb12u3) over (1.22.0-3+deb12u2+rpt1) ... Preparing to unpack .../07-gstreamer1.0-plugins-base_1.22.0-3+deb12u3_arm64.deb ... Unpacking gstreamer1.0-plugins-base:arm64 (1.22.0-3+deb12u3) over (1.22.0-3+deb12u2+rpt1) ... Preparing to unpack .../08-gstreamer1.0-x_1.22.0-3+deb12u3_arm64.deb ... Unpacking gstreamer1.0-x:arm64 (1.22.0-3+deb12u3) over (1.22.0-3+deb12u2+rpt1) ... Preparing to unpack .../09-initramfs-tools_0.142+rpt2+deb12u1_all.deb ... Unpacking initramfs-tools (0.142+rpt2+deb12u1) over (0.142+rpt1+deb12u1) ... Preparing to unpack .../10-initramfs-tools-core_0.142+rpt2+deb12u1_all.deb ... Unpacking initramfs-tools-core (0.142+rpt2+deb12u1) over (0.142+rpt1+deb12u1) ... Preparing to unpack .../11-libpixman-1-0_0.42.2-1+rpt3_arm64.deb ... Unpacking libpixman-1-0:arm64 (0.42.2-1+rpt3) over (0.42.2-1+rpt1) ... Preparing to unpack .../12-libliftoff0_0.4.1-1~bpo12+rpt2_arm64.deb ... Unpacking libliftoff0:arm64 (0.4.1-1~bpo12+rpt2) over (0.4.1-1~bpo12+rpt1) ... Selecting previously unselected package libxcb-errors0:arm64. Preparing to unpack .../13-libxcb-errors0_1.0.1-2~bpo12+1+rpt1_arm64.deb ... Unpacking libxcb-errors0:arm64 (1.0.1-2~bpo12+1+rpt1) ... Selecting previously unselected package libwlroots-0.18:arm64. Preparing to unpack .../14-libwlroots-0.18_0.18.1-1+rpt6_arm64.deb ... Unpacking libwlroots-0.18:arm64 (0.18.1-1+rpt6) ... Preparing to unpack .../15-labwc_0.8.1-1+rpt1_arm64.deb ... Unpacking labwc (0.8.1-1+rpt1) over (0.7.4-1+rpt1) ... Preparing to unpack .../16-libcamera0.3_0.3.2+rpt20241119-1_arm64.deb ... Unpacking libcamera0.3:arm64 (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ... Preparing to unpack .../17-libcamera-ipa_0.3.2+rpt20241119-1_arm64.deb ... Unpacking libcamera-ipa:arm64 (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ... Preparing to unpack .../18-libcamera-tools_0.3.2+rpt20241119-1_arm64.deb ... Unpacking libcamera-tools (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ... Preparing to unpack .../19-libgstreamer-gl1.0-0_1.22.0-3+deb12u3_arm64.deb ... Unpacking libgstreamer-gl1.0-0:arm64 (1.22.0-3+deb12u3) over (1.22.0-3+deb12u2+rpt1) ... Preparing to unpack .../20-libwebkit2gtk-4.1-0_2.46.5-1~deb12u1_arm64.deb ... Unpacking libwebkit2gtk-4.1-0:arm64 (2.46.5-1~deb12u1) over (2.46.3-1~deb12u1) ... Preparing to unpack .../21-libjavascriptcoregtk-4.1-0_2.46.5-1~deb12u1_arm64.deb ... Unpacking libjavascriptcoregtk-4.1-0:arm64 (2.46.5-1~deb12u1) over (2.46.3-1~deb12u1) ... Preparing to unpack .../22-librbd1_16.2.15+ds-0+deb12u1_arm64.deb ... Unpacking librbd1 (16.2.15+ds-0+deb12u1) over (16.2.11+ds-2) ... Preparing to unpack .../23-librados2_16.2.15+ds-0+deb12u1_arm64.deb ... Unpacking librados2 (16.2.15+ds-0+deb12u1) over (16.2.11+ds-2) ... Selecting previously unselected package linux-headers-6.6.62+rpt-common-rpi. Preparing to unpack .../24-linux-headers-6.6.62+rpt-common-rpi_1%3a6.6.62-1+rpt1_all.deb ... Unpacking linux-headers-6.6.62+rpt-common-rpi (1:6.6.62-1+rpt1) ... Selecting previously unselected package linux-image-6.6.62+rpt-rpi-2712. Preparing to unpack .../25-linux-image-6.6.62+rpt-rpi-2712_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-image-6.6.62+rpt-rpi-2712 (1:6.6.62-1+rpt1) ... Selecting previously unselected package linux-kbuild-6.6.62+rpt. Preparing to unpack .../26-linux-kbuild-6.6.62+rpt_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-kbuild-6.6.62+rpt (1:6.6.62-1+rpt1) ... Selecting previously unselected package linux-headers-6.6.62+rpt-rpi-2712. Preparing to unpack .../27-linux-headers-6.6.62+rpt-rpi-2712_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-headers-6.6.62+rpt-rpi-2712 (1:6.6.62-1+rpt1) ... Selecting previously unselected package linux-image-6.6.62+rpt-rpi-v8. Preparing to unpack .../28-linux-image-6.6.62+rpt-rpi-v8_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-image-6.6.62+rpt-rpi-v8 (1:6.6.62-1+rpt1) ... Selecting previously unselected package linux-headers-6.6.62+rpt-rpi-v8. Preparing to unpack .../29-linux-headers-6.6.62+rpt-rpi-v8_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-headers-6.6.62+rpt-rpi-v8 (1:6.6.62-1+rpt1) ... Preparing to unpack .../30-linux-headers-rpi-2712_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-headers-rpi-2712 (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ... Preparing to unpack .../31-linux-headers-rpi-v8_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-headers-rpi-v8 (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ... Preparing to unpack .../32-linux-image-rpi-2712_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-image-rpi-2712 (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ... Preparing to unpack .../33-linux-image-rpi-v8_1%3a6.6.62-1+rpt1_arm64.deb ... Unpacking linux-image-rpi-v8 (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ... Preparing to unpack .../34-linux-libc-dev_1%3a6.6.62-1+rpt1_all.deb ... Unpacking linux-libc-dev (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ... Preparing to unpack .../35-lxplug-bluetooth_0.36_arm64.deb ... Unpacking lxplug-bluetooth (0.36) over (0.35) ... Preparing to unpack .../36-lxplug-ejecter_0.23_arm64.deb ... Unpacking lxplug-ejecter (0.23) over (0.22) ... Preparing to unpack .../37-lxplug-menu_0.5_arm64.deb ... Unpacking lxplug-menu (0.5) over (0.4) ... Preparing to unpack .../38-lxplug-netman_0.12_arm64.deb ... Unpacking lxplug-netman (0.12) over (0.11) ... Preparing to unpack .../39-raspi-config_20241210_all.deb ... Unpacking raspi-config (20241210) over (20241119) ... Removing obsolete conffile /etc/init.d/raspi-config ... Removing obsolete conffile /etc/default/cpu_governor ... Preparing to unpack .../40-lxplug-updater_0.20_arm64.deb ... Unpacking lxplug-updater (0.20) over (0.19) ... Preparing to unpack .../41-lxplug-volumepulse_0.27_arm64.deb ... Unpacking lxplug-volumepulse (0.27) over (0.26) ... Preparing to unpack .../42-piwiz_0.86_arm64.deb ... Unpacking piwiz (0.86) over (0.85) ... Preparing to unpack .../43-python3-libcamera_0.3.2+rpt20241119-1_arm64.deb ... Unpacking python3-libcamera:arm64 (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ... Preparing to unpack .../44-python3-picamera2_0.3.23-1_all.deb ... Unpacking python3-picamera2 (0.3.23-1) over (0.3.22-2) ... Preparing to unpack .../45-raindrop_0.12_arm64.deb ... Unpacking raindrop (0.12) over (0.10) ... Preparing to unpack .../46-raspberrypi-net-mods_1.4.3_all.deb ... Unpacking raspberrypi-net-mods (1.4.3) over (1.4.2) ... Preparing to unpack .../47-raspberrypi-sys-mods_20241202_arm64.deb ... Unpacking raspberrypi-sys-mods (20241202) over (20241111) ... Preparing to unpack .../48-raspberrypi-ui-mods_1.20241211_arm64.deb ... Unpacking raspberrypi-ui-mods (1.20241211) over (1.20241112) ... Preparing to unpack .../49-rc-gui_1.90_arm64.deb ... Unpacking rc-gui (1.90) over (1.89) ... Preparing to unpack .../50-rpi-eeprom_26.7-1_all.deb ... Unpacking rpi-eeprom (26.7-1) over (26.4-1) ... Preparing to unpack .../51-rpicam-apps_1.5.3-1_arm64.deb ... Unpacking rpicam-apps (1.5.3-1) over (1.5.2-2) ... Preparing to unpack .../52-squeekboard_1.21.0-1+rpt7_arm64.deb ... Unpacking squeekboard (1.21.0-1+rpt7) over (1.21.0-1+rpt5) ... Preparing to unpack .../53-wfplug-connect_0.10_arm64.deb ... Unpacking wfplug-connect (0.10) over (0.9) ... Setting up libliftoff0:arm64 (0.4.1-1~bpo12+rpt2) ... Setting up libpixman-1-0:arm64 (0.42.2-1+rpt3) ... Setting up rasputin (0.2) ... Setting up librados2 (16.2.15+ds-0+deb12u1) ... Setting up pcmanfm (1.3.2-1+rpt29) ... Setting up wfplug-connect (0.10) ... gtk-update-icon-cache: Cache file created successfully. Setting up firefox (133.0-1+rpt7) ... Setting up libxcb-errors0:arm64 (1.0.1-2~bpo12+1+rpt1) ... Setting up linux-libc-dev (1:6.6.62-1+rpt1) ... Setting up raindrop (0.12) ... Setting up tzdata (2024b-0+deb12u1) ... Current default time zone: 'America/Chicago' Local time is now:      Mon Jan  6 07:00:51 CST 2025. Universal Time is now:  Mon Jan  6 13:00:51 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libjavascriptcoregtk-4.1-0:arm64 (2.46.5-1~deb12u1) ... Setting up libwlroots-0.18:arm64 (0.18.1-1+rpt6) ... Setting up raspi-firmware (1:1.20241126-1) ... '/boot/vmlinuz-6.6.62+rpt-rpi-2712' -> '/boot/firmware/kernel_2712.img' '/boot/vmlinuz-6.6.62+rpt-rpi-v8' -> '/boot/firmware/kernel8.img' Setting up librbd1 (16.2.15+ds-0+deb12u1) ... Setting up linux-headers-6.6.62+rpt-common-rpi (1:6.6.62-1+rpt1) ... Setting up rpi-eeprom (26.7-1) ... Setting up lxpanel-data (0.10.1-2+rpt20) ... Setting up initramfs-tools-core (0.142+rpt2+deb12u1) ... Setting up linux-kbuild-6.6.62+rpt (1:6.6.62-1+rpt1) ... Setting up raspi-config (20241210) ... Setting up libgstreamer1.0-0:arm64 (1.22.0-2+deb12u1) ... Setcap worked! gst-ptp-helper is not suid! Setting up rc-gui (1.90) ... Setting up labwc (0.8.1-1+rpt1) ... Setting up initramfs-tools (0.142+rpt2+deb12u1) ... update-initramfs: deferring update (trigger activated) Setting up lxpanel (0.10.1-2+rpt20) ... Setting up libgstreamer-plugins-base1.0-0:arm64 (1.22.0-3+deb12u3) ... Setting up linux-image-6.6.62+rpt-rpi-2712 (1:6.6.62-1+rpt1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.6.62+rpt-rpi-2712 '/boot/initrd.img-6.6.62+rpt-rpi-2712' -> '/boot/firmware/initramfs_2712' /etc/kernel/postinst.d/z50-raspi-firmware: '/boot/vmlinuz-6.6.62+rpt-rpi-2712' -> '/boot/firmware/kernel_2712.img' Setting up raspberrypi-sys-mods (20241202) ... Setting up lxplug-menu (0.5) ... Setting up linux-image-rpi-2712 (1:6.6.62-1+rpt1) ... Setting up raspberrypi-ui-mods (1.20241211) ... Installing new version of config file /etc/xdg/labwc/rc.xml ... Setting up lxplug-bluetooth (0.36) ... Setting up libgstreamer-gl1.0-0:arm64 (1.22.0-3+deb12u3) ... Setting up gstreamer1.0-plugins-base:arm64 (1.22.0-3+deb12u3) ... Setting up piwiz (0.86) ... Setting up raspberrypi-net-mods (1.4.3) ... Installing new version of config file /etc/profile.d/wifi-check.sh ... Setting up squeekboard (1.21.0-1+rpt7) ... Setting up lxplug-updater (0.20) ... Setting up lxde-core (11+rpt2) ... Setting up lxplug-netman (0.12) ... Setting up libwebkit2gtk-4.1-0:arm64 (2.46.5-1~deb12u1) ... Setting up linux-image-6.6.62+rpt-rpi-v8 (1:6.6.62-1+rpt1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.6.62+rpt-rpi-v8 '/boot/initrd.img-6.6.62+rpt-rpi-v8' -> '/boot/firmware/initramfs8' /etc/kernel/postinst.d/z50-raspi-firmware: '/boot/vmlinuz-6.6.62+rpt-rpi-v8' -> '/boot/firmware/kernel8.img' Setting up gstreamer1.0-x:arm64 (1.22.0-3+deb12u3) ... Setting up gstreamer1.0-alsa:arm64 (1.22.0-3+deb12u3) ... Setting up lxplug-ejecter (0.23) ... Setting up lxplug-volumepulse (0.27) ... Setting up linux-headers-6.6.62+rpt-rpi-v8 (1:6.6.62-1+rpt1) ... Setting up linux-headers-6.6.62+rpt-rpi-2712 (1:6.6.62-1+rpt1) ... Setting up lxde (11+rpt2) ... Setting up linux-headers-rpi-2712 (1:6.6.62-1+rpt1) ... Setting up linux-image-rpi-v8 (1:6.6.62-1+rpt1) ... Setting up linux-headers-rpi-v8 (1:6.6.62-1+rpt1) ... Setting up libcamera-ipa:arm64 (0.3.2+rpt20241119-1) ... Setting up libcamera0.3:arm64 (0.3.2+rpt20241119-1) ... Setting up rpicam-apps (1.5.3-1) ... Setting up python3-libcamera:arm64 (0.3.2+rpt20241119-1) ... Setting up libcamera-tools (0.3.2+rpt20241119-1) ... Setting up python3-picamera2 (0.3.23-1) ... Processing triggers for shared-mime-info (2.2-1) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1.1) ... Processing triggers for libglib2.0-0:arm64 (2.74.6-2+deb12u4) ... Processing triggers for libc-bin (2.36-9+rpt2+deb12u9) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142+rpt2+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.6.62+rpt-rpi-v8 '/boot/initrd.img-6.6.62+rpt-rpi-v8' -> '/boot/firmware/initramfs8' update-initramfs: Generating /boot/initrd.img-6.6.62+rpt-rpi-2712 '/boot/initrd.img-6.6.62+rpt-rpi-2712' -> '/boot/firmware/initramfs_2712' ***@***.***:~$ sudo reboot

--- Post-upgrade, test unit with non-working BT, however out of range of sensor  -- ***@***.***:~$ sudo tail -f /var/log/genmopeka.log 2025-01-06 07:07:24,201 : Stop Scan Filtered 2025-01-06 07:07:24,202 : stopped scan 2025-01-06 07:07:24,203 : Processed Ads:0 2025-01-06 07:07:24,204 : Rejected Ads:0 2025-01-06 07:07:24,204 : Skipped Ads:0 2025-01-06 07:07:24,205 : Zero Length Ads:0 2025-01-06 07:07:24,205 : Ignored Ads:0 2025-01-06 07:07:24,208 : No sensor comms detected for BDAddress('D1:49:FB:DA:17:F9') 2025-01-06 07:07:24,209 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2025-01-06 07:07:24,229 : SendCommand Result: OK 2025-01-06 07:08:24,230 : starting scan 2025-01-06 07:08:24,232 : Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402 2025-01-06 07:08:39,236 : Stop Scan Filtered 2025-01-06 07:08:39,237 : stopped scan 2025-01-06 07:08:39,238 : Processed Ads:0 2025-01-06 07:08:39,238 : Rejected Ads:0 2025-01-06 07:08:39,239 : Skipped Ads:0 2025-01-06 07:08:39,239 : Zero Length Ads:0 2025-01-06 07:08:39,240 : Ignored Ads:0 2025-01-06 07:08:39,243 : No sensor comms detected for BDAddress('D1:49:FB:DA:17:F9') 2025-01-06 07:08:39,245 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2025-01-06 07:08:39,248 : SendCommand Result: OK 2025-01-06 07:09:39,250 : starting scan 2025-01-06 07:09:39,251 : Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402 2025-01-06 07:09:54,252 : Stop Scan Filtered 2025-01-06 07:09:54,253 : stopped scan 2025-01-06 07:09:54,254 : Processed Ads:0 2025-01-06 07:09:54,255 : Rejected Ads:0 2025-01-06 07:09:54,256 : Skipped Ads:0 2025-01-06 07:09:54,256 : Zero Length Ads:0 2025-01-06 07:09:54,257 : Ignored Ads:0 2025-01-06 07:09:54,260 : No sensor comms detected for BDAddress('D1:49:FB:DA:17:F9') 2025-01-06 07:09:54,260 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2025-01-06 07:09:54,262 : SendCommand Result: OK 2025-01-06 07:10:54,263 : starting scan 2025-01-06 07:10:54,264 : Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402 2025-01-06 07:11:09,265 : Stop Scan Filtered 2025-01-06 07:11:09,266 : stopped scan 2025-01-06 07:11:09,267 : Processed Ads:0 2025-01-06 07:11:09,268 : Rejected Ads:0 2025-01-06 07:11:09,268 : Skipped Ads:0 2025-01-06 07:11:09,269 : Zero Length Ads:0 2025-01-06 07:11:09,269 : Ignored Ads:0 2025-01-06 07:11:09,271 : No sensor comms detected for BDAddress('D1:49:FB:DA:17:F9') 2025-01-06 07:11:09,272 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2025-01-06 07:11:09,274 : SendCommand Result: OK ***@***.***:~$ sudo hostnamectl Static hostname: HeadendGenmon        Icon name: computer       Machine ID: 0236fadcd41341658f26075ffc12586d          Boot ID: fb509638e8b048ceac368f76942fb3e1 Operating System: Debian GNU/Linux 12 (bookworm)            Kernel: Linux 6.6.62+rpt-rpi-v8     Architecture: arm64 ***@***.***:~$ From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Saturday, January 4, 2025 at 3:24 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) @msteil4vse, I am out of things to suggest and try unless you can provide the information requested. I have requested but not received the following: 1. your complete logs 2. the kernel version you are using when the failure occurs. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[gm58]

Try sending yourself a Test Email from the Settings page

[jgyates]

If you reply in the github web interface you can attach files to the thread. It looks like you are only using email to respond to this thread. Try clicking the link at the bottom of the email from github. The link will take you to the web interface where you can attach files by dragging and dropping them in the thread text entry box.

I am guessing your email setup is sending and receiving to and from the same domain. The About page sends to a Gmail address so you should test using a domain not from your sender account to make the test a better real world test.

[msteil4vse]

That works fine, and I have the unis all setup with email accounts, and they routinely email me.  Only thing I can see, is when I originally set the email up in the units and I see it is setup to not use TLS or any encryption.  I seem to recall having some trouble making the encryption work and did this as a work around/test and never revisited the issue.  So with that In mind could the email be getting trapped in some sort of SPAM filter.  I will revisit the encryption email setup more this AM and see what was/is wrong. Mark From: gm58 ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Monday, January 6, 2025 at 8:19 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Try sending yourself a Test Email from the Settings page — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

Test email errors are shown on the web interface. Any errors from submissions are in /var/log/mymail.log

[msteil4vse]

Well, I get the email messages to several accounts and not all in the same domain, and I get test messages to me test gmail account.  Now errors in the mymail.log file, other hand expected ones when I was testing, but I did just get the SSL encryption working and I just re-sent the logs and registers again to see if that makes a difference . So please advise if you get them here in a few minutes. From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Monday, January 6, 2025 at 9:05 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) If you reply in the github web interface you can attach files to the thread. It looks like you are only using email to respond to this thread. Try clicking the link at the bottom of the email from github. The link will take you to the web interface where you can attach files by dragging and dropping them in the thread text entry box. I am guessing your email setup is sending and receiving to and from the same domain. The About page sends to a Gmail address so you should test using a domain not from your sender account to make the test a better real world test. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[msteil4vse]

Post upgrade-genmon_logs.tar.gz

[jgyates]

I received your logs via email also

[msteil4vse]

Excellent!  2 notes with respect to the log submission process, it would be my suspicion that there was something to do with the encryption or the lack thereof in submitting the logs.  A side issue it would be interesting to see if the logs previously submitted were somehow blocked by a junk mail filter. The second, it would be an improvement if the web interface provided a “Success/failure” message after submitting the information on the about page, like that of the “test email” function. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Monday, January 6, 2025 at 9:42 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) I received your logs via email also — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

The issue with your email is likely due to the errors in your /var/log/mymail.log file:

2025-01-06 09:16:50,234 : Error SMTP sendmail: {'[email protected]': (550, b'unknown recipient: route')} : mymail.py:716
2025-01-06 09:16:50,249 : Error in SendMailThread, sendEmailDirectMIME failed, retrying

You mail error log is filled with this error.

The 550 unknown recipient: route error is sent from the mail server you specify in the settings.

Your mail server will relate mail to other mail domains, if it can not then it will generate this error. Most mail domains do not accept non encrypted mail however you can setup a server to send mail on the same domain non encrypted, but forwarding to another domain will not work and will generate a 550 error.

Just searched. No logs in the mail filter.

Test email errors are shown on the web interface. Any errors from submissions are in /var/log/mymail.log. This is by design due to the way the information is generated by genmon. the web interface does not wait for the data to be sent so the request is queued. Adding a mechanism for this type if feedback would not be worth it from a maintenance point of view. This is the reason the test email was added. I have seen people have issues with email who have their own managed email server, but they always end up being misconfigured email servers or misconfigured settings for the locally run email server. Dedicating a free / throwaway email account from google, microsoft, apple or yahoo is an easy way to ensure compatibility.

More importantly, now that I have your kernel version I am able to test with the exact kernel version you have (6.6.62+rpt-rpi-v8). In October I was unable to duplicate and unable to use a stock distribution with the exact kernel version that you were using. In October I was using this:

On my system with bullseye (fully updated pi3b with 32 bit OS) the kernel version is 6.1.21-v8+
On my system with bookworm (fully updated pi 4 with 64 bit OS) the kernel version is 6.6.51+rpt-rpi-v8

Now, my pi 4 running the 64 bit OS is running 6.6.62+rpt-rpi-v8, the same version you are. Now I can duplicate the issue. I will look into this. For now I would recommend not updating your kernel if you want to use the genmopeka add on as this appears to be an issue with the python bleson module and the linux kernel. The genmon mopeka add on uses the bleson library to capture and parse the Bluetooth LE data sent from the sensor. In general these types of issues are resolved by either the library maintain fixes the issue (not likely in this case since the bleson library has not been updated in 5 years)or the party using the library fixes it or moves to an alternate solution. The later option will take some time if it occurs at all.

[msteil4vse]

Yes, that email address was one that is no longer in use and has subsequently been removed, however the other email addresses have been getting email, I supposed if you want I can go back to the unencrypted configuration and try sending you a new set of logs, but really maybe just salt this one away in memory if it happens to someone else in the future, as I doubt many send email unencrypted in this day and age, and the only reason mine was that way was really an oversight, not returning to the initial configuration once I got the email working to see what I had done wrong setting up the encryption.   I also know on some SMTP servers I manage they do out-of-hand reject non-encrypted messages. Thanks for the help and as you recemended I have a temporary moratorium on upgrading my production units, and now I have a lab setup in place I will be doing any updates in a test environment before applying anything to a production unit. Best Regards From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Monday, January 6, 2025 at 12:32 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) The issue with your email is likely due to the errors in your /var/log/mymail.log file: 2025-01-06 09:16:50,234 : Error SMTP sendmail: ***@***.***': (550, b'unknown recipient: route')} : mymail.py:716 2025-01-06 09:16:50,249 : Error in SendMailThread, sendEmailDirectMIME failed, retrying You mail error log is filled with this error. The 550 unknown recipient: route error is sent from the mail server you specify in the settings. Your mail server will relate mail to other mail domains, if it can not then it will generate this error. Most mail domains do not accept non encrypted mail however you can setup a server to send mail on the same domain non encrypted, but forwarding to another domain will not work and will generate a 550 error. Just searched. No logs in the mail filter. Test email errors are shown on the web interface. Any errors from submissions are in /var/log/mymail.log. This is by design due to the way the information is generated by genmon. the web interface does not wait for the data to be sent so the request is queued. Adding a mechanism for this type if feedback would not be worth it from a maintenance point of view. This is the reason the test email was added. I have seen people have issues with email who have their own managed email server, but they always end up being misconfigured email servers or misconfigured settings for the locally run email server. Dedicating a free / throwaway email account from google, microsoft, apple or yahoo is an easy way to ensure compatibility. More importantly, now that I have your kernel version I am able to test with the exact kernel version you have (6.6.62+rpt-rpi-v8). In October I was unable to duplicate and unable to use a stock distribution with the exact kernel version that you were using. In October I was using this: On my system with bullseye (fully updated pi3b with 32 bit OS) the kernel version is 6.1.21-v8+ On my system with bookworm (fully updated pi 4 with 64 bit OS) the kernel version is 6.6.51+rpt-rpi-v8 Now, my pi 4 running the 64 bit OS is running 6.6.62+rpt-rpi-v8, the same version you are. Now I can duplicate the issue. I will look into this. For now I would recommend not updating your kernel if you want to use the genmopeka add on as this appears to be an issue with the python bleson module and the linux kernel. The genmon mopeka add on uses the bleson library to capture and parse the Bluetooth LE data sent from the sensor. In general these types of issues are resolved by either the library maintain fixes the issue (not likely in this case since the bleson library has not been updated in 5 years)or the party using the library fixes it or moves to an alternate solution. The later option will take some time if it occurs at all. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[msteil4vse]

I found a new tidbit of information, of my 4 production deployments 3 of the 4 are running the 32 bit version of Raspbian GNU/Linux 11 (bullseye) the 4th installation has the 64 bit version and generally was the production  unit that was giving me the most grief when I attempted to do the full-upgrade.  All of the 32bit versions are on 6.6.33-v7+  and when I do a “apt list –upgradable” it would appear there is not an upgraded Kernel available in the list conversely the 64bit version wants to upgrade to the Linux 6.6.62-1+rpt1 arm64.  So my thought is anyone else using the genmopeka add on using the 32bit version will not see the issue until such time as they push a kernel update on the 32 bit version. From: Mark Steil ***@***.***> Date: Monday, January 6, 2025 at 1:09 PM To: jgyates/genmon ***@***.***>, jgyates/genmon ***@***.***> Cc: Mention ***@***.***>, Mark Steil ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Yes, that email address was one that is no longer in use and has subsequently been removed, however the other email addresses have been getting email, I supposed if you want I can go back to the unencrypted configuration and try sending you a new set of logs, but really maybe just salt this one away in memory if it happens to someone else in the future, as I doubt many send email unencrypted in this day and age, and the only reason mine was that way was really an oversight, not returning to the initial configuration once I got the email working to see what I had done wrong setting up the encryption. I also know on some SMTP servers I manage they do out-of-hand reject non-encrypted messages. Thanks for the help and as you recemended I have a temporary moratorium on upgrading my production units, and now I have a lab setup in place I will be doing any updates in a test environment before applying anything to a production unit. Best Regards From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Monday, January 6, 2025 at 12:32 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) The issue with your email is likely due to the errors in your /var/log/mymail.log file: 2025-01-06 09:16:50,234 : Error SMTP sendmail: ***@***.***': (550, b'unknown recipient: route')} : mymail.py:716 2025-01-06 09:16:50,249 : Error in SendMailThread, sendEmailDirectMIME failed, retrying You mail error log is filled with this error. The 550 unknown recipient: route error is sent from the mail server you specify in the settings. Your mail server will relate mail to other mail domains, if it can not then it will generate this error. Most mail domains do not accept non encrypted mail however you can setup a server to send mail on the same domain non encrypted, but forwarding to another domain will not work and will generate a 550 error. Just searched. No logs in the mail filter. Test email errors are shown on the web interface. Any errors from submissions are in /var/log/mymail.log. This is by design due to the way the information is generated by genmon. the web interface does not wait for the data to be sent so the request is queued. Adding a mechanism for this type if feedback would not be worth it from a maintenance point of view. This is the reason the test email was added. I have seen people have issues with email who have their own managed email server, but they always end up being misconfigured email servers or misconfigured settings for the locally run email server. Dedicating a free / throwaway email account from google, microsoft, apple or yahoo is an easy way to ensure compatibility. More importantly, now that I have your kernel version I am able to test with the exact kernel version you have (6.6.62+rpt-rpi-v8). In October I was unable to duplicate and unable to use a stock distribution with the exact kernel version that you were using. In October I was using this: On my system with bullseye (fully updated pi3b with 32 bit OS) the kernel version is 6.1.21-v8+ On my system with bookworm (fully updated pi 4 with 64 bit OS) the kernel version is 6.6.51+rpt-rpi-v8 Now, my pi 4 running the 64 bit OS is running 6.6.62+rpt-rpi-v8, the same version you are. Now I can duplicate the issue. I will look into this. For now I would recommend not updating your kernel if you want to use the genmopeka add on as this appears to be an issue with the python bleson module and the linux kernel. The genmon mopeka add on uses the bleson library to capture and parse the Bluetooth LE data sent from the sensor. In general these types of issues are resolved by either the library maintain fixes the issue (not likely in this case since the bleson library has not been updated in 5 years)or the party using the library fixes it or moves to an alternate solution. The later option will take some time if it occurs at all. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

I have a proposed fix that I would like you to test on both 32 and 64 bit systems. To test:

1. update genmon from the About page

2. from a console (or ssh) type:

   cd genmon
   ./genmonmaint.sh -r

3. restart genmon (in the same genmon folder)

   ./startgenmon.sh restart

Then you can look at the mopeka support to see if it works as expected. You should not get the error in the /var/log/genmopeka.log file.

Let me know how your testing goes.

[msteil4vse]

Well thank you for the attention I did not expect. I submitted the logs from my lab test unit and have some apprehension on going farther so I have paused for further input.  The lab unit is running the 64 bit code and post update I am see the following log entries.  Now the lab unit remember is out of range of the sensors, and I can locate it closer if you wish me to, be advised it is only 16 Degrees here today, and I am somewhat less motivated to stand out in the cold any more than necessary.  ☺ 2025-01-07 10:50:51,597 : Error in IsRunning: PID still exists but it's a zombie (pid=1647, name='python'): mysupport.py:571 2025-01-07 10:50:53,979 : Tank Address = d1:49:fb:da:17:f9 2025-01-07 10:50:53,981 : Min Reading Quality: 0 2025-01-07 10:50:53,986 : min: 38.1 , max: None 2025-01-07 10:50:53,987 : Tank Type: 500_GAL 2025-01-07 10:50:53,988 : Adding sensor:d1:49:fb:da:17:f9 2025-01-07 10:50:53,990 : Tank Volume Calculated: 501.14 2025-01-07 10:50:53,991 : <Horizontal tank, V=115764.285893 m^3, D=37.000000 m, L=83.000000 m, spherical heads, a=18.500000 m.> 2025-01-07 10:50:54,994 : starting scan 2025-01-07 10:51:15,472 : Error in MopekaBT:Start: [Errno 110] Connection timed out : mymopeka.py:398 2025-01-07 10:51:30,473 : MopekaBT:Stop: Scan already stopped 2025-01-07 10:51:30,474 : stopped scan 2025-01-07 10:51:30,474 : Processed Ads:0 2025-01-07 10:51:30,475 : Rejected Ads:0 2025-01-07 10:51:30,476 : Skipped Ads:0 2025-01-07 10:51:30,476 : Zero Length Ads:0 2025-01-07 10:51:30,477 : Ignored Ads:0 2025-01-07 10:51:30,479 : No sensor comms detected for BDAddress('D1:49:FB:DA:17:F9') 2025-01-07 10:51:30,480 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2025-01-07 10:51:30,500 : SendCommand Result: OK 2025-01-07 10:52:30,501 : starting scan From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 9:41 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) I have a proposed fix that I would like you to test on both 32 and 64 bit systems. To test: 1. update genmon from the About page 2. from a console (or ssh) type: cd genmon ./genmonmaint.sh -r 3. restart genmon (in the same genmon folder) ./startgenmon.sh restart Then you can look at the mopeka support to see if it works as expected. You should not get the error in the /var/log/genmopeka.log file. Let me know how your testing goes. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

No rush. Let me know once you have an opportunity to test. Thanks, Jason

[msteil4vse]

Look at the log text..   the update mad the “402” error go away in the new error: Error in MopekaBT:Start: [Errno 110] Connection timed out : mymopeka.py:398 Would indicate some failure to start a BT process?   Typically in the log of the lab unit there is no error when it’s on the x.51.x kernel, just a notation that it did not “hear” the sensor I will take the lab unit over near the sensor here directly and try it.. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 11:08 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) No rush. Let me know once you have an opportunity to test. Thanks, Jason — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[msteil4vse]

I have the test unit powered up and setting outside near the sensor for testing.  I submitted the logs again, and the 64 bit 6.6.62+rpt-rpi-v8 version I am testing is not working correctly. I will leave the test unit out until tonight in case you need something further. Mark From: Mark Steil ***@***.***> Date: Tuesday, January 7, 2025 at 11:18 AM To: jgyates/genmon ***@***.***>, jgyates/genmon ***@***.***> Cc: Mention ***@***.***>, Mark Steil ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Look at the log text.. the update mad the “402” error go away in the new error: Error in MopekaBT:Start: [Errno 110] Connection timed out : mymopeka.py:398 Would indicate some failure to start a BT process? Typically in the log of the lab unit there is no error when it’s on the x.51.x kernel, just a notation that it did not “hear” the sensor I will take the lab unit over near the sensor here directly and try it.. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 11:08 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) No rush. Let me know once you have an opportunity to test. Thanks, Jason — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

ok. Thanks for the testing data. The fix is one that someone submitted to the bleson repository as a fix for the structure packing issue with the changed kernel, but it has not been officially tested by the maintainer of the bleson package. I will continue to look at this, the long term fix may be to abandon bleson and move to another library for Bluetooth LE packet sniffing. That will require more time. I thought it may be worth trying this as a quick fix but it appears that this is not an option.

Let me know if it works on the 32 bit version. This would lit me know if it should keep this change or revert back to the older library.

[msteil4vse]

Ok will do, I need to build a 32bit installation as I don’t want to try it on a production unit, I will do that this PM and get back to you. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 11:48 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) ok. Thanks for the testing data. The fix is one that someone submitted to the bleson repository as a fix for the structure packing issue with the changed kernel, but it has not been officially tested by the maintainer of the bleson package. I will continue to look at this, the long term fix may be to abandon bleson and move to another library for Bluetooth LE packet sniffing. That will require more time. I thought it may be worth trying this as a quick fix but it appears that this is not an option. Let me know if it works on the 32 bit version. This would lit me know if it should keep this change or revert back to the older library. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[msteil4vse]

Ok, after several interruptions today I finally  tested the 32 bit version and it seems to be having the same issue as the 64 bit, I am not entirely certain what if any significance this is but the 32 bit installation shows kernel version  6.6.62+rpt-rpi-v8 and the 64bit shows kernel Linux 6.6.62+rpt-rpi-v7. Mark From: Mark Steil ***@***.***> Date: Tuesday, January 7, 2025 at 11:52 AM To: jgyates/genmon ***@***.***>, jgyates/genmon ***@***.***> Cc: Mention ***@***.***>, Mark Steil ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Ok will do, I need to build a 32bit installation as I don’t want to try it on a production unit, I will do that this PM and get back to you. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 11:48 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) ok. Thanks for the testing data. The fix is one that someone submitted to the bleson repository as a fix for the structure packing issue with the changed kernel, but it has not been officially tested by the maintainer of the bleson package. I will continue to look at this, the long term fix may be to abandon bleson and move to another library for Bluetooth LE packet sniffing. That will require more time. I thought it may be worth trying this as a quick fix but it appears that this is not an option. Let me know if it works on the 32 bit version. This would lit me know if it should keep this change or revert back to the older library. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

I have since tested with a 32bit (6.6.62+rpt-rpi-v7) Pi3b and 64 bit (6.6.62+rpt-rpi-v8) pi4B. Both show now errors when scanning. I had a mopeka sensor that I used for testing, but I have not been able to locate it so I have not actually tested with the mopeka yet, but no errors in my tests so far. I change the scan rate from th 60 min default to 1 min and no issues so far.

[jgyates]

I located my mopeka sensors. I am able to get readings from both with no errors with the update. Did you update the software and run ./genmonmaint.sh -r on both systems? Which error are you getting?

[msteil4vse]

Good AM, Sorry distractions abound on this end.  To answer your direct question yes I did run  ./genmonmaint.sh -r.  When I did the initial update the Pi was in my office out of range of any sensor, and I shut the Pi down and relocated it to where it could receive the sensor data, that location is a remote location about a ½ mile away, and that unit is currently running the 64 bit release.  The error continues to be Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402  if we can for the moment focust on the 64 bit verson that would be helpful as I have to run over and swap out the SD card to move from 64 bit to 32 bit. Here is the exact steps I took from the .bash_hstory log ./genmonmaint.sh -r ./startgenmon.sh restart sudo tail -f /var/log/genmopeka.log sudo hostnamectl sudo shutdown -h now Is there a chance some other item needs to be updated?  as this just occurred to me I dis and apt update and then apt list –upgradable and go back the list below.  I presuming the python updates might be relevant.  I have not updated them awaiting your feedback. ***@***.***:~$ apt list --upgradable Listing... Done gstreamer1.0-alsa/stable 1.22.0-3+rpt1+deb12u4 arm64 [upgradable from: 1.22.0-3+deb12u3] gstreamer1.0-plugins-base/stable 1.22.0-3+rpt1+deb12u4 arm64 [upgradable from: 1.22.0-3+deb12u3] gstreamer1.0-plugins-good/stable 1.22.0-5+rpt1+deb12u2 arm64 [upgradable from: 1.22.0-5+rpt1+deb12u1] gstreamer1.0-x/stable 1.22.0-3+rpt1+deb12u4 arm64 [upgradable from: 1.22.0-3+deb12u3] libgstreamer-gl1.0-0/stable 1.22.0-3+rpt1+deb12u4 arm64 [upgradable from: 1.22.0-3+deb12u3] libgstreamer-plugins-base1.0-0/stable 1.22.0-3+rpt1+deb12u4 arm64 [upgradable from: 1.22.0-3+deb12u3] python3-av/stable 12.3.0-2+rpt1 arm64 [upgradable from: 10.0.0-1+rpt4] python3-picamera2/stable,stable 0.3.24-1 all [upgradable from: 0.3.23-1] python3-pidng/stable 4.0.9+git20250106.30c8ba7-1 arm64 [upgradable from: 4.0.9-1+bookworm] From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Tuesday, January 7, 2025 at 6:23 PM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) I located my mopeka sensors. I am able to get readings from both with no errors with the update. Did you update the software and run ./genmonmaint.sh -r on both systems? Which error are you getting? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

So this is test is pre-system software update? I don't see where you updated genmon with this command: ./genmonmaint.sh -u or did you do that before? In would need to be done before in order to get rid of the 402 error.

When I run on a 64 bit system I got the 402, applied the bleson update and go now errors both with and without the sensor present.

I am not sure what you are referring to with another update. The ./genmonmaint.sh -r refreshes (updates) all of the python modules used by genmon to the latest or the version specified in the ./genmon/requirements.txt file.

[msteil4vse]

Yes I did both ./genmonmaint.sh -u and ./genmonmaint.sh -r  yesterday and I just did them again today and from the output of genmonmaint.sh -r  every item shows “Requirement already satisfied”. I spent most of my time on the 32 bit test environment yesterday and when I revisited the 64 bit version today when I noticed there were python updated needing to be applied.  See previous email for the list.  After completing a dist-upgrade again this AM and upon completion I rebooted.. Success!!   No more errors and I am getting readings on the 64 bit version.  I will go over and swap out the SD cards and test the 32 bit version this PM. From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Wednesday, January 8, 2025 at 10:31 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) So this is test is pre-system software update? I don't see where you updated genmon with this command: ./genmonmaint.sh -u or did you do that before? In would need to be done before in order to get rid of the 402 error. When I run on a 64 bit system I got the 402, applied the bleson update and go now errors both with and without the sensor present. I am not sure what you are referring to with another update. The ./genmonmaint.sh -r refreshes (updates) all of the python modules used by genmon to the latest or the version specified in the ./genmon/requirements.txt file. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgyates]

Great. I tested the update on Debian 12 32 and 64 bit and Debian 11 32 bit all are working with no errrors for me.

[msteil4vse]

Just getting back  to you for some reason there was something wrong with my installation on the 32 bit SD card and the Pi would not boot, anyhow short version is I bult out a fresh install from the ground up of the 32 bit version and it seems to be working just fine as well. Thanks for all the help. Mark From: jgyates ***@***.***> Reply-To: jgyates/genmon ***@***.***> Date: Wednesday, January 8, 2025 at 11:10 AM To: jgyates/genmon ***@***.***> Cc: Mark Steil ***@***.***>, Mention ***@***.***> Subject: Re: [jgyates/genmon] genmopeka.log, "Error in MopekaBT:Start: [Errno 22] Invalid argument : mymopeka.py:402" (Discussion #1230) Great. I tested the update on Debian 12 32 and 64 bit and Debian 11 32 bit all are working with no errrors for me. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>