I’ve merged in some significant updates to the NanoBLESensors project. Hop over to GitHub to check them out.

I’ve created a new simple Arduino sketch using a variety of Temperature/Humidity sensors. (https://github.com/tjpetz/EnvironmentSensorTests. Of note in this simple example is using the DHT11 sensor with a Nano 33 BLE Sense board.

I recently upgraded a very old Netgear ReadyNAS device to a new Synology DS-420+ at a remote location.

The main use of the old ReadyNAS was an a rsync target for backing up my main Synology rack station. I have about 2.5TB of rsync’d files. I wanted to reuse the existing rsync files to avoid the several months necessary to build a new backup.

I thought I could just repoint the existing Hyper Backup jobs on the Synology rack station. This did not work as I couldn’t reset the name of the share where the files were to be backed up to. I also tried building new jobs using the targets of the copied files but this would error out because HyperBackup would report that files already existed in the target directories.

The Arduino Nano 33 BLE (Sense) and the Nano 33 IoT expose SWD pads on the bottom of the board. These pads expose the SWD interface that enable debugging when used with an SWD compatible debugger such as the Segger J-Link Mini EDU.

The pads on the bottom of the Nanos are very small (and as we’ll see later quite fragile). Normally you would use some form of test fixture and pogo pins to connect to the pads. I don’t have that. Some approaches show soldering dupont wires to the pads and then connecting to the J-Link via and adapter.

After a good bit of investigation and thinking… the problem with bind9 has nothing to do with bind9. The problem was a mismatch between UIDs between the Synology NAS server and the bind account on the pi. As I was using sec=sys for authentication all the authentication is based on UIDs. On the pi bind has a UID of 109. There was no account on my Synology NAS with a UIDs of 109. Hence the access was denied by the NFS server.