Hi @Michael_Harris, @Frank_M, @Henrik_Lampe,
my partner @Klaus_Engel can reproduce the issue 
This means we will start looking for it and hopefully provide an update soon.
Best DrCWO
1 Like
Thanks Doctor
I will not do any investigation this evening, and your auto update feature is looking an ever better investment in time and energy
1 Like
Hi @Michael_Harris, @Frank_M, @Henrik_Lampe,
I pushed an update to v3.1.1 that reverts the “improvements” I made for rooNuimo. Seems I inserted a race condition 
Please go to the web configuration page of your rooExtend Box http://[of of rooExtend] and click the button “Look for Software updates” to install it.
Please report if this fixed the Nuimo issue.
Best DrCWO
1 Like
@DrCWO
And now, after the upgrade to 3.1.1, the Nuimo is connected again and seems to wrok perfectly.
Thank you for the fast solution.
Kind regards, Frank.
1 Like
Thank’s for the quick reply 
Great, so I was right with my analysis of the race condition. I will give the “improvements” a next try when I am back from travelling next week.
Best DrCWO
Thank you. My RooExtend still shows V3.1.0 and is disconnected. Is it going to autoupdate tonight or do I need to do this manually? Bo
Both is possible. See my post four entries above 
This update solved the bluetooth connections issue with my Nuimo. Thanks.
BTW: is there an option to disable autoupdate?
1 Like
Done. It took me a while to figure out how to access my box but now it’s updated and connected again. Thank you!
1 Like
It is not.
As I am a one man show I only can support the current release. This is why I hope with the OTA update sooner or later everybody will have the current release.
I apologize about the issue but believe me I tested a lot before releasing to give you a good experience with your rooExtend.
This time I failed as I did not see this issue in my setup. S h i t happens
Best DrCWO
2 Likes
Hi DrCWO,
No problem. This can happen. The error was resolved very fast. So thank you for the solution.
Kind regards, Frank.
1 Like
Price reduction for FLIRC Case LIDs
I still have a lot of those nice FLRIC lids in stock. Recently I had to increase the price but it now seems to be too high for getting accepted. From now on the old price is back!
No more gain for me any more but I want to get rid of them…
@DrCWO when you say the OTA updates happen at night… who’s night is this…i.e. what time/window exactly?
Time zone is local
1 Like
It happens between 2AM and 4AM of your LOCAL timezone.
rooExtend knows about the timezone you are in 
Best DrCWO
1 Like
OK that’s OK then I guess as long as its local time zone
Thanks @DrCWO both of my RooExtend’s updated overnight and seem stable now .
Nice turn around time 
1 Like
Hi-
My Pi Zero W 2 just updated overnight to 3.1.1, and for what it’s worth it didn’t reboot properly, it shut down and then didn’t come back up. Not a huge deal - but thought I’d mention. It shut down at 3:17am local, and I manually powered off and on again at 7:34 local.
System log quote from relevant time period:
Summary
-- Journal begins at Wed 2023-02-15 03:17:03 EST, ends at Wed 2023-02-15 07:35:04 EST. -- Feb 15 03:17:26 rooExtend-Acrylic-PiZero systemd[1]: Started rooExtend service. Feb 15 03:17:30 rooExtend-Acrylic-PiZero rooExtend[871]: Verifying archive integrity... Feb 15 03:17:31 rooExtend-Acrylic-PiZero rooExtend[908]: [160B blob data] Feb 15 03:17:31 rooExtend-Acrylic-PiZero rooExtend[871]: MD5 checksums are OK. All good. Feb 15 03:17:31 rooExtend-Acrylic-PiZero rooExtend[871]: Uncompressing rooExtend Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[970]: [160B blob data] Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[1015]: -------------------------------------------------- Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[1015]: rooExtend 3.1.1 started... Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[1015]: Config Path: /config.json Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[1015]: Hostname: rooExtend-Acrylic-PiZero Feb 15 03:17:35 rooExtend-Acrylic-PiZero rooExtend[1015]: Ethernet: not connected Feb 15 03:17:36 rooExtend-Acrylic-PiZero rooExtend[1015]: Got language: US Feb 15 03:17:36 rooExtend-Acrylic-PiZero rooExtend[1015]: Got timezone: America/New_York Feb 15 03:17:36 rooExtend-Acrylic-PiZero rooExtend[1015]: Set timezone: Success Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Restarted: false Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Has Bluetooth: true hci0 UART Feb 15 07:34:37 rooExtend-Acrylic-PiZero rfkill[1081]: unblock set for id 1 Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: TV name: Unk-Composite di Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Found: Raspberry Pi Zero 2 W Rev 1.0 Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Production: true Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Interface: wlan0 Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Has WiFi: true Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Is NanoPi: false Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: Has Linux 64: true Feb 15 07:34:37 rooExtend-Acrylic-PiZero rooExtend[1015]: --------------------------------------------------
And complete update log from overnight:
Summary
` – Journal begins at Wed 2023-02-15 03:17:03 EST, ends at Wed 2023-02-15 07:37:53 EST. –
Feb 15 03:17:08 rooExtend-Acrylic-PiZero systemd[1]: Started rooExtendUpdater service.
Feb 15 03:17:08 rooExtend-Acrylic-PiZero rooExtendUpdater[373]: Verifying archive integrity…
Feb 15 03:17:08 rooExtend-Acrylic-PiZero rooExtendUpdater[419]: [62B blob data]
Feb 15 03:17:08 rooExtend-Acrylic-PiZero rooExtendUpdater[373]: MD5 checksums are OK. All good.
Feb 15 03:17:08 rooExtend-Acrylic-PiZero rooExtendUpdater[373]: Uncompressing rooExtendUpdater
Feb 15 03:17:09 rooExtend-Acrylic-PiZero rooExtendUpdater[459]: [62B blob data]
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: {
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “isR2S”: false,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “ledPortPath”: “/sys/class/leds/led0/brightness”,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “revisionCode”: 9445664,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “hardware”: “BCM2835”,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “revision”: “902120”,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “serial”: “0000000018f8528b”,
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: “model”: “Raspberry Pi Zero 2 W Rev 1.0”
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: }
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: --------------------------------------------------
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: rooExtendUpdater: v3.1.1
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: production: true
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: testRepository: false
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: Apt local file: /etc/apt/sources.list.d/rooextend.list
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: Apt source: deb https://rooextend.com/rooextend-prod-PI agnostic main
Feb 15 03:17:15 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: --------------------------------------------------
Feb 15 03:17:17 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** Aquire timezone and local time…
Feb 15 03:17:19 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** Cannot get timezone: undefined
Feb 15 07:34:50 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** Aquire timezone and local time…
Feb 15 07:34:50 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** Timezone: America/New_York
Feb 15 07:34:50 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** Date: 2023/02/15 07:34:50
Feb 15 07:34:50 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: I got: {“timezone”:“America/New_York”,“dateString”:“2023/02/15 07:34:50”}
Feb 15 07:34:50 rooExtend-Acrylic-PiZero rooExtendUpdater[476]: ***** First update: 2023/02/16 03:54:00
`
Not sure if useful, I’m not looking for a resolution, but thought might be useful to you if others experience a “not quite complete auto-update”.
Thanks as always for great software!
Strange, no idea what went wrong 
Did it work after reboot?
Works just fine after reboot - again, not complaining so much as documenting in case others see the same thing or it happens to me again. Small issue! And many thanks again!
1 Like