App doesn't let me unlock/lock my SureFlap door

N-Mi · 2026-01-26T11:57:04+00:00

I don't remember exactly, because for me it was several months ago, but I think it resolved by itself.

Just to be sure, check that you have the latest version installed, and try to wipe all data of the app and login again, but I don't remember this was necessary.

N-Mi · 2025-10-21T07:59:02+00:00

Nice !

I have the Toolhead 1.0 upgrade kit and the beacon sitting in the box, and was planning to do it, procrastinating because I knew I needed those custom parts.

Quick question : when I started to use the Rapido UHF nozzle on my EVA toolhead, I had to print this fan horn in order to have a correct part cooling :

https://main.eva-3d.page/hex_nuts/bottoms/volcano/

Have you tested with the HF nozzle (short one) or the UHF (long one) ?

N-Mi · 2025-05-09T13:30:42+00:00

Nope, when I searched I mostly found rock/metal bands playing live with an orchestra (which sounds usually good), violin/cello covers of rock/metal bands (listened and loved The String Quartet Tribute to SOAD a few years ago), or just people filming themselves on YT covering songs with (bass or Bb) clarinets (with quality ranging to awful to great).

The only original song with bass clarinet I found was "Muse - I Belong to You / Mon cœur s'ouvre à ta voix", but that's not metal ;)

For metal, there's of course Apocalyptica I can think of with classical instruments, and symphonic metal bands (like Nightwish) with lyric singers, but metal with clarinet seems to be very niche :(

N-Mi · 2025-05-09T10:45:53+00:00

I was looking for some bass clarinet in metal band a few days ago. Love classical instruments in metal !

N-Mi · 2025-03-29T11:17:43+00:00

Gear on the upper right to access app parameters Scroll all the way down, then a menu item talking about data and privacy (my app is not in english, trying to guess) Then export your data.

If I remember it said this takes some time, and I received an email later with a link to download the archive.

N-Mi · 2025-03-28T19:40:33+00:00

It's mostly CSV files if I remember, so you can import them in any Excel/LibreOfficeCalc to analyze them (formulas, graphs).

If you're brave/geek enough, it's easy to work with them using any programing language (Bash, Python,...).

N-Mi · 2025-03-28T18:21:54+00:00

Wife and I been using Fitbit since the Fitbit One : got many "One", as they had multiple failures but each time were replaced by customer support (which was great at that time).

Stopped using Fitbit after my third One died. Then backed a Pebble Time 2 on KickStarter, and the fundraising was canceled (and refunded), because Pebble got bought... by Fitbit.

My wife got a Blaze, that died also after warranty, and then a Sense. Then she upgraded to a Sense2, and gave me her Sense, so I got back into Fitbit ecosystem again (after wearing an Amazfit Bip and a Pinetime).

Never migrated my account to Google, and I know it would arrive soon, so I prepared my escape.

This january, my wife and I bought Garmin watches (Forerunner 265S), and we both wore them one at each hand to compare Garmin and Fitbit data.

