[RELEASE] Unified Thermostat Driver - MELCloud, MELView, Kumo Cloud and more if you want

Actually I think I know what is happening.

Did you only try this once? If so, can you confirm that your min/max settings on the air conditioner child device are now in Fahrenheit? If so, could you try changing the set temp again?

Otherwise....

Would it be ok for you to setup your devices again? At least removing the child device(s) and hitting refresh on the parent device?

Always best to wait a while for me to respond, I do tend to bounce between a few ideas before landing on one....:slightly_smiling_face:

i tried it many times, I edit the code with new one, and save preference on both. I'll just redo them all together, and test.

1 Like

Readded the device, both apps show F. so thats good. I set 68 and temp, leave it for 5 min stays. I hit refresh auto goes to 87.5.

2021-07-17 08:49:00.509 pm debugadjustSetTemperature: No action taken, either no change in temperature or null temperature provided

dev:10252021-07-17 08:49:00.499 pm debugadjustSetTemperature: Temperature passed in was 87.8 which was parsed as 87.8, current set temperature is 87.8

dev:10252021-07-17 08:49:00.488 pm debugadjustRoomTemperature: updating room temperature from 71.6 to 71.6

dev:10252021-07-17 08:49:00.477 pm debugadjustRoomTemperature: Temperature provided = 71.6, Units = °F, Converted Value = 71.6

dev:10252021-07-17 08:49:00.467 pm debugapplyStatusUpdates: About to adjust temperatures...

dev:10252021-07-17 08:49:00.457 pm debugadjustThermostatOperatingState: Thermostat Mode passed in = 3, Power passed in 1, OperatingState: cooling

dev:10252021-07-17 08:49:00.447 pm debugadjustThermostatMode: Thermostat Mode provided 3, Power provided 1, parsed as Mode Description cool

dev:10252021-07-17 08:49:00.436 pm debugadjustThermostatMode: Adjust Thermostat Mode called

Hmmm, ok, that shouldn't happen. I suspect it is where I am trying to make sure the temperature sits within the limits (min and max) set for the device, but must have it not quite right.

1 Like

It would be useful to see the logs when you try to set the temperature. And exactly how you tried setting the temperature, was in through the device edit screen with the set cooling set point, or through a dashboard tile?

I did both, ill turn on all logs and see

1 Like

Parent always says this.

2021-07-17 09:23:25.610 pm errorjava.lang.NullPointerException: Cannot invoke method toFloat() on null object on line 537 (refresh)

2021-07-17 09:25:00.644 pm debugapplyResponseStatus: Status update complete

dev:10252021-07-17 09:25:00.632 pm debugadjustThermostatFanMode: No change to Fan Speed detected, no action taken

dev:10252021-07-17 09:25:00.623 pm debugadjustThermostatFanMode: No change to Fan Mode detected, no action taken

dev:10252021-07-17 09:25:00.606 pm debugadjustThermostatFanMode: MEL Fan Mode Key 0 parsed as HE Fan Mode Value Auto and HE Fan Speed auto

dev:10252021-07-17 09:25:00.595 pm infoThermostat Set Point adjusted to 87.8 for front Room Mini split - FRONT ROOM

dev:10252021-07-17 09:25:00.577 pm infoCooling Set Point adjusted to 87.8 for front Room Mini split - FRONT ROOM

dev:10252021-07-17 09:25:00.561 pm debugadjustCoolingSetpoint: Current coolingSetpoint 68.0, Current ThermostatSetpoint = 68.0, New coolingSetpoint = 87.8

I did through dashboard, Logs just show me clicking it down and down. refresh back to 87.5

Is there an entry in the log before the one at the bottom of your last post? So before the:

is there a debug log starting with "setCoolingSetpoint: Setting Cooling Set Point to..."

sent you all logs in dm, was too big.

1 Like

Thanks for that. I'll need to take a closer look to try and work out what is happening.

Hopefully the latest update will fix the issues you were seeing @tjc4561. I was not comparing the platform and HE hub temperature scales correctly (I suspect).

In the latest update (1.0.3) I've updated this and added some more logging to the code where you are adjusting the cooling or heating set points. Could you please test once more...

Thanks,
Simon

Did a second update tonight (1.0.4), looking to fix an issue for those in Europe (MELCloud) with units showing as off when they are on, reported by @mikkomattip.

SetPoint seems to work!. however, when i go to the dashboard and click Temp down or up, Logs show it but hit refresh, and Setpoint in parent won't change, stays what I put in originally.

2021-07-19 01:10:33.243 pm debugapplyResponseStatus: Status update complete

dev:10252021-07-19 01:10:33.234 pm debugadjustThermostatFanMode: No change to Fan Speed detected, no action taken

dev:10252021-07-19 01:10:33.222 pm debugadjustThermostatFanMode: No change to Fan Mode detected, no action taken

dev:10252021-07-19 01:10:33.211 pm debugadjustThermostatFanMode: MEL Fan Mode Key 0 parsed as HE Fan Mode Value Auto and HE Fan Speed auto

dev:10252021-07-19 01:10:33.200 pm debugadjustSetTemperature: No action taken, either no change in temperature or null temperature provided

