Lars Stegman

This is exactly my thoughts. Applications/deployments should specify what port they need to be open and nginx should take care of it (if the port is not already claimed)

This is great! When this is merged, ESPHome can be updated to use the new version. This should finally fix this issue: https://github.com/esphome/issues/issues/3982

@PolarGoose will you continue the work on this PR?

I have no idea how to do that yet, but I can try.

@powersj > Is that due to an update in the library with how it handles errors? I think this is the only explanation, since nothing else changed in the opc...

@powersj would it make sense to have the aggregator store its state as well? I don't even know if aggregators can store their state, to be honest.

That's right, this functionality is not implemented. It shouldn't be difficult to add it. Can you open a new issue describing the functionality?

I also run into this. Notes are also not always included. I am using an iPad with iOS 17.2

I looked into the code a little bit and it looks like the field that is in focus does not update its state before the onAdd logic runs, which causes...

I prefer the YNAB style where the sidebar is an "inspector" for the currently selected Category. A separate page would mean a lot of clicking around to get an overview...