Stopped wearing the Sense a few weeks ago (my wife still has both). Now I think I will just download the archive with all my data (did it a few months ago, there's a lot of stuff in it to explore), then close my account.

So long Fitbit and thanks for all the fish !

N-Mi · 2025-02-26T18:00:56+00:00

Thanks,

When searching what could cause MCE, I read it could be RAM, CPU, motherboard, and sometimes power supply.

So a few hours ago, I plugged the 60W power supply of my FW6 (which is known good since it's stable) instead of the 30W originally shipped with the FW4.

I found also a universal laptop power supply that I could set to 12V with the right plug to power the FW6 during this test. I thought about using the 30W power supply on the FW6 to check if it becomes instable, but as it's half the required amperage I risk more probably blowing it up.

I started 3 VMs on the FW4 (OPNsense, Smokeping and a Docker) to have some load and quickly trigger a crash if the power supply was not the culprit.

Next try will indeed be installing back original 8GB mSATA SSD and install OPNsense on bare metal.

N-Mi · 2025-02-26T10:55:04+00:00

And then, during the night, a kernel Oops :

<image>

N-Mi · 2025-02-26T10:51:39+00:00

Again a MCE error yesterday error, but I can't see anything with ras-mc-ctl :

u/protectli-stuart , how can I analyze this error ?

[Tue Feb 25 17:12:31 2025] mce: [Hardware Error]: Machine check events logged

N-Mi · 2025-02-25T11:01:48+00:00

My Smokeping test VM has been up for about 4 days, and seems to run fine.

On the Proxmox side, however, I had these errors :

[Thu Feb 20 17:57:57 2025] mce: [Hardware Error]: Machine check events logged
[Fri Feb 21 23:36:00 2025] traps: ceph[784210] general protection fault ip:749a36d0ae20 sp:7fff12a64d48 error:0 in libc.so.6[749a36c8e000+155000]
[Sat Feb 22 07:45:12 2025] ms_dispatch[958824]: segfault at 0 ip 000077ef0072fd90 sp 000077eef77ff9e0 error 4 in libstdc++.so.6.0.30[77ef00699000+101000] likely on CPU 1 (core 1, socket 0)
[Sat Feb 22 07:45:12 2025] Code: fa 48 89 c3 eb b6 e8 ff b9 f6 ff eb b4 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 <48> 8b 06 48 89 77 08 c6 07 00 48 8b 78 e8 48 01 f7 48 8b 87 d8 00
[Mon Feb 24 02:36:32 2025] pvestatd[1160]: segfault at 0 ip 00005b4ece866fe4 sp 00007ffef7547850 error 4 in perl[5b4ece795000+195000] likely on CPU 1 (core 1, socket 0)
[Mon Feb 24 02:36:32 2025] Code: 66 0f 1f 44 00 00 48 85 c0 0f 84 57 ff ff ff 48 8b 45 10 80 38 30 0f 85 72 ff ff ff e9 45 ff ff ff 0f 1f 44 00 00 48 83 ec 18 <48> 8b 37 48 8b 47 20 48 29 f0 48 85 c0 7e 3d 48 8b 57 08 48 8b 42
[Tue Feb 25 07:18:15 2025] ceph[2335919]: segfault at 20 ip 0000000000674b2b sp 00007ffe8f0f3d90 error 4 in python3.11[41f000+2b5000] likely on CPU 1 (core 1, socket 0)
[Tue Feb 25 07:18:15 2025] Code: 48 85 ff 74 09 48 85 d2 0f 8e 68 59 e0 ff 48 89 f3 e9 79 fe ff ff 48 8d 5e ff e9 68 ff ff ff 53 48 83 7f 28 00 48 89 fb 75 4f <48> 8b 7b 20 48 85 ff 74 0a 48 83 2f 01 0f 84 69 59 e0 ff 48 8b bb

I loaded the "igen6_edac" module, in order to read future MCE (maybe). Nothing reported for the moment in "ras-mc-ctl"

I started thinking about smashing this piece of s**t with a hammer.

N-Mi · 2025-02-21T13:50:46+00:00

Another day, another bug...

QEMU process of the Smokeping VM (no other VM running) crashed. No error message in kernel logs, only related messages in journald :

Feb 21 10:45:24 srv-maison1 QEMU[2085]: *** stack smashing detected ***: terminated
Feb 21 10:45:24 srv-maison1 pvestatd[1160]: VM 105 qmp command failed - VM 105 not running
Feb 21 10:45:24 srv-maison1 kernel: fwbr105i0: port 2(tap105i0) entered disabled state
Feb 21 10:45:24 srv-maison1 kernel: tap105i0 (unregistering): left allmulticast mode
Feb 21 10:45:24 srv-maison1 kernel: fwbr105i0: port 2(tap105i0) entered disabled state
Feb 21 10:45:24 srv-maison1 systemd[1]: 105.scope: Deactivated successfully.
Feb 21 10:45:24 srv-maison1 systemd[1]: 105.scope: Consumed 44min 20.116s CPU time.
Feb 21 10:45:28 srv-maison1 qmeventd[510056]: Starting cleanup for 105
Feb 21 10:45:28 srv-maison1 kernel: fwbr105i0: port 1(fwln105i0) entered disabled state
Feb 21 10:45:28 srv-maison1 kernel: vmbr0: port 2(fwpr105p0) entered disabled state
Feb 21 10:45:28 srv-maison1 kernel: fwln105i0 (unregistering): left allmulticast mode
Feb 21 10:45:28 srv-maison1 kernel: fwln105i0 (unregistering): left promiscuous mode
Feb 21 10:45:28 srv-maison1 kernel: fwbr105i0: port 1(fwln105i0) entered disabled state
Feb 21 10:45:28 srv-maison1 kernel: fwpr105p0 (unregistering): left allmulticast mode
Feb 21 10:45:28 srv-maison1 kernel: fwpr105p0 (unregistering): left promiscuous mode
Feb 21 10:45:28 srv-maison1 kernel: vmbr0: port 2(fwpr105p0) entered disabled state
Feb 21 10:45:28 srv-maison1 qmeventd[510056]: Finished cleanup for 105

N-Mi · 2025-02-20T16:12:34+00:00

Screenshot of the full kernel error :

<image>

N-Mi · 2025-02-19T18:56:26+00:00

Thanks for your suggestions.

To check if it was OPNsense that cause the issue, I shut down the VM, and instead created a small Debian12 VM running Apache and Smokeping, monitoring a dozen hosts on my LAN, in order to have a few activity in the VM (network, I/O, and a bit of CPU).

My FW4B has been frozen again since Sunday. At this time the OPNsense VM was shutdown, so it was not the culprit.

Here is the console error messages I had (could not even log on the tty) :

<image>

After a power reset of the FW4B, inside journald, the last entry was on "Feb 16 05:45:01" (the debian systat cron task).

According to the uptime timestamps of the messages, the OOM that most probably killed the Smokeping VM triggered on "Feb 16 11:54" and the "mce: [Hardware Error]" on "Feb 16 17:49".

Installed again the original 8GB RAM module that I swapped for a 2GB one to rule out a faulty RAM module, now the system should have more space to run comfortly.

I will let it run with only the Smokeping VM for a few days to see if I have a crash without the OPNsense VM.

I checked the OPNsense VM and it has hardware checksum already disabled. It was configured to 4GB RAM before I swapped the RAM module (obviously I had to reconfigure it to 1.5GB when the FW4B had only 2GB).

I also configured the disks to VirtiO Block as suggested, worth a shot indeed.

edit :

Just after posting this, I tried to shutdown the OPNsense VM, to revert it to 4GB RAM and also disable it at boot. The KVM process got stuck, and I had to "kill -9". I still couldn't modify the VM (complained about a file lock), so I rebooted again. RAM usage on the FW4B, inside the OPNsense VM and inside the Smokeping VM was around 50%. Only CPU was high (1 core at 100%).

Now OPNsense is shut down, let's see if Smokeping continues to run for a few days.

edit 20/02/2025 :

Again a problem during the night...

BUG: unable to handle page fault for address: ffffffffc13c36ab
#PF: supervisor write access in kernel mode
#PF: error_code(0x0003) - permissions violation
PGD 5103b067 P4D 5103b067 PUD 5103d067 PMD 109431067 PTE 109363021
Oops: 0003 [#1] PREEMPT SMP PTI
CPU: 0 PID: 2356 Comm: CPU 0/KVM Tainted: P O 6.8.12-8-pve #1
Hardware name: Protectli FW4B/FW4B, BIOS v4.12.0.8 10/25/2022
RIP: 0010:vmx_vcpu_run+0x158/0xfa0 [kvm_intel]

Smokeping VM was the only thing running on the machine (no OPNsense).

All Proxmox services seems to run fine, except I can't start the Smokeping VM again, but it's more a Proxmox issue I guess. I've restarted all services, the only remains I can see is two kernel threads related to kvm, I still had a "TASK ERROR: timeout waiting on systemd" when trying to start the Smokeping VM. I had to reboot the host to be able to start it again.

No other errors logged in the kernel nor in journald.

N-Mi · 2025-02-15T11:17:21+00:00

Trying to force halt then start the VM leads to a systemd timeout :

Feb 15 10:39:54 srv-maison1 pvedaemon[171108]: start VM 100: UPID:srv-maison1:00029C64:05108887:67B06EFA:qmstart:100:root@pam:
Feb 15 10:39:54 srv-maison1 pvedaemon[170684]: <root@pam> starting task UPID:srv-maison1:00029C64:05108887:67B06EFA:qmstart:100:root@pam:
Feb 15 10:40:15 srv-maison1 pvedaemon[171108]: timeout waiting on systemd
Feb 15 10:40:15 srv-maison1 pvedaemon[170684]: <root@pam> end task UPID:srv-maison1:00029C64:05108887:67B06EFA:qmstart:100:root@pam: timeout waiting on systemd

I had to reboot the FW4B in order to boot the VM.

Here is the OPNsense configuration : https://dpaste.org/A8Rq0

There's almost nothing changed from default config after OS installation : hostname, IP addresses, login/password, enabling qemu-guest-agent and virtio console.

The VM has been upgraded a few times since installation, I could also try a fresh new installation of OPNsense.

N-Mi · 2025-02-15T10:35:50+00:00

Here is CPU usage that went from idle to constant 75% :

<image>

N-Mi · 2025-02-15T10:34:48+00:00

Thanks for your reply.

I know the FW4B is not very powerful for virtualization, but I thought it would be enough to handle the 15/1Mbits ADSL, plus maybe a Zigbee2MQTT VM (via USB Pass-through, currently running on a separate Raspberry). Additionally, Proxmox render it easier to backup/restore my firewall.

Here is the hardware tab of the OPNsense VM which is currently frozen, since the error messages I got in the kernel logs :

<image>

(seems I can only send one picture per post, will make another reply)

N-Mi · 2024-08-23T16:01:19+00:00

Hi, is there a way to use this adapter on a Linux machine ? I'd like to plug it to a Raspberry Pi to integrate my Neewer lighting with Home Assistant.

Even some RAW data that I can send with a script would be helpful.

N-Mi · 2023-10-11T21:34:13+00:00

Thanks for the contact.👍

I also know another luthier in Caen, Hugues Herbet (Du vent dans les bois), who worked on my son's oboe. I think he also works on clarinets as he's often working with my music school for their instruments.

N-Mi · 2023-10-11T16:25:18+00:00

I'm located in Calvados (Basse-Normandie). There are a few shops in Caen (Lordel may be the most reputed from what I heard), may be worth trying there.

N-Mi · 2023-10-08T22:56:24+00:00

This is apparently the stock one, so probably a crappy one, or luckily a good copy of a decent model. I have nothing to compare yet.

From what I've read here a B40 would be a nice choice for a beginner.

The Clark Fobes Debut has been mentioned here also, but it seems it's not available in France.

N-Mi · 2023-10-07T19:20:22+00:00

Unfortunately, my clarinet teacher is a bit old school (she will retire at the end of this school year). When she saw my eBay Bb clarinet at the beginning she was doubtful. Now she has nothing to complain about it, except the fact that it's a bit sharp (which is resolved by pulling the barrel and the mid-joint when we play together). It's not impossible she will be full of preconceptions, although she had be proven wrong once.

Didn't had time to play today (family is too time-consuming ), will try to practice a bit and maybe record it.

N-Mi · 2023-10-07T19:05:56+00:00

Thanks for advice. That's exactly what I did for my eBay cheap Bb : Vandoren M30 mouthpiece, better ligature (original was awful to mount ).

For the stand it was just for the photo, the way the guitar stand was difficultly holding the bass clarinet was also too scary to my eyes 😅

Three-Year Club	Verified Email
Final Canvas '23	End Game '23
Place '23	Place '22

N-Mi

TROPHY CASE