Makes sense, thanks. Yeah idk about usb serial over Ethernet, it’s an interesting idea but I wouldn’t want to introduce more moving parts (and/or latency) to the network.
Makes sense, thanks. Yeah idk about usb serial over Ethernet, it’s an interesting idea but I wouldn’t want to introduce more moving parts (and/or latency) to the network.
Proxmox is going to be a lot easier to pick up if you’re coming from vmware. Kubernetes is a beast with a considerable learning curve so if you’re not familiar with it already then I wouldn’t recommend it for a lab environment (unless the goal is specifically to learn it).
I’ve migrated most of my lab from a mess of proxmox lxcs over to k3s (I use k8s at work), except for home assistant. I’ve been back and forth on that one. I really like being able to back up the entire vm before running updates or whatever. Could you use a node selector to force zwave or zigbee or whatever to run on the node that has the usb device? Or is it still a pain in the ass that way cause you have to know the path on the specific host… I haven’t tried that yet.
My only contribution is to stay away from ultraloq. I have their zwave deadbolt and it’s terrible. I will probably replace it with something schlage.
Oh weird I thought that icon was just for highlighting requests to my backend
Any recommendations for tranquilizer sentries that work with HA?
Yes, this will definitely happen
If you have your compose files in git, you might be able to use renovate to send you pull requests with image updates. I’ve done something similar with kubernetes but I think it supports docker compose too. You might need some kind of automation on your hosts to keep things in sync.
I’m not actually familiar with truenas or its ui, but if you have kubectl access you should be able to poke around in the logs and see what’s going on. I’m not sure if these logs are shown in the ui anywhere. With helm, there are so many different things it could be that there’s no use in speculating without some logs.
All that message means is “the thing didn’t start” and isn’t gonna tell you anything about why. You’d need to dig into pod logs or something to see if you can find the actual error that is preventing startup.
Rack mounting non-rack-mount gear always seemed like an interesting application to me. Raspberry pis, tiny lenovos, network gear, etc.
Cloudflare cause they already had my DNS and google domains was on its way to the google graveyard. Not sure how privacy respecting they are but they do offer some kind of partial whois redaction. Surely better than google though?
TIL about the auto entities card. I’ll have to try that out. Since I don’t actually know anything about that card, I don’t have anything useful to offer specific to that plugin. But coming from a different angle, I wonder if using a template sensor to invert the “default” state and hiding the original entity (+ some clever naming) would help to make it behave how you want?
<$1/mo for bitwarden hosted premium is a no brainer for me
To be fair, if you’re ordering from Amazon, your personal info was already “part of the Amazon machine.”
Did you order it using your Amazon account? I think they pre-configure them for you unless you say “this is a gift” when ordering.
I’m not totally sure what this means in practice other than maybe the continued health of the project. Which sounds good. I’ve been pretty happy with the reliability of zwave js too.
Have you looked into grafana cloud? I haven’t used it myself but they have a free tier. Or if you’re open to self-hosting you can run loki and grafana yourself.
You’re likely not going to find a premade dashboard that does exactly what you want, but grafana is extremely powerful if you’re willing to put in the time to learn it. There are ways to visualize things across hosts without having to configure things separately for every host. If you’re using the same mechanism to scrape metrics from each (sounds like you’re using prometheus + node exporter?), this could be as simple as adding a
by (node)
(or whatever the label name is if it’s not node) grouping to the query on each panel.