dev:10252021-07-19 01:10:33.189 pm debugadjustSetTemperature: Temperature passed in was 68.0 which was parsed as 68.0, current set temperature is 68.0

dev:10252021-07-19 01:10:33.176 pm debugadjustRoomTemperature: updating room temperature from 71.6 to 71.6

dev:10252021-07-19 01:10:33.165 pm debugadjustRoomTemperature: Temperature provided = 71.6, Units = °F, Converted Value = 71.6

dev:10252021-07-19 01:10:33.154 pm debugapplyStatusUpdates: About to adjust temperatures...

dev:10252021-07-19 01:10:33.143 pm debugadjustThermostatOperatingState: Thermostat Mode passed in = 3, Power passed in 1, OperatingState: cooling

dev:10252021-07-19 01:10:33.131 pm debugadjustThermostatMode: Thermostat Mode provided 3, Power provided 1, parsed as Mode Description cool

dev:10252021-07-19 01:10:33.120 pm debugadjustThermostatMode: Adjust Thermostat Mode called

dev:10252021-07-19 01:10:33.110 pm debugapplyStatusUpdates: About to adjust thermostat mode details...

dev:10252021-07-19 01:10:33.099 pm debugapplyResponseStatus: Status Info: [unitId:9734P0089100041F, power:1, setMode:3, roomTemp:71.6, setTemp:68.0, setFan:0]

dev:10252021-07-19 01:10:33.068 pm debugretrieveStatusInfo_KumoCloud: Status Info - [unitId:9734P0089100041F, power:1, setMode:3, roomTemp:22, setTemp:20, setFan:0]

dev:10252021-07-19 01:10:33.052 pm debugretrieveStatusInfo_KumoCloud: response - [true, null, [[[id:2253801430414576, record_time:2021-07-19T20:09:53.596Z, device_serial:9734P0089100041F, it_status:null, rssi:-51, power:1, operation_mode:3, set_temp:null, set_temp_a:null, fan_speed:0, air_direction:0, prohibit_local_remote_control:null, room_temp:22, room_temp_beyond:null, room_temp_a:null, out_of_use:null, unusual_figures:32768, two_figures_code:A0, status_display:0, actual_fan_speed:null, sp_cool:20, sp_heat:24, sp_auto:-1, raw_frames:null, run_test:0, active_thermistor:null, temp_source:null, seconds_since_contact:38]], [[device_serial:9734P0089100041F, id:2253801268455333, responded_to:null]]]]

dev:10252021-07-19 01:10:32.556 pm debugretrieveStatusInfo: Retrieving status info from KumoCloud

dev:10252021-07-19 01:10:32.533 pm debugrefresh: Refresh process called

dev:10252021-07-19 01:10:25.603 pm debugsetCoolingSetpoint: Setting Cooling Set Point to 66.0, current minimum 60.8, current maximum 87.8

dev:10252021-07-19 01:10:24.319 pm debugsetCoolingSetpoint: Setting Cooling Set Point to 67.0, current minimum 60.8, current maximum 87.8

So not sure if Its actually going to 66, since Setpoint is 68 in device.

Child app Errors.

2021-07-19 01:06:30.093 pm errorjava.lang.ClassCastException: null (setCoolingSetpoint)

dev:10262021-07-19 01:05:51.289 pm errorjava.lang.ClassCastException: null (setCoolingSetpoint)

dev:10262021-07-19 01:04:50.847 pm errorjava.lang.NullPointerException: Cannot invoke method toFloat() on null object on line 538 (refresh)

dev:10262021-07-19 01:04:25.495 pm errorjava.lang.NullPointerException: Cannot invoke method toFloat() on null object on line 538 (refresh)

Thanks for the quick responses! great work.

1 Like

Glad to hear we are a little closer. I'll take a look later today.

Thanks,
Simon

Release 1.0.5 - Fixes for MELCloud Heating, was passing in power = false, should be true

Rolled out fix for European users where heating mode was turning off air conditioning unit. More work to be done on temperature in Europe and the U.S.

@tjc4561 - I need a little more time to sort out the temperature issues, seems to be an issue for both U.S. and European users, though different behaviour according to the logs you and others have reported.

Thanks for your ongoing patience and assistance with testing, along with others of course.

Simon

Release 1.0.6 - Fahrenheit Conversion - moving temp conversion from setCooling / Heating SetPoint to setTemperature method

This release hopefully addresses some of the issues you were seeing @tjc4561. The root of most of these issues has been that I need to keep the temperatures stored and manipulated on the HE hub in the local temperature scale (Fahrenheit for most in the U.S.), but then need to send Celsius when issuing commands. So there may be a couple more situations where this pops up, but hopefully we can sort them out relatively quickly.

From the logs you provided I feel like there are some more gremlins lurking that I will need to sort out, some related to the initial setup of a device in HE, some when handling refreshes of the device state shortly after a command is issued.

Simon

Just on the recent conversations about the temperature change increment (there's an issue with adjusting heating set temperature on a dashboard tile that is being fixed by HE staff), I do eventually plan to read in the settings from MEL/Kumo platform to then use, but want to stabilise the drivers first.

Seems like SetCoolingpoint isn't working now. Let it wait for 3 min Refresh goes back. If I don't hit refresh it stays at setpoint.