There's also ems-esp which I use on an older Worcester Bosch boiler to set flow temperatures based on the outside temperature (managed by home assistant).
All our desk phones at work are poe and they have pass through ports to allow connecting a PC to the LAN. Really neat to just have one cable that gives you a powered phone, and Ethernet access.
What switch do you use? I have PoE wifi APs throughout the house, but I bought an Aruba switch and it's super noisy tbh. Fine for me because it's in the basement, but I couldn't recommend it
At one of our offices (it is not a large office), I have a 24-port Netgear POE switch running the show. If it has a fan inside (it may! there's cutouts for fans on the sides of the chassis but I have not looked inside), I've never heard it.
It fit the price-performance curve for our needs several years ago when we eventually outgrew the previous Netgear POE switch...that was also apparently fanless, and that I installed in 2007.
IIRC, it is a GS724TP. It's running a dozen cameras and some access points, and almost all of the rest of the ports are filled up with computers and printers and other Ethernet stuff. No issues at all to to report so far.
(A used enterprise switch with serious fans may be cheaper and/or more featureful and/or more reliable, but do we need that kind of noise at home? We sure don't need it at that small office.
I've also installed some fanless Cisco POE switches with big heatsinks (and dual power supplies, each fed from different sources) on some high-dollar projects where ultimate reliability was kind of a big deal, but... sheesh.
If one of these installed Netgear switches dies in one of these low-risk environments, I'll just patch things up for now and get a replacement coming under warranty.)
some netgear 8-ch poe switch. i don't recall. it's been on and running for about 8 years with no issues, way up near the ceiling of my garage, covered with dust. its plugged into a wrt1900 router i bridged via wifi to my main router.
I use this very specifically for setting up new machines. It's one of those where I don't use it much, but when I do it has saved me a whole lot of time, and it's worked well every time.
Yes same here but with i3, I ran it for over 10 years but niri was just an instant 'aha' moment for me.
I will say, recent builds have a 'mini map' sort of zoom-out feature that I quite like - my one critique of niri was that I would sometimes get 'lost'.
I might give Niri a shot at some point, but yes, this is my thought too: this is more or less the same as having multiple tabbed panes, which enables the grouping GP refers to.
I was running i3 and sway foe years and tabbed tiles never really clicked for me the same way scrolling did. The first time I used a scrolling WM (I tried on of the plugins for sway or hyprland IIRC) it was an immediate revelation. However the sway/hyprland version were always a bit quirky, while niri "just works".
For those on older niri versions I have to say the "zoom out" overview feature is definitely worth the upgrade. As another poster said it really fixes the one issue on scrolling/ tiling wms, which is getting lost.
Newly started applications receive focus, so they're visible by default. They are inserted right of the current view, so recovering the previous active pane is consistent ("left pane" keybinding, or the appropriate gesture).
Things on other desktops are invisible in every WM.
The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know what I expect to be on a specific desktop (it's related to the topic) and seldom need it.
Like imagine editor is on ws2, you open a terminal to /tmp/ to check something quick, it scrolls to the right, then jump to ws3 for your file manager and other stuff and go back to your editor.
Now you want to access that terminal on /tmp/ again. Where was it?
In i3, I just spam-switch workspaces in this case, but at least I can find them. With scrollable wms, every ws can potentially hold that target app.
If you have (having had "Editor" focused, and just opened "TermT"):
Editor | (TermT) | Term | Browser
(FM) | Term | Browser | etc.
(where pipe delimits a pane and parens are the active pane), if you go "next desktop" from "TermT" (the terminal at /tmp), that moves you down the stack of desktops. Moving up the stack of desktops returns with focus on "TermT". You'd then go "left pane" from "TermT" to get back to the editor.
The answer (for me) is to think of desktops as topics. The terminal on /tmp is with the things that prompted its creation. If I needed to check some log output, for example, it's with the project that made that log output.
Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to
Editor | (TermT), Term | Browser
(FM) | Term | Browser | etc.
where the terms stack vertically in the ribbon of the desktop.
I think they aren't referring to "where does it go?" and more being forgetful.
If you have something that would be reasonable to open on any workspace because it's ephemeral (they used a tmp terminal as an example), and you open it, navigate away from it, and then switch workspaces a few time, and then get pulled into a meeting or go to lunch, and come back, switch workspaces a few more times...
"Where did I leave that terminal, I dont remember where I was when I opened it."
In i3wm/sway etc, you can cycle all your workspaces and eventually one of them will have it visible. On Niri, as you cycle through all your workspaces you may never see it because you don't see all the windows in a workspace, unless you scroll through the workspace panes as you cycle workspaces.
It's not a problem necessarily, but it is something to consider. It sounds like this doesn't affect your workflow, but it might affect others.
That's true, you do end up with some windows hidden or partially visible. Niri is still tiling, though, so with proper management you can avoid making too much use of the infinite strip (though that would defeat the purpose of niri).
This seems like a good place to note the "center window" keybinding for windows that don't fit well in the screen (e.g., 2/3 wide pane next to 2/3 wide pane, or 1/3 pane on the right end of the stack next to a full-screen pane).
Vastly preferable to having to look at the edge of the screen.
Many moons ago I tried out a service [0] that did this with pocket articles (although I used to send to pocket vis RSS). It was pretty good! It didn't last long though.
I suspect maybe it's easier now to nail the layout if ai can read content before it goes to print.
AI is indeed a crucial part in solving the two most difficult challenges -- typesetting and curation, although we'll probably do things that don't scale for a little while before fully automating.
If you can spring for Ruckus (I just buy used off ebay), it's worth it. The controller is integrated into the AP - for me that was worth it over unifi alone.
