Sensor is not Showing Room Temperature #12
Labels
question
Further information is requested
Comments
|
Please restart homebridge in debug mode and send me the debug log. (Mac address is missing. Did you clear it or your configuration file does not have mac addresses set?) |
|
Thank you for the quick reply @eibenp, I did clear the MAC and IPs,. |
|
It seems that the AC unit named office does not have an internal temperature sensor or the sensor is not working. It can be a hardware failure if this type of AC should have a sensor built-in. I saw only a short period of logs. I see that the device has sent value 0 instead of the actual temperature but I do not know if it follows the room temperature or not. Did you check if it shows always -40 Celsius or sometimes is it different? If the value changes with the room temperature but it is incorrect then you can try to fix it with the sensorOffset parameter. The default value is 40 which works well on most units but you can try a different value (e.g. -33). If it is independent from the actual room temperature then the sensor is not working but it sends always the zero value. Can you check what temperature is displayed by different real room temperatures? Is it always -40? |
|
@eibenp Not sure how can I make sure if sensor is working on not, but I tried for example setting fan to auto and it lowered the fan speed after a while so I assume it's working. I have attached more logs(I'm setting temperature offset to -27) the ACs named Office and Living room both are the same type and have the same issue also both are only running for a year. I had a thought that maybe this duct concealed have two sensors and docs seems to confirm this, so maybe the data parsing does only support single sensor but I check the logs and your code it's seems so that is the issue. |
|
Theoretically there is a TEMP button on the remote control. If the AC unit has a built-in temperature sensor then pressing the TEMP button changes the temperature display on the AC unit to the internal measured value for a few seconds. My GREE Pulse unit works in the following way:
So I think, if there is some difference between the desired and real room temperature and the AC unit has a built-in sensor and the sensor is working then you can show the actual real room temperature on the AC unit for a few seconds using the remote control. |
|
I have read the new logs. Can you send me a link to the documentation of your AC? If your device has two sensors and the sensors have different status ids then unfortunately they are unknown for me. I try to guess the ids. I have published a new beta version (2.1.0-beta.3) which tries to query some guessed sensor ids. If you install this beta version and send the debug logs back to me I can check if we have success and we can query the sensor or not. |
|
@eibenp I check my wired controller manual and it mentions the below which can be used to get current temp, I tried it and it showed 28(while target temp is 23): New logs using Unfortunately, I couldn't check AC exact model as it's on the roof and I don't have access to it right now, I will be able to check it tomorrow. |
|
No luck at the moment. My guessed sensor ids are not valid. The AC unit did not sent a valid temperature value back to homebridge. Until we do not find the sensor id it is not possible to query the measured value from your device. |
|
I have searched for this problem. Some others had also the same problem. They said that this is a firmware problem because some firmware versions do not report the correct measured temperature value over Wifi. Old firmware versions did not report it at all. Newer versions report it with +40 offset. And there are some versions which report a fixed value instead of the measured one. Typical is the zero value but I found somebody who gets a fixed 218 from the AC unit. The only solution I found is the firmware upgrade or downgrade (if there is no newer version available). Unfortunately the official GREE+ mobile app do not support current room temperature display so it is not possible to capture the network traffic to reverse engineer this information type. |
|
@eibenp using target room temp as current is fine, about firmware update mine is 1.2 and it mentions that there is no new update, but U fount this where I might be able to update to newer versions, but I also saw another issue for you which you mentioned that the network protocol has changed and I'm afraid it will break it more, also any idea about how to downgrade if I managed to upgrade and it broke. Thank you for your support 🙏 |
|
Sorry. I do not know how to downgrade the firmware. I have never done so. Currently I am working on the new network protocol. It will be available soon. |
|
Great looking forward to that 🙏, I see a new beta version 4 does that sets the target temp as current temp? |
|
Yes, the latest beta version sets the target temp as current if device reports a fixed zero value like yours. Did you try it? |
|
@eibenp sorry I was a bit busy and I didn't test it, I don't see the new beta version anymore |
|
No problem. v2.1.0 final version has been published. You can use it. It contains the temperature modification and also the new v2 network protocol2024. jún. 24. dátummal, 18:47 időpontban Mohammad Alhomaid ***@***.***> írta:
@eibenp sorry I was a bit busy and I didn't test it, I don't see the new beta version anymore
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Issue solved with workaround solution implemented in v2.1.0 : Display target temperature as current if device reports a fixed zero value instead of the measured one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe Your Problem:
I tried adding two types of Gree air conditioners, the split one works fine and but the duct(central) works fine except that Homekit doesn't read current room temperature.
In the logs you can see
Officeas the duct which doesn't read the temperature andBedroomis the split which reads it fine.Logs:
Plugin Config:
{ "name": "GREE Air Conditioner", "port": 7002, "scanAddress": "", "scanCount": 10, "scanTimeout": 3, "devices": [ { "mac": "", "name": "Dressing room", "model": "10001-v16.2", "speedSteps": 5, "statusUpdateInterval": 10, "sensorOffset": 40, "minimumTargetTemperature": 16, "maximumTargetTemperature": 30, "xFanEnabled": false, "temperatureSensor": "disabled", "overrideDefaultVerticalSwing": 0, "defaultVerticalSwing": 0 }, { "mac": "", "name": "Living Room", "model": "3019-v1.7", "speedSteps": 5, "statusUpdateInterval": 10, "sensorOffset": 40, "minimumTargetTemperature": 16, "maximumTargetTemperature": 30, "xFanEnabled": false, "temperatureSensor": "disabled", "disabled": false, "overrideDefaultVerticalSwing": 0, "defaultVerticalSwing": 0 }, { "mac": "", "name": "Office", "model": "3019-v1.7", "speedSteps": 5, "statusUpdateInterval": 10, "sensorOffset": 40, "minimumTargetTemperature": 16, "maximumTargetTemperature": 30, "xFanEnabled": false, "temperatureSensor": "disabled", "overrideDefaultVerticalSwing": 0, "defaultVerticalSwing": 0 }, { "mac": "", "name": "Bedroom", "model": "10001-v16.2", "speedSteps": 5, "statusUpdateInterval": 10, "sensorOffset": 40, "minimumTargetTemperature": 16, "maximumTargetTemperature": 30, "xFanEnabled": false, "temperatureSensor": "disabled", "overrideDefaultVerticalSwing": 0, "defaultVerticalSwing": 0 } ], "platform": "GREEAirConditioner" }Screenshots:
The first one is the
Officewhich doesn't read the temperature and shows-40and the second reads it fine and shows33.Environment:
The text was updated successfully, but these errors were encountered: