Adapter for Gree and C&H conditioners

[Wildbill]

@serhiy-krasovskyy Installed via NPM, put in ip of a Proklima aircon and it worked OOTB. Seeing all the stuff I also see in FHEM, which I use for some things, iobroker can't handle (like this aircon until right now).

Good job and thanks.

[mcm1957]

@wildbill said in Adapter for Gree and C&H conditioners:

@serhiy-krasovskyy Installed via NPM

Just to ensure that info reaches users: adapter is available at latest repository

[Wildbill]

@mcm1957 Today noon, at the time I installed it, I changed repo from stable to beta(Latest) searched for "gree" but didn't find anything. Even not after manually refreshing. So I decided to click on the "cat", selected NPM and looked for gree and BINGO.
Perhaps I was a little impatient and too early.

[Homoran]

@wildbill sagte in Adapter for Gree and C&H conditioners:

didn't find anything. Even not after manually refreshing

@mcm1957
to be honest, I think the 23 days in latest, according to your screeshot, is not possible

[mcm1957]

@homoran said in Adapter for Gree and C&H conditioners:

@wildbill sagte in Adapter for Gree and C&H conditioners:

didn't find anything. Even not after manually refreshing

@mcm1957
to be honest, I think the 23 days in latest, according to your screeshot, is not possible

Yes, but thats something to report to Bluefox / Statisticscalculation
I think the time is taken from npm package creation date as I do not know that the date a revison is inserted into repository json is stored anywhere.

Main goal was to show that the adapter IS available at latest and an direct installtion is not required (althogh tester normally know what they are doing and thus its ok to directly install from npm or github for them

[mcm1957]

@wildbill said in Adapter for Gree and C&H conditioners:

@mcm1957 Today noon, at the time I installed it, I changed repo from stable to beta(Latest) searched for "gree" but didn't find anything. Even not after manually refreshing. So I decided to click on the "cat", selected NPM and looked for gree and BINGO.
Perhaps I was a little impatient and too early.

Well, most likely you did not press "Search for updates" Button after changing repos. That's a know issue (in my oppinion) that changing repositories does not include a refresh of the data.

https://github.com/ioBroker/ioBroker.admin/issues/2420

But it's ok for testers to do direct installations - I did not want to critize you in any way.

EDIT:
Just read that you did a refresh.
Interesting - no idea what happend.

NOW it is available - at least at my system

Well, don't think its worth further examination.

mcm1957 created this issue in ioBroker/ioBroker.admin

open [bug]: Repositories are not refreshed after switching repository source #2420

[Wildbill]

@mcm1957 sagte in Adapter for Gree and C&H conditioners:

@wildbill said in Adapter for Gree and C&H conditioners:

@mcm1957 Today noon, at the time I installed it, I changed repo from stable to beta(Latest) searched for "gree" but didn't find anything. Even not after manually refreshing. So I decided to click on the "cat", selected NPM and looked for gree and BINGO.
Perhaps I was a little impatient and too early.

Well, most likely you did not press "Search for updates" Button after changing repos. That's a know issue (in my oppinion) that changing repositories does not include a refresh of the data.

Well, as I wrote, I changed to beta, did a manual refreshing (hitting the button you mentioned) but there was no gree adapter visible. So I decided to go the "npm way".

https://github.com/ioBroker/ioBroker.admin/issues/2420

But it's ok for testers to do direct installations - I did not want to critize you in any way.

I normally am no tester and use stable for all adapters, where it is possible. But I also have no problem to use some versions out of the beta repo or npm, even this is my productive system. Thanks to Proxmox and the snapshot and backup functions I have no problem to go back, if something gets broken. Also, I'm relatively confirm with Linux and know what to do, if something won't work as expected.

But yes, normally I also would suggest not to use Github or NPM versions in a productive system (beside you know what you are doing). So no risk, no fun.

• I did not want to critize you in any way.

I didn't take it that way either. Everything is fine.

EDIT: To get fully ONTOPIC:
@Serhiy-Krasovskyy I did some tests and all worked as expected. Even changed some values via FHEM and after the polling time the values changed in iobroker as well and vice versa.

I got exactly one error in the log since I installed an that was not during some of my tests. I don't know what happend. In FHEM log I got no messages but I even don't know if there get all those things logged.
Since then, no more messages, just a working adapter.

gree-hvac.0
2024-05-24 12:42:43.401	info	Device 502xxxxxx2e9 is responding again

gree-hvac.0
2024-05-24 12:42:33.366	error	Error in getDeviceStatus for device 502xxxxxx2e9: Error: Request to 192.168.100.101:7000 timed out

[Serhiy Krasovskyy]

@wildbill device can't respond by many reasons, for example, my devices stops responding if they don't have internet access.

[Wildbill]

@serhiy-krasovskyy Since this one no more errors in log until now. I‘ll keep an eye on it, maybe I can find a reason. Nevertheless, adapter is working as expected. Thanks.

[Wildbill]

@Serhiy-Krasovskyy Just a few more errors today, but beside of that, all working fine.
I set the interval to 20000, maybe this „filters“ some of the moments, the device isn‘t reachable.

gree-hvac.0
2024-05-25 10:09:07.227	error	Error in getDeviceStatus for device 502xxxxx52e9: Error: Request to 192.168.100.101:7000 timed out

gree-hvac.0
2024-05-25 03:29:52.324	error	Error in getDeviceStatus for device 502xxxxx52e9: Error: Request to 192.168.100.101:7000 timed out

gree-hvac.0
2024-05-25 01:48:15.175	error	Error in getDeviceStatus for device 502xxxxx52e9: Error: Request to 192.168.100.101:7000 timed out

gree-hvac.0
2024-05-25 00:40:12.990	error	Error in getDeviceStatus for device 502xxxxx52e9: Error: Request to 192.168.100.101:7000 timed out

[Serhiy Krasovskyy]

@wildbill Actually this error is not critical if occurred occasionally. Just informs that didn't receive data in current iteration. For my devices I set request timeout to 5000.

[Pixelsolution]

@serhiy-krasovskyy I ve installed a "U-Match gud50t1" when i am writing to the adapter i always receive time out messages "Error in onStateChange for state gree-hvac.0.c039375c96a6.power: Error: Request to 192.168.x.xxx timed out" any ideas?

[Pixelsolution]

@pixelsolution Oh - noticed U-Match isn't supported?