Error : indisponible since the new version #29
Comments
|
@jeo25550 its still working here with intesishome local and airconwithme cloud connections. Is this since you did an update? What version are you on and what kind of device / connection did you configure? |
|
@srkoster Hello, i use version 1.1.1 of intesishome on HA. my device is an heater pump panasonic Aquarea with tank . I have create rest sensor , they always run. I send you a part of the response of a postman request. Hope that can help. "devices": [ |
|
Sounds like you're using the cloud control and not a local connection to the device. I've had issue with my cloud connection due to a change in the referenced python package Could you try to manually revert back to |
|
@srkoster I change my manifest like that : I have always unknow message on the compoment , but now i can change the mode . But there is only 1 mode heater (and stop) No tank and tank+heater
|
|
Okay, that's a start then :) Could you post the rest of the response of your Postman call? You've posted the "config" bit which is used to created the entities in Home Assistant. The "status" bit contains both the real values like temperature (which is used to populate the actual values) but also available options (which is used to create the option lists like mode) |
|
@srkoster |
|
Here the correspondance between UID and function. <style type="text/css"></style> UID | | 1 | 10 | 14 | 15 | 34 | 37 | 38 | 39 | 42 | 43 | 44 | 45 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 65 | 66 | 69 | 75 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 107 | | | | | | | | | | | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 142 | 144 | 50000 -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- Date | Ordre CH | power | Tp int | alarm stat | error code | silencieux | Tp ext | Tp eau aller | Tp eau retour | 2=powerfull CH 1=eco | ECS ONOFF | Mode ECS | Tp ECS | décalage eco CH | thermoshift cool eco | décalage power CH | thermoshift cool full | décalage ECS eco | décalage ECS Power | error reset | décalage courbe eau | cool water setpoint temperature | consigne ECS | oper mode 3 tank 2 H+T | Config Quiet | comfirm off | conso total | CONFIG_OPERATING_MODE | conso ECS | conso froid | conso CH | HIeau | heating off temperature | | | | heater setpoint temperature | | | Consigne temp eau | | booster ? | booster delay | heat interval 1 = 30, 2 = 1h | | | | | | | | | Booster tank en marche | Top defrost | heure working | | | | | | | | | | | H2O HI | | | | | ext_thermo_control 170=on | tank_present 170 = on | solar off | | | | | | | | | | | heat low outdoor set temperature | heat high outdoor set temperature | heat_low_water_set_temperature | | error_code | external_led |
|
Thanks, that looks good. I think the issue is with the Home Assistant integration which might not map all mode returned by the API and the python package to a mode in the climate entity. Could you make sure that you have earning logging enabled in your HA Or enable debug logging on the custom component from the integration UI screen. Then check your HA logs for messages with |
|
here the log: NO Unexpected mode find! 2025-01-19 20:20:41.585 DEBUG (MainThread) [pyintesishome] Received: {"command":"status","data":{"rssi":194,"deviceId":127927475490,"uid":82,"value":164635}} 2025-01-20 02:53:27.347 ERROR (MainThread) [homeassistant.components.rest.data] Timeout while fetching data: https://user.intesishome.com/api.php/get/control?username=xxxxxx&password=xxxxxx&cmd={"status":{"hash":"x"}}&version=2.8.5 2025-01-20 11:46:05.709 DEBUG (MainThread) [pyintesishome] Received: {"command":"rssi","data":{"deviceId":127927475490,"value":195}} |
|
Did you reload the integration after enabling the debug log? That's the moment when the list is populated. |
|
Sorry, i haven't reload. now i have Unexpected mode 2 time. 2025-01-20 13:27:12.703 DEBUG (MainThread) [pyintesishome] Received: {"command":"status","data":{"rssi":190,"deviceId":127927475490,"uid":69,"value":194971}} |
|
Good, that matches the expectation. Quick check, you don't have a cooling option on the device? Just heating? |
|
|
|
I take that as a no. So even though everything is exposed by the API and processed by the python package The quickest fix would be to change this part so that the However, you won't be able to change the status of the tank through the climate entity as Home Assistant only allows predefined modes and |
|
Heater+Tank and Tank modes appeared in the HA interface under Dry and Fan_Only in previous versions which was fine for me |
|
Do you mean that you could press "Mode" in the climate UI in Home Assistant and you saw: "Off, Heat, Dry, Fan_Only, Heat+Tank, Tank"? Or did you mean you'd have "Off, Heat, Dry, Fan_Only" and pressing "Dry" would put the device in "Heat+Tank" mode? |
|
Before when I press MODE I have OFF,heat, Fan only, dry if i choosed Dry I have heater+tank in real action. now i have only OFF and heater. If I use action Set HVAC mode to dry, nothing happens |
|
I can't find anything in the code that would explain the previous behavior. What version was it? You could implement that logic by changing this part into this: It won't make it back into the integration itself as it would break the integration for devices that do have a dry or fan option. |
|
Ok, i had mad some test. it's ok only with this : Thanks !! |
|
I am having the same issue, but with a Mitsubishi reverse cycle air-conditioner the logs are nearly the same but as there is no tank I don't see that error. After a restart I get almost the same response as jeo25550 posted 3 weeks ago. The last few lines of my log are: 2025-02-08 09:16:28.085 DEBUG (MainThread) [pyintesishome] Opening connection to IntesisHome API at 212.92.41.143:5210 The climate.air_con entity shows as unavailable but for the instant I restart I do get the values from the cloud. Then always every 4 minutes I get the following 3 lines in the LOG: 2025-02-08 09:20:33.474 DEBUG (MainThread) [pyintesishome] sending keepalive to {self._device_type} |
|
@dhilbig did you try downgrading the PyIntesishome dependency? See #29 (comment) |
|
@srkoster have now and it is working. |
L'intégration ne fonctionne plus depuis quelques jour (Maj ?) Message indisponible.
2025-01-14 09:47:19.433 DEBUG (MainThread) [pyintesishome] Sending command {"command":"get","data":{"deviceId":127927475490,"uid":10}}
2025-01-14 09:47:19.433 ERROR (MainThread) [pyintesishome] <class 'ConnectionResetError'> Exception. ('Connection lost',) / Connection lost
The text was updated successfully, but these errors were encountered: