That would be illegal. I worked on the software deployment of these devices in a store. If we increased the price, we’d automatically give the customer the lowest price in the last several hours.
The other problem was they were extremely low powered and low bandwidth and it would have killed the battery to update more than a few times a day.
Accidentally typo your password and get blocked. And if you’re tunneling over tor, you’ve blocked 127.0.0.1 which means now nobody can login.
Paperless does support defining a folder structure that you can use to organize documents within that paperless media volume however you should treat it as read only.
OP could use this as a way to keep their desired folder structure as much as possible, but it would have to be separate from the consumption folder.
Yeah I always use states when I can but the original post description made it sound like the integration was directly sending a notification. If it didn’t set a state (which would be weird) then you’d need an event.
https://www.home-assistant.io/docs/configuration/events/
In the dev tools > events tab you can subscribe and see what events are sent. There should be an event that is sent when it sends a notification. Create an automation that listens for that event
One of the problems with the cloud-polling integrations is that they will frequently poll the back-end APIs to get the current status of that device. A normal user might only open up the app once or twice a day and call the APIs, but these integrations will go 24/7 every 10s-5m. That can add up to a non-trivial amount of traffic. If there’s 100 users opening it up once a day, that’s not a lot of traffic, but 10 users polling every 1 minute is equivalent to 15k people doing something once a day.
I actually saw one of my integrations I used defaulted to updating every 10 seconds. I decreased that because I didn’t want to draw attention to it.
A business will look at their usage and ask why there’s more than expected traffic. They could be running their server on a potato. They could go back and support Matter, that costs money, requires skilled engineers, and cuts into profit margins.
While it sucks, that is something they could point to in a court about “economic harm”.
I don’t fully understand what you’re saying, but let’s break this down.
Since you say you get an NGINX page, what does your NGINX config look like? What exactly does the NGINX “login page” say? Is it an error or is it a directory listing or something else?
Then try something like:
Create Quanity unit of ml and a liter unit
In your product use: Unit stock: bottle or liter Unit purchase: bottle Consume: ml Price unit: ml
Set a product specific QU conversion of bottle to ml
Weirdly, the quick consume unit is based on the stock unit, not the consume unit. That seems like a bug.
The problem with Grocy is that going too fine grained means you’re unlikely to keep it up to date or it be accurate. I would not try to track your usage in ml. Just track it at the bottle level.
However you can still track the price per ml because grocy lets you independently set units. Just define a mapping between bottle and ml.
It just updated on my phone to the new icon. I tried to give it a chance but wow that looks not great. Something about the scale and lack of discerning features.
Will I still need to consider multicast DNS if my DNS server is on-prem (Pi-Hole + Unbound)
Multicast DNS is separate from DNS, so even if you have Pi-Hole, you’d still have devices using mDNS. It’s possible to route mDNS across separate IP networks seeing as how there’s mDNS relays across VLANs which would suggest Wireguard could support Multicast. Other things use Broadcast (e.g. WoL) which is a bit more challenging to forward across IP networks.
I’m not familiar with GRE so I couldn’t comment on whether it’s possible or not. I guess it all depends on how confident you are with your networking skills. If you get it working, you should definitely document it and share with others.
I didn’t quite do what you did, but I ran HA in a Kubernetes cluster which was logically a separate IP network. I had to setup the container with multiple network interfaces and specially craft the route table to forward broadcasts + multicast traffic to the correct network.
Tailnet appears to be Tailscale which is Wireguard underneath. This means it operates at layer 3 (IP). However a bunch of smart home stuff (mDNS, WoL, etc) all depend on layer 2 connectivity (same subnet).
That means some stuff won’t work correctly.
If you’re running Docker for servers not development, then you can make Hyper-V work. I used to do that before I got a separate Linux server and it worked out.
Just setup a network adapter that gets bridged to your Ethernet adapter, then create a VM that uses that bridged adapter. The Linux VM will appear like its another computer on your LAN and you can use Docker with host Network.
Mine was flashing my Emporia Vue2 home energy monitoring system with ESPHome
I’m always interested in sensors (got a bunch of home made Air Quality and CO2 sensors) so seeing real time energy was cool.
With the per circuit sensing I’m experimenting with identifying if my fridge is left open, or identifying when my clothes washer is finished.
What is your threat model or goal? It could hide the device you use to connect to the instance, however a lot of actions you do on Lemmy, including all upvotes, are public to other instances.
If I create a secondary config as you are suggesting, wouldn’t it create a conflict with the server blocks of default.conf
No, you can have multiple server
blocks with the same listen
directive. They just need to differ by their server_name
and only one server
block can contain default_server
; Reference
NGINX will use the server_name directives to differentiate the different backend services. This is a class virtual host configuration model.
There was an uncaught exception to boot gunicorn workers
That’s odd that it didn’t cause the Docker container to immediately exit.
What now? So now that it looks like everything is working. What is the best practice for the nginx.conf? Leave it all in /etc/nginx/nginx.conf (with user as root), reestablish the out box nginx.conf and /etc/nginx/conf.d/default.conf
My suggestion would be to create /etc/nginx/conf.d/mycooldjangoapp.conf
. Compared to conf.d/default.conf
, this is more intuitive if you start hosting multiple apps. Keep it out of the nginx.conf
because apt-get or other package managers will usually patch that with new version changes and again it gets confusing if you have multiple apps.
First the basics. Connection refused means that nothing is running on “http://192.168.0.2:8020/”
0.0.0.0/8082->8082
Confirmed upstream block container is running and on the right exposed port
What steps did you do to confirm that this is running?
I’ve been eagerly looking forward to the time when I can replay my Echo Dots with a self-hosted solution, but so far I haven’t found hardware that I really liked the look and style of.