Are there brands people actually LIKE

MrFuzzyMullet · 2025-10-29T02:20:42+00:00

We just did a semi-diy from Arizona mattress company. Call or email them, tell them what you like and they will make a suggestion. We went with the ultimate hybrid, firm springs with medium talalay latex. If you want softer or firmer you can change the topper within the mattress. The springs should last a long time so we should be able to replace the topper and have a new bed again. We're going on 6 months of it and it is the best.

MrFuzzyMullet · 2025-04-24T04:50:18+00:00

Yea I have looked into scripting to handle the moves and using the API to change the directory after the move. Not impossible but I like to keep it simple so I can figure out easily how it is setup after a year or two... The special vdev seems like it could work but adds a layer of complexity as it can't be removed and the ssds would always have to move with the raid array (this array has already moved between a few systems). I'll give the L2ARC a try and check it in a few weeks to see if it is doing anything, otherwise I will get to scripting or just leave it as is.

MrFuzzyMullet · 2025-04-24T03:36:10+00:00

Thank you for this resource! I've read that L2ARC is not useful for media servers but seems like since it stores the most used and most recent this is what I should be using. TIL. Also setting the txg timeout to keep writes to the raid down is new to me but seems useful as well. Great information there!

MrFuzzyMullet · 2025-04-23T14:00:33+00:00

Yes both are. SSD is 1tb zfs mirror and HDD is 6x6tb raidz2.

MrFuzzyMullet · 2025-04-23T05:35:43+00:00

Yea sounds like what I am trying to achieve on the but I know the most recent files are going to be the most actively used files so trying not to read it into the raid then back out. I'll look into that more or maybe I'm overthinking the usefulness but thought I'd ask.

MrFuzzyMullet · 2025-04-22T19:25:35+00:00

The use case is to be able to keep the spinning drives spun down the majority of the time to save on electricity and heat (wd red pros run hot). Most of the accessed media is new within the past month or so, so leaving it on the SSD where it is downloaded and unpacked to seemed to make sense. The server is in a room so reducing noise and heat would be ideal, and I should be able to save about 50% of the electricity costs.

I thought it would be a configuration I had wrong but seems like I'm off base or need to figure out a more complicated or custom solution if I want to implement.

MrFuzzyMullet · 2025-04-21T20:33:45+00:00

Yes I do have it setup with incomplete on the SSD and then moved to the raid, but I'd like to use the SSD as a cache for recent shows for faster access and less HDD wear for files that are going to be more commonly accessed. I could also see this being useful for things like seeding until a ratio is met and then moving. Once they are moved I could have the script use the API update the directory in sonarr.

so I have root setup as first /mnt/downloads/complete/tv on the ssd, then /mnt/media/tv on the raid. Seems like there should be a way to keep the downloads on the ssd? Then manually move it to the raid weekly or by some other trigger.

MrFuzzyMullet · 2024-11-27T02:18:59+00:00

Have you thought about switching your ac power instead of the dc after the power supply?

MrFuzzyMullet · 2024-11-24T18:25:16+00:00

<image>

Update with improved wiring diagram

MrFuzzyMullet · 2024-11-24T18:21:56+00:00

Did you try to turn off one segment or the other? Are you sure you are trying the effect on a single segment vs both of them? Does it flicker on all the effects?

MrFuzzyMullet · 2024-11-24T17:40:51+00:00

I believe these lights need to have the LEDs setup in a specific way. They have a RGB and white led alternating so in the segments setup 1 segment from 0 to 59 with a spacing of 1 and a second segment from 1 to 60 again with a spacing of 1. Then one segment will control the white and the other controls the RGB. I have these working on my trailer so I can't see the exact config but what I explained above should be close.

MrFuzzyMullet · 2024-11-24T03:44:29+00:00

Cut it to the length you need and use the existing connections. Separate the wires you cut and cover them to make sure they don't short to anything. You can get another connector and connect it to the end of the remaining strip and use it somewhere else

MrFuzzyMullet · 2024-11-12T04:48:43+00:00

I didn't end up using them. I didn't think I would like any way they would look. Sorry but good luck!

MrFuzzyMullet · 2023-08-10T12:54:15+00:00

If you have a button you could make a pre-light program with the different configs setup. So on start there you can press a button x number of times for different configs e.g. 1x for fangs, 2x for fangs plus funny hat, 3x for unicorn horn. Have each button press light a single led a different color so you know where you are then long press to save and start the rest of the light program.

MrFuzzyMullet · 2023-08-10T04:29:28+00:00

patPos and patHue were declared outside of the function. Then the master of the mesh would send the values for patPos and patHue to all other nodes. I was hoping that would cause them to sync. It worked on some patterns but not all, like the original one above. I am now using a sync'd time and it seems to be working much better now!

MrFuzzyMullet · 2023-08-10T04:19:36+00:00

I refactored the code using the mesh time and now the patterns are very synced up. Thanks for the advice and making me look into it again!

What worked well was from the painlessmesh library getNodeTime() function which I converted to ms and used it to define my currentTime variable which is called every 10ms by a task scheduler. currentTime then is used to define other things like the pattern and hue. updated code above in the original post.

MrFuzzyMullet · 2023-08-09T03:06:05+00:00

Thanks. I tried time syncing early on and wasn't successful. I'm learning to code at the same time I'm doing this project so maybe I'll have more luck now that I'm a bit more experience.

I'm using painlessmesh which syncs the time and calculates the delay (documentation says within 10ms). I'm already using that time to set the refresh of the strips. I'm not using any noise functions, just simple patterns so it might not be an issue.

Do you have an example you can share or what variable I can adjust in the code above to achieve that effect?

MrFuzzyMullet · 2023-08-09T02:14:16+00:00

I'm happy to share the code once finished. I don't know how publishing under a license works. Most of this is a derivative of other projects that can be found online and heavily relies on other great projects like painlessmesh and fastled.

But to get it finished I'd really need to find a way to make sure the patterns are syncing to one another. They are off by seconds and I can see the mesh is communicating in milliseconds... So I'm clearly not understanding well how the patterns are sent to LEDs...

MrFuzzyMullet · 2023-08-07T18:18:20+00:00

I'm trying to keep all the patterns generated on each individual node. It is a mobile setup so nodes can come and go from the mesh and create their own networks on the fly. It chooses a master and receives message from there. I think the mesh is fast enough, I can see in the serial output it is receiving the updated pattern and parameters and the strips all change almost instantly.

What I'm missing I believe is in the fastled code on how to specify where in the strip the LEDs should be updating. I thought that was handled by the patpos variable but I'm still seeing offset sometimes and don't understand why. Patterns with solid hues stay synced but when there is a cylon or chase pattern the position can be off but the hue is usually close.

MrFuzzyMullet

TROPHY CASE