I separate the name from the ID, so the IDs are relative to the specific device only, and the names represent the device and location.

I’ve set the IDs for all my sensors to use a code. The letters identify the type of sensor, and the numbers are sequential when I got them. I also have a label maker and labeled all the devices with their codes.

Example:

AA##

So my first temperature sensor is

TS01

Then the name of the sensor is a little more elaborate, where it includes the type of the sensor, the code, and the location.

{Type} {ID} - {Location}

So my bedroom motion sensor is:

Motion MS02 - Bedroom

Then if I have to rearrange anything, I don’t update the device ID, just the name and how it’s used.

I recently moved and had to rearrange some of the devices. It wasn’t as bad as it could have been as I tried sticking the sensors in the proper rooms (ie all the old bedroom devices stayed in the bedroom). But there were some cases where I did have to rename them & update the integrations.

An unfortunate series of events

Soldier was firing blanks towards the officer, and the officer probably panicked and fired back; thinking they were being shot at.

For those unaware: blank rounds / blanks is a special type of ammunition you can use in a real firearm that doesn’t have a projectile (ie the bullet). Military and police use blanks to simulate real ammo being fired out of the gun so they get used to the bang, mechanics of the firearm, having to reload, fixing jams, etc.

Other than the actual bullet, there are only a few noticeable differences between real ammo and blanks:

• The firearm has to be modified to be able to use the blanks. Usually they put a bright yellow plug at the end of the barrel. It helps the firearm function properly, and will catch a bullet in case live ammunition is used
• The bang is a bit louder.

From the officers perspective: they got calls saying there was a shooter. They arrive on scene, and someone starts shooting at them. I’d shit my pants too and shoot back

I fully flipped over every device in my house off windows about a week or two ago, and so far so good!

I’ve been daily driving linux on my personal laptop since 2009 (16 years now!?) for school / work / personal work-esque stuff, and my work laptop is now OSX. A few weeks ago I flipped my gaming machine from windows to popOS and been quite pleasantly surprised at how well gaming on Linux is these days. So much so, I convinced my wife to let me flip her gaming machine to Linux as well.

The only hiccup I’ve recently had was having to deal with windows-only, non-steam software. Ie. insta360. Luckily, there are compatibility layers / emulators I can use to be able to run it. It’s slow, but good enough.

At this point, there’s no good reason for me to go back to Windows or anything Microsoft. It’s even become a red flag when I hear a business is using Microsoft’s products. I want to hope Microsoft gets a wake up call at some point soon and turns the ship around, but I think they’ve got too many big-company deals to have to worry about their consumer products being shite.

Linkwarden user here. Can confirm - it’s a great tool to dump links for later. I’ve setup an iOS shortcut that lets me share links directly to linkwarden. Super handy

Looking through the docs n’ stuff, this is what I found:

• Updating Guide. Just basic steps, similar to what I explained above; but with commands to run.
• Backing up and restoring
• 2.0.0 Change Log. Unfortunately they don’t include any notes about how to upgrade

I wasn’t able to find any additional instructions on how to update other than the expected generic steps (docker pull or pip install -r requirements.txt). So my guess at this point is that they have scripts built in to check the version and run upgrade scripts as needed

I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I’d recommend doing this on a regular basis anyway.
• (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup

I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I’d recommend doing this on a regular basis anyway.
• (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup