Just a question about a few unavailable functions

[jm314159]

I noticed that some functions, among others:

• screenDisplayStatus
• silentSleepStatus
• night_mode

are unavailable in Home Assistant from some time. Is it related to the main case? I truly regret these functions are missing in HE integration.

[jfmfreire]

I have the same issue.

[jm314159]

Yesterday I made some tests and discovered that each of HA Cores 2024.x.y makes those entities unavailable. So, I reverted to 2023.12.4, then deleted Haier hOn integration, restarted the Core once again, added hOn, and, surprisingly, I can operate my favourite entities (functions like, especially, Screen Display and Silent Mode). See my screen.

[animalillo]

i also found this issue, with a bunch of entities not updating and being unavailable, specially that screen display one that i use every night to be able to sleep xD

Those are my HA versions:	Component	Version
Core	2024.2.2
Supervisor	2024.01.1
Operating System	11.5
Frontend	20240207.1

I found this on the logs, which i'm not sure if it's related:

Logger: homeassistant.components.climate
Source: components/climate/__init__.py:354
Integration: Climatización (documentation, issues)
First occurred: 11:20:41 (2 occurrences)
Last logged: 11:20:41

Entity None (<class 'custom_components.hon.climate.HonACClimateEntity'>) implements HVACMode(s): off, auto, cool, dry, heat, fan_only and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/Andre0512/hon/issues

[NoUsername10]

Hello. Great that im not alone (so i haven't messed something up), i have the same issues, screen display (and echo) is a must for sleeping. It's hard to go back to using the remote :-)

Tried to restart, downgrade to v12 but that did not help.

Ver 13.0 hOn integration. Hass:

Enteties error:

I get this warning in the logs, but perhaps this is not related to the functions missing:

[jm314159]

Well, I can only state that after doing some monkey tests I found the (still) working config with:

Core version: 2023.12.4
hOn version: 0.10.0

A core downgrade itself can be done in the ssh terminal with a command:

ha core update --version 2023.12.4

Installing any newer core disables hOn usability in both versions 0.10.0 and 0.13.0.

[NoUsername10]

Well, I can only state that after doing some monkey tests I found the (still) working config with:

Core version: 2023.12.4
hOn version: 0.10.0

I’ve had it working with hOn v12, but I think the latest HASS upgrade caused it for me.

Strange one this.

[InCrustWeTrust]

Same issue for me.

[jm314159]

My current status is so, the latest updates have been installed.

hOn integration - version: 0.12.0 All entities of my interest are available and working fine.

Something's wrong with hOn v13. If the issue and the status are well known, e.g. #147, please someone confirm here to close this case.

[droeloe1818]

Same problem here,

Downgrade to version 12 solved the problem.

@jm314159 I think you can add the label Bug and hope @Andre0512 will take a look into this.

[NoUsername10]

I got it working again.

I downgraded to V12, with HASS core 2024.2.4 it did not help.

I updated to the latest HASS core 2024.2.5 update, hOn works again!

I then tried to update to V13 hOn, that broke the hOn integration.

But, downgrading to V12 with lates HASS core 2024.2.5 is working for me.

[jm314159]

One hint comes to my mind as long as you should have missed it. Upon the integration upgrade/downgrade, remember to remove the whole content of the directory where you used to store the project (/config/customcomponents/hon) including the directory __pycache_\ prior to pasting a new content in there. Then, restart Home Assistant.

[Andre0512]

Hi guys, @VadymMelnychuk fixed it in Andre0512/pyhOn#23 :partying_face: I created a new beta release, please check it out.

[NoUsername10]

Work’s great! Thank you for updating ✌️🙏

[jm314159]

Confirm, after the update to 0.14.0-beta.1 all functions to operate klima are available to me. Really fixed! Thanks, Guys @Andre0512 and @VadymMelnychuk