computeRTL exception breaking ZHA configuration editing

[ahaverty]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

On trying to update my ZHA configuration, by editing a field, and clicking "update configuration", nothing happens.
When I refresh the page, the configuration hasn't been updated.
The reason I'm reporting as a UI issue is because it seems to be an exception with computeRTL here.

Perhaps this exception is preventing the form from submitting?

Describe the behavior you expected

The ZHA configuration to update, or report an error.

Steps to reproduce the issue

1. Open ZHA integration
2. Modify a config field such as 'default light transition time'
3. Click "update configuration" button

What version of Home Assistant Core has the issue?

2022.10.4

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome Version 106.0.5249.119 (Official Build) (arm64)

Which operating system are you using to run this browser?

macOS Ventura 13.0 Beta

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

zha-config-dashboard.ts:210 Uncaught (in promise) {code: 'unknown_error', message: 'Unknown error'}code: "unknown_error"message: "Unknown error"[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()__proto__: (...)get __proto__: ƒ __proto__()set __proto__: ƒ __proto__()
value @ zha-config-dashboard.ts:210
await in value (async)
handleEvent @ styles.ts:370

### Additional information

_No response_

[ahaverty]

Regarding browsers/cache: I'm seeing the same issue on my android phone's home assistant app (not browser).

[ahaverty]

I've tested on Safari and get the same issue.
I'm now assuming it's not related to that RTL line, and that the browsers aren't accurate in what they're breakpointing here.
I've tried mapping my filesystem to this repo, but it still thinks it's the RTL line.
I can't see any network requests to try to debug if it's some configuration data issue, although I'm doubtful that's the cause, as I've tried with all the checkboxes unticked, and some small values for the seconds (600) and still have the same issue.

Everything else with ZHA works, and this has worked for me in the past. I just haven't tried an update in the last few months, so I'm not sure when this issue started unfortunately.

[ahaverty]

The reason I think the RTL line error in my console is a red-herring is that I don't get a console error on page load or refresh (and the reported line is inside the render block).

It only errors in console, after I click the update configuration button.

[ahaverty]

So I deleted and re-added ZHA, starting with a new network.
Straight away, I'm able to update the configuration for ZHA, and I also see a config section for alarm panels that I've never seen before.

Is this normal, or could I have missed out on some kind of config migration over the last year perhaps?

[dmulcahey]

Do you have an alarm control panel paired?

[ahaverty]

I have a Ring alarm setup via cloud, and an alarm panel UI card.
But no, no Zigbee alarms. After starting from scratch just now with ZHA, I literally don't have any Zigbee devices.

[ahaverty]

I'm not sure how relevant, but for context on why I've re-installed from fresh, I have a full workthrough over at zigpy/zigpy-deconz#208
Long story short, an unexplained issue last night caused all 60 of my zigbee devices to be uncontactable. The only solution I found was to re-pair each device individually. @puddly helped debug and couldn't see anything out of the ordinary with my db files or steps.

I'm committing to resetting up all 60 devices tonight on this fresh install. Perhaps I've just hit some really strange edge case from running ZHA for over a year without much maintenance other than HA updates.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.