Stop shouting.
Private address ranges aren’t routed across the Internet. When you are in the hotel, yes, you may have a 192.168.1.x address but when you access the Internet that 192.168.1.x will be masked with the public IP of wherever you coming from via PAT/NAT (Port/Network Address Translation).
Hi there,
Love all the good work you are performing on Home Assistant.
I got a question about the new Home Screen.
I am using Home Assistant 2023.12 in a docker container on my Synology Nas.
When logging in, I do see the new login screen for the local network, but without accounts to select to login.
Am I doing something wrong, and should I adjust a setting somewhere?
You don’t have any persons defined.
I still don’t get it.
Currently ther is need for a password when I’m at home. And when I’m in a hotel there is also the need for a password when I use Nabucasa Cloud. I fill in the password and I stay connected. Or when I want to be safe I disconnect every time and fill in the password when needed.
In the new system there is no need fo a password when I’m on the private range. Whem I’m at home that is fine.
In the hotel it will also open without a password. But that also gives me direct access via Nabucasa Cloud. Even when I’m logged out there for security reasons.
I have rolled back to latest November release because I am not very excited about the new thermostat card. I have seen quite of number of remarks of which the current temperature back to the center position in large font is the most prominent one. I don’t read it has been addressed and so I stay with the latest November release. Annoyingly enough I run into a dead end street unless the feature request on the thermostat card Add option for switching places of target and current temperature in the new climate cards is accepted and implemented. I do hope the developer will appreciate the feedback and change it back.
2 Likes
Thanks for the feedback it seems at least one other user chimed in to say that they were having issues. My idea to install clean and transpose all the configurations appears to not work as another user reported that after installation the machine would not start properly but I have not investigated myself. It does seem to relate to the docker network and I am not sure why it is such a show ending crash/error nor do I have the time right now to figure it out
I’m on 2023.12.1 and on the desktop there is no on/off/mode button on the primary view just temperature controls (-+) (which is what I mean) you have to click on the 3dots to get to the controls. Which is annoying, 3 clicks to turn the device on, click on the three dots, click on the mode, select the new mode. Going from 1 click to three isn’t great even if it looks nicer…
And I keep a test system on an older version, so I can say “oh yeah that did change”.
So often on a new version I think, “that didn’t do that before did it?”
Another option is using VmWare with snapshots.
Hi Tom, thanks for your reply.
Figured it out. Used my persons only for item tracking, not for logging in.
Changed so also logging in is possible for the persons, restarted home assistant, and now it is possible.
The only thing I am not able to do is making my “owner” account appear in the user screen, whilst this is not attached to a person entity.
Do you know of any option to do so?
Again, thanks for your reply. Appreciated!
Found the solution. My owner account was not attached to any person entity. Made the connection, and now it works.
Thanks.
This is really an amazing feature, didn’t know about LTS before!
Given that most data is actually not stored in LTS, would it make sense to add support for the InfluxDB integration as an alternative data source?
It would make even more sense to split these two very different functions out into two different databases. And then, yes, it would make sense that one or both of them could use different database back ends, at the user’s discretion.
Me too
Some screens with lot of gauges and power flow card plus for enegy for my home energy consumption are barely unresponsive
Once I enter into this screen the computer or phone is stuck
This changelog seems to be missing at least 1 breaking change with command line sensors…why was that left off?
I reviewed the breaking changes, and it broke things they were apparently only mentioned months ago?
P.S. your forum also seems broken, when you get the unformatted code popup it won’t let you click either button (at least on Firefox, idk about others)
Yes, it was mentioned when it happened and has been in your log ever since. It should also have generated a Repair for you to address.
1 Like
I was on 2023.11.3 and it neither generated warnings in my log, nor a repair. I even rolled back and explicitly looked for warnings and found none.
After upgrade it also did not generate a repair, it just had an extremely cryptic Python error.
Even if it had, that does not excuse incomplete changelogs omitting critical breaking changes information.
1 Like
It was mentioned on the 2023.6 release notes when the change was introduced, and a repair issue was issued at that time.
Could it be you pressed the ignore button then, and forgot about it?
4 Likes