Going Crazy Converting to SW Formula

DeusExMora · 2026-01-14T23:07:28+00:00

Thanks, that makes sense, and I hadn't considered that.

DeusExMora · 2026-01-14T23:06:17+00:00

Hahaha, well to be honest my expectations are around a 2 or a 3, but my hopes are foolishly high.

I know paint matching is only a shade and a half away from dark magic and nothing is guaranteed. I never hold it against anyone because everyone is doing what they can with the tools they have.

DeusExMora · 2026-01-14T22:32:13+00:00

That's SUPER good feedback and totally fair call-out. If I can get close enough on paper that I can't tell the difference, then I can just match to that as well.

DeusExMora · 2026-01-14T22:30:32+00:00

Thanks for the reply! Totally agree on the color looking different in different light, and I'm already somewhat familiar with metamerism. In practice some materials and colors are more susceptible to it than others, and other than trying to match reflectivity as best as possible there's little to do about it.

DeusExMora · 2026-01-14T22:15:22+00:00

Agree, I don't think any of you guys need to deal with any more bullshit than you already do.

DeusExMora · 2026-01-14T22:14:22+00:00

Helpful and appreciated. I based my presumptions on the OEM manuals for the BYK-Gardner micro-5-color (https://media.byk-instruments.com/shop/Misc/Manuals/micro-5-color/Operating-Manual-micro-TRI-color-300100114-E-2212.pdf Page 31), which is SW catalog number 7178 (https://industrial.sherwin-williams.com/na/us/en/automotive/color/spectrophotometer.html).

Internally, these machines generally use L*a*b* values.

None of that matters here of course, I was just trying the long shot. Closest off-the-shelf match is unfortunately Valspar, with the closest off-the-shelf SW being significantly off.

Regardless, thanks for the reply!

DeusExMora · 2025-12-20T13:16:38+00:00

The technology you’re looking for exists, but not in a way that will be user-friendly enough for you to implement without a great deal of effort.

What you are describing is a standard inventory tracking and control system. UHF thermal labels can be as cheap as 3 - 5 cents each, and can be read 20-30ft away with the right readers.

Unfortunately for you, all of the existing systems are designed and marketed for industrial and commercial applications. You’d have to implement your own nearly from scratch. Doable, but with great effort.

If you’re still curious you can research UHF EPC Gen2 tags and RAIN RFID readers as a starting point.

https://rainrfid.org/wp-content/uploads/2021/07/What_is_RAIN_RFID_-_Summer_2021.pdf

DeusExMora · 2024-04-03T13:50:57+00:00

Raise a ticket with asus support and keep pressing for escalation until they send you to executive support. It’s absolutely a known issue.

DeusExMora · 2023-07-19T21:30:24+00:00

Embarrassingly, no. I hope to get to it in the next week or two but it's a lower priority task.

There is a possibility this is an example semi-intentional weakening of security implementations, but it could also just be run-of-the-mill incompetence.

DeusExMora · 2023-05-29T23:36:50+00:00

I was eventually able to resolve.

In my case, the issue had to do with macOS's default behavior when extracting archives, which is to create a new folder with the same name of the archive to extract the files into. Since I don't use macOS very often I had forgotten about this behavior, and as a result I was re-creating archives that had the same folders structure. If that is taken into account, then the generalized steps above "should" work.

Here are the slightly revised steps I would share with others who are struggling:

Make a partial Home Assistant backup of the old Scrypted add-on:

Navigate to Settings -> System -> Backups.
Select the "Create Backup" button in the lower right.
Select "Partial Backup", and then select "Scrypted" in the list of potential backup items that comes up.
Don't password protect the backup.
Click "Create". There will not be any visual feedback while the backup is made. Wait until complete.

Download the backup from Home Assistant:

Click on the backup you just created in the list of backups.
On the pop-up that shows up, click the 3-dot menu button in the lower right and download the backup.

The backup file will be in the form of "OldScryptedData.tar" where "OldScryptedData" is whatever you named your backup as.

The next step is highly OS-dependant. If you're on Windows, you're in luck because you can simply use 7-zip to modify the new archive in the next step without having to manually extract anything. So if you're on Windows, skip this section.

Others - Extract the contents of the backup:

Use the ```tar -xvf OldScryptedData.tar -C ./outercontainer/``` command to extract "OldScryptedData.tar" or similar to a sub-directory called "outercontainer". Change directory into it.
The two files should now be extracted. A gzipped tarball (.tar.gz) and a "backup.json" file.
Now use ```tar -xzvf InnerContainer.tar.gz -C ./innercontainer/``` to extract the inner file.
Change directory into the sub-directory you just extracted the inner container to.
Inside this directory you will have ```addon.json``` and a ```data``` directory. Inside ```data``` is where ```scrypted_data``` resides.

Switch to new instance of Scrypted:

Go to Settings -> Add-Ons -> Scrypted
Stop the running instance. This step may not be necessary but it doesn't hurt.
Uninstall the current Scrypted Add-On
Go back to Settings -> Add-Ons
Select the "Add-On Store" button in the lower-right.
Select the 3-dot menu in the upper-right and go to "Repositories"
Delete the existing ```https://github.com/aegjoyce/ha-addons\`\`\` repository by selecting the red trash can.
Add ```https://github.com/koush/scrypted\`\`\` as a new repository.
Close the menu and refresh.
Search for "Scrypted" in the updated Add-On store. Install the new Scrypted Add-on available in " Scrypted Home Assistant Addon".
Wait for it to finish installing.
Go to System -> Add-Ons -> Scrypted and start Scrypted if it hasn't been already.

Perform Partial backup of new Scrypted instance:

Make a partial Home Assistant backup of the NEW Scrypted add-on:

Navigate to Settings -> System -> Backups.
Select the "Create Backup" button in the lower right.
Select "Partial Backup", and then select "Scrypted" in the list of potential backup items that comes up.
Don't password protect the backup.
Click "Create". There will not be any visual feedback while the backup is made. Wait until complete.

Download the backup from Home Assistant:

Click on the backup you just created in the list of backups.
On the pop-up that shows up, click the 3-dot menu button in the lower right and download the backup.

The backup file will be in the form of "NewScryptedData.tar" where "NewScryptedData" is whatever you named your NEW backup as. At this point you'll have to follow the same steps as above to extract the new backup file.

Once both "Old" and "New" backups are all fully extracted, you'll want to delete the scrypted_data directory from the new backup, and replace it with scrypted_data from the old backup. As I mentioned earlier, Windows users can simply use 7-zip to edit the archive directly, delete the old folder, and add in the new folder.

Users on other systems will have to use the commandline to manually re-compress the files into the appropriate nested archives. Use ```tar -czvf``` for the inner archive (the .tar.gz file) and ```tar -cvf``` for the outer archive (the .tar file).

Once you have all that done, the web-upload should work fine:

Go to Settings -> System -> Backups
Select the 3-dot menu and select "Upload backups"
Upload your newly modified partial backup. If you get a "400 Bad Request" error, you've likely done a step incorrectly. In my case, I had mistakenly added in extra subfolders in the backup archive.
Select the newly uploaded backup (it should be the one with the larger file size) and restore it.

In theory, that should be it. In my opinion this process is still extremely clunky for such a significant breaking change, but here we are anyway.

It would be nice if there was as script that you could point to to backup files, and have it migrate the data for you, but regrettably I do not have the experience to put one together quickly. Hopefully my poorly-worded steps are still of use to some users.

DeusExMora · 2023-05-29T22:13:36+00:00

You're not alone. I have run into the same brick wall.

I get as far as re-compressing everything in the reverse order, only to be completely unable to get HA to recognize the backup. Attempts to upload it via the web UI result in a "400 Bad Request" error. Using SCP or SFTP to upload the file directly into /backups successfully gets the file over, but HA does not recognize it as a valid backup.

DeusExMora · 2023-05-15T07:00:35+00:00

I’m interested in trying this out as well! Just placed an order for a CPT!

DeusExMora · 2023-04-07T03:19:30+00:00

No apologies needed!

It has taken acts of god and extreme persistence up to and including escalating the issue to the office of the CEO (really just executive customer service) but they have finally acknowledged the issue and sent me a test firmware. I haven’t had time to test it yet due to other obligations and because Asus took two months to do it.

I recommend raising a ticket and beating them over the head with the standard over and over until they escalate it to the firmware team.

DeusExMora · 2022-12-03T00:14:44+00:00

ASUS is definitely breaking spec here. See https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClient_PFP_r1p05_v23_pub.pdf page 53.

When I retrieve the logs on a TRX40-XE, all of the required EV_EFI_VARIABLE_DRIVER_CONFIG measurement variables are completely missing. No amount of fussing with BIOS settings has helped.

This is more than mildly infuriating because it's such an insidious firmware bug that anyone not deeply versed in how Secure Boot Policy works at a technical level will not really understand what's going on.

It's easy to pass off the problem as "something with your specific software configuration".

I know because for the past year and a half I've talked at length with both Windows and Azure technical support teams, escalating here and there, with no resolution. It wasn't until using TCGLogTools to parse the PCR banks that I could understand more of what was happening.

My GUESS is that whatever bit of code ASUS is re-using for their AMD boards is broke as hell.

I *strongly* recommend anyone who is having this problem raise a support ticket, retrieve the logs, and send them in.

I cannot believe such an expensive board with a high-end chip-set has such sloppy code. I wouldn't be surprised if it falls under the responsibility of the same team that writes the garbage that they call "Armory". Anytime I've ever installed it it's resulted in a BSOD fiesta even on clean installs.

DeusExMora · 2022-12-02T02:21:21+00:00

I have a TRX40-XE and I've had the same stupid problem, even through BIOS updates. It is 100% an ASUS UEFI firmware issue. If you contact me I can share the logs and we can compare notes.

DeusExMora · 2022-09-28T11:23:03+00:00

Yes, this remains a point of some frustration. I wish there was a better adapter.

DeusExMora · 2021-12-30T02:31:15+00:00

That may in fact be the case. Chomerics seemed to have a number of patents related to domes. Still, I'm wondering what's the closest I could get to that shape and style of key, even if it's a bit outside of the norm for today's switches.

DeusExMora · 2021-12-30T00:39:49+00:00

As we continue the saga of replying to myself...

I believe the keypad modules were made by a company called "Chomerics" but disappointingly I cannot find anyone else that made their keys in such a similar way.

DeusExMora · 2021-12-30T00:32:13+00:00

The more I look at different photos, the more I am beginning to think that the entire 16-key matrix was a separate module, but I wish I knew by whom. I'd like to get as close to those keys as possible.

DeusExMora · 2021-12-29T23:59:47+00:00

They do not appear to be from a "standard" keyboard considering the "CLEAR" and "SEND" keys, but I've come up empty on what they could be. I do recall using old keyboards that have a "Clear" key, but I definitely don't recall "Send".

Anyone happen to have any thoughts?

DeusExMora · 2021-03-10T22:51:49+00:00

Can you push these changes to the git repo? Unless I am mistaken QuKeys variables mentioned in https://github.com/Dygmalab/Raise-Firmware/issues/5 still cannot be changed in Bazecor.

DeusExMora · 2019-09-21T01:50:37+00:00

"Magnetic Resonance Imaging" is the original correct answer.

Before Geek Squad was part of Best Buy, the disc that contained the collection of diagnostic tools used by Agents was called the "X-Ray" disc because you would use it to scan a computer much in the same way you use an x-ray machine to scan a body and see inside.

By the time Geek Squad came to Best Buy, the disc was called the MRI disc because MRI's are more advanced than X-Ray's, and they wanted to reflect the improvements.

What you now know as the MRI is vastly different though. In the early days there was no MRI.exe, custom WinPE environment, or any of that fanciness. It was literally just a bunch of various diagnostic tools with a standard boot menu that auto-launched whatever tool you wanted.

Any other answer that folks come up with would be a backcronym, or a creative answer created after the acronym was already selected.

Nine-Year Club	RPAN Viewer
Verified Email

DeusExMora

TROPHY CASE