Anybody having infinite loading issues after 2.5.0 or 2.5.1 updates?
1 Like
i'd never heard of ha-china before. can you provide some context about the switch to that org?
Looks as the repository name changed: Home Assistant China (unofficial)
Seems odd.... I'd also like to understand why and what this new repository represents.
I joined an organisation. It doesn't affect anything regarding the integration.
It's an organisation for HA in china. As I live here i decided to join to give more exposition to the integration and get more support.
1 Like
i've not had any issues like that...
It is not an issue. 
I wasn't forced to join. I join voluntarily. It's not by the gov it's an organization by Chinese ha community. I want to gain more followers and users for my integrations.
Hi, as the owner of the organization, I think I can explain both the purpose of this org and why I drafted these rules.
First of all, I’m also a Home Assistant volunteer. My hope is to create a place where Chinese Home Assistant developers and volunteers can collaborate together more effectively.
At the same time, different countries have different laws and regulations. I also want this organization to operate in a legal and compliant way, so that Home Assistant can continue to grow and go further in the long term.
1 Like
So why do you need to replicate a bunch addons/apps purely for use in China?
I don't see why this app is going to get any more exposure to users than it has already and when it was hosted on the author's own repo.
Because in China cannot reliably install add-ons directly from GitHub Container Registry (ghcr.io), Docker Hub (docker.io), and similar services(included ,Home Assistant official Addons), I optimized the add-on sources to use accessible mirror registries instead. If you check the add-on README, you’ll see the related instructions and mirror configurations that allow installations to work successfully in the Chinese network environment.
Everything(repos) is designed with a clear purpose: to make Home Assistant easier to use in China.
Almost Home Assistant end users in China cannot even access the GitHub website itself.
I'm foreigner who lives in China and this helps me also in building connections. Me joining the organization doesn't affect the integration in any way. If you have doubts the code is open source you can check it to your heart's content.
oh ha! no, i was again responding late to a different comment of yours. you asked if anyone had infinite loading issues with the last versions, but i haven't had those issues. i will try quote-reply in the future.
alright no worries. The UI is not very clear what messages is referring to what.
I noticed an "odd" behaviour, and i wonder if it's intentional or not:
a template sensor: if i add one line after "state: >" then code is colored accordingly, but if i don't then code is of the same color.
Pic:
I'll implement a fix on next release. Could you share the code snippet for testing please.
Great, thanks!
I noticed this pretty much on all of my template sensors, NOTE that in the empty line after "state" a tab or at least one space must exist! If there's only an empty line then coloring remains single. (you can see that tab in pic above).
Code from above pic is here ( it's binary sensor template)
- name: odvoz_smeti_soba
state: >
{{(is_state('sensor.rumena_kanta', '1')
or is_state('sensor.rjava_kanta', '1')
or is_state('sensor.crna_kanta', '1'))}}
- name: odvoz_smeti_soba2
state: >
{{(is_state('sensor.rumena_kanta', '1')
or is_state('sensor.rjava_kanta', '1')
or is_state('sensor.crna_kanta', '1'))}}
EDIT: interesting... one space: colored code. Tab (two spaces) also, but three and more spaces: single colored. Also on 5 or mode spaces a red error icon appears. This pic shows error with 5 spaces just below "state: >"
Alright I'll take a look and solve it
1 Like
There error is normal behavior because it is considered incorrect indentation. Even i vscode it is flagged as an errot. I've fixed the highlighting and it will be availbale in the next release.
1 Like
Great, thanks!
None of these "errors" are not big ones, i just found them quite randomly and thought "perhaps i should report"...
