Strange Behavior in editor -- traced to second window with another instance open.

[coldnight333]

I've just run into a situation where I am managing two HomeAssistant instances.

Because of browser caching and (I presume) presumption of single-instance on a page, the schedule editor was behaving strangely.

There are very reasonable limits to bounds-checking and naturally I'm well outside of them.

If you are having editor issues, check for additional browser windows & tabs with this tool; I thought I'd broken something much bigger.

[kneave]

Oh that's pretty evil, do both of your instances have different hostnames or are they the same?

[coldnight333]

My local HA instance has a hostname, the remote one is not in a DNS and we connect with IP address, via VPN. ( Read I'm the only one who connects to the vpn instance and I'm lazy. )

I first noticed this with two panels showing the scheduler interface card; I was trying to get a large enough view and changing and comparing page/card/section settings - one card I could edit some elements and not others and the second some others but not all of the options between them- until I cleaned up the pages/panels.

Further multi-host work was called off as the behavior was strange. I have since only connected to one instance/host at a time using Chrome on mac. I will see if there is cross site challenges as well as multi-screen lovelace confusion.

[kneave]

A whole bunch of the config is mirrored in to local storage if memory serves so I'll bet that's the issue

[kneave]

I'll look at adding in a UID of some kind to local storage so disambiguate between servers, likely the easiest fix