https://youtu.be/jVhlJNJopOQ

I just wanted to add this video to your comment because e-ink is so cool and this guy has a bunch of macro shots of the displays that are awesome and you can see the particles in the screen changing colors.

https://youtu.be/1qIHCUWAgh4

So cool!

This guy’s channel is so awesome, glad to see it posted here. He has all kinds of cool tools that he built in his lab like a scanning electron microscope. His videos on atomic force microscopes and laser lithography are really fascinating as well, he is really great at explaining the concepts too, definitely recommend!

+1 for Raindrop, that app is amazing, I keep watching for a self-hosted version/alternative that is as good and they are getting closer. The killer feature for me is being able to highlight stuff and then when you visit the site again you see what you have highlighted (in addition to saving them elsewhere). I also pay for premium because it’s great, I don’t use a ton of the pro features either.

So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former. It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping. Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.

This is awesome, I look forward to the weekly updates and have found lots of great tools from that. Keep up the awesome work, it is very much appreciated!

Well 5ghz requires more power, has less range, and needs its own antenna so for microcontrollers this makes it pretty pointless for devices that need range and low bandwidth for sending sensor updates, especially those that are battery powered. 5ghz can also have its own issues in cities if you have a lot of use of the DFS bands as well as being worse at traversing reinforced concrete.

Also, a 2.4ghz radio can also sometimes support other things like zigbee, BT, and BLE which can be used for other functions.

For what it’s worth, I have probably 50 WiFi devices and the majority of them are 2.4ghz sensors or switches and other low bandwidth tasks and I don’t have any issues, even when living in an apartment complex. If you are having issues you might need different hardware or more access points or something.

Anyway, all that to say that 2.4ghz definitely still has a lot of utility today.

They also make this one which uses a CM4 but you can control 4 machines! I have been eying it now that I can get CM4s again, thanks for the post!

Do you want to not use your DL380? IF no it might make a good moonlight host!

Yeah I’m with you, I read most of it but I just don’t know where the disdain comes from. At most scales of infrastructure anymore you can use them interchangeably because the difference is immaterial in practical applications.

Like if I am going to provision 2TB I don’t really care if it’s 2000 or 2048GB, I’ll be resizing it when it gets to 1800 either way, and if I needed to actually store 2TB I would create a 3TB volume, storage is cheap and my time calculating the difference is not.

Wait until you learn about how different fields use different precision levels of pi.

hmm the last line in the log above there says:

“[Fatal ConsoleApp: The requested address is not valid in this context. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions Press enter to exit.“

So that sounds like that the container might be running but sonarr is not. Did you ever get it working?

Your netstat command shows a process named docker-proxy using that port, which confirms what the log says. If your container isn’t running you can try to find the process using it with netstat or lsof, it might be a stale container process or something but a reboot is often faster than figuring out what it is to see if that clears up whatever is using the port.