This is a clean install of the Home Assistant Operating System on a Raspberry Pi 3 B+.
The Android app gives exactly the same result.
I even tried the Samba route, but it doesn’t show up on my network even though it says it’s running.
I tried a new clean slate install with the same result. The filesystem is “read only”, so there’s no possibility of making changes. I’ve tried every way I can find to make the filesystem writeable, to no avail.
I am with wo1fmane here… I’ve done 5 fresh installs, EACH ONE IS GEO LOCKED, also to note, simply because I could I even tried 2 different other sd cards, the same result. For web browsers again simply because I could. I have used browsers (PC opera, chrome, chromium, firefox, IE, Edge) (MAC Brave and Safari) ALL have the same result wo1fmane is talking about
Same for me. I cannot change the location at all, it’s stuck. I can move around the mini-map, but this does not change the location of the pin in it. Right-clicking also does not change the location of the pin on the map.
Here is how to solve the issue… (in version core-2022.5.5)
Steps:
Go to your ‘Map’ card (showing the incorrect location)
Click the ‘pencil’ icon (top-right corner)
Select your ‘Home’ location (right-hand side)
Click & drag your ‘Home’ icon very slightly
… once you drop the icon in a location your ‘Map’ card will now default to the new location.
Having an issue here. I just moved. Trying to move the marker on the map does not work. Even after hitting save and restarting. Marker just reverts to old location. Any ideas?
Pinch the map, this compresses distances, then you can drag your home to your area. Then reverse pinch the map, and you can drag to a fairly precise location
These answers aren’t working for me. I just get this:
and then if I click the edit button, I get this:
There is literally nothing in my configuration.yaml that sets a home location. So why does HA persist in saying it’s defined in there? Why can’t the error message give the line number of configuration.yaml where the home location is set, so I can see it for myself?
egrep -r <my latitude> config showed it was defined in .storage/core.restore_state and .storage/core.config. Renaming both those files and rebooting just resulted in .storage/core.restore_state being regenerated with the same values — and my home location being changed to 0°, 0° — and still not being editable!
I suspect that the way the home location was defined changed several versions ago, and the change that introduced the new way simply left old configs untouched, rather than migrating them. Am I stuck unless I nuke the whole HA setup and recreate everything from scratch?
Here’s my configuration.yaml. Prize for the first person to point to the line that sets the home location, as claimed by the error message
# Loads default set of integrations. Do not remove.
default_config:
homeassistant:
external_url: https://REDACTED
country: GB
http:
use_x_forwarded_for: true
trusted_proxies:
- 192.168.1.11
# Text to speech
tts:
- platform: google_translate
# Workdays
binary_sensor:
- platform: workday
country: GB
province: England
workdays: [mon, tue, wed, thu, fri]
excludes: [sat, sun, holiday]
This is a bit of a guess, but you could try removing the country: key under homeassistant:. This can now be set via the UI. (So can external_url as well by the way).