search

sinseman44 / koolnova-BMS-Integration

Koolnova air conditioning support for Home Assistant via BMS
MIT License
6 stars 2 forks source link

Doesn’t work anymore #6

Open Lk1975 opened 1 month ago

Lk1975 commented 1 month ago

It was working fine before vacation, I left the ac turned off during vacation, and now I am back and it’s not working anymore. I tried to delete the device and add it again, it sees it, but it’s doesn’t takes any command. In the log i found this: Logger: custom_components.koolnova_bms.coordinator Source: helpers/update_coordinator.py:312 integration: Koolnova BMS Modbus RS485 (documentation, issues) First occurred: 12:48:53 AM (14 occurrences) Last logged: 12:55:23 AM

Unexpected error fetching koolnova_bms data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 268, in _async_update_data return await self.update_method() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 408, in async_update_all_areas self._areas[_idx].order_temp = v['order_temp'] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 126, in order_temp raise OrderTempError('Order temp value must be between {} and {}'.format(const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER)) custom_components.koolnova_bms.koolnova.device.OrderTempError: Order temp value must be between 15.0 and 35.0

what can I check? Thanks!

sinseman44 commented 1 month ago

Hello, Can you indicate the version of the integration installed in your home assistant ?

sinseman44 commented 1 month ago

Can you try a code modification to better understand the problem? In the file /config/custom_components/koolnova_bms/koolnova/device.py, line 126. replace the line by raise OrderTempError('Order temp value ({}) must be between {} and {}'.format(val, const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER)) I would like to know which temperature is measured by the system.

After the modification, restart your home assistant and give me the error log, please.

Lk1975 commented 1 month ago

Ciao!

The integration version is 0.1.0

I've modified the file, but stil it doesn't work. when I try to turn on a room, it doesn't do anything. here is a screenshot. I have 1 room that I don't know what it is for, but it's always been like this, and shows also in the koolnova app. [image: image.png]

[image: image.png] those are the logs:

Logger: custom_components.koolnova_bms.coordinator Source: helpers/update_coordinator.py:312 integration: Koolnova BMS Modbus RS485 (documentation https://github.com/sinseman44/koolnova-BMS-Integration, issues https://github.com/sinseman44/koolnova-BMS-Integration/issues) First occurred: 10:02:50 AM (43 occurrences) Last logged: 10:23:50 AM Unexpected error fetching koolnova_bms data

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 268, in _async_update_data return await self.update_method() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 408, in async_update_all_areas self._areas[_idx].order_temp = v['order_temp'] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 126, in order_temp raise OrderTempError('Order temp value ({}) must be between {} and {}'.format(val, const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER)) custom_components.koolnova_bms.koolnova.device.OrderTempError: Order temp value (0.0) must be between 15.0 and 35.0

thanks a lot.

Il giorno lun 5 ago 2024 alle ore 09:08 sinseman44 @.***> ha scritto:

Can you try a code modification to better understand the problem? In the file /config/custom_components/koolnova_bms/koolnova/device.py, line 126. replace the line by raise OrderTempError('Order temp value ({}) must be between {} and {}'.format(val, const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER)) I would like to know which temperature is measured by the system.

After the modification, restart your home assistant and give me the error log, please.

— Reply to this email directly, view it on GitHub https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268331981, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCTQICHBBOIJ7QK3WGNQTGLZP4QHHAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGMZTCOJYGE . You are receiving this because you authored the thread.Message ID: @.***>

sinseman44 commented 1 month ago

Ok, first thing, can you update the koolnova integration with the latest version (0.1.3) ? and retry ? To explain the error, when the koolnova integration starts (example: after restart of Home Assistant), if one parameter can't be retreive from RS485 comm, the koolnova integration stops and can't be controlled anyway. Here, your integration can't retreive area temperature value. why ? (don't know for the moment) How many areas did you configured on the integration ? The area radio thermostat have enough battery ?

Lk1975 commented 1 month ago

Hi,

I've updated to 0.1.3 but it still doesn't work. Physically I have 4 rooms, but I don't know why the system shows me 5 rooms, and the one that I don't know is with temp at 0 degree. I have 4 wired thermostat..

here are the last logs:

2024-08-05 10:48:33.027 ERROR (MainThread) [custom_components.koolnova_bms.coordinator] Unexpected error fetching koolnova_bms data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 268, in _async_update_data return await self.update_method() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 408, in async_update_all_areas self._areas[_idx].order_temp = v['order_temp'] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/koolnova_bms/koolnova/device.py", line 126, in order_temp raise OrderTempError('Order temp value must be between {} and {}'.format(const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER)) custom_components.koolnova_bms.koolnova.device.OrderTempError: Order temp value must be between 15.0 and 35.0 2024-08-05 10:48:33.029 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 255, in _handle_refresh_interval await self._async_refresh(log_failures=True, scheduled=True) File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 411, in _async_refresh self.async_update_listeners() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 165, in async_update_listeners update_callback() File "/config/custom_components/koolnova_bms/sensor.py", line 149, in _handle_coordinator_update for _cur_engine in self.coordinator.data['engines']:


TypeError: 'NoneType' object is not subscriptable
2024-08-05 10:49:03.025 ERROR (MainThread)
[custom_components.koolnova_bms.coordinator] Unexpected error fetching
koolnova_bms data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py",
line 312, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py",
line 268, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/koolnova_bms/koolnova/device.py", line 408,
in async_update_all_areas
self._areas[_idx].order_temp = v['order_temp']
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/koolnova_bms/koolnova/device.py", line 126,
in order_temp
raise OrderTempError('Order temp value must be between {} and
{}'.format(const.MIN_TEMP_ORDER, const.MAX_TEMP_ORDER))
custom_components.koolnova_bms.koolnova.device.OrderTempError: Order temp
value must be between 15.0 and 35.0

Il giorno lun 5 ago 2024 alle ore 10:42 sinseman44 ***@***.***>
ha scritto:

> Ok, first thing, can you update the koolnova integration with the latest
> version (0.1.3) ? and retry ?
> To explain the error, when the koolnova integration starts (example: after
> restart of Home Assistant), if one parameter can't be retreive from RS485
> comm, the koolnova integration stops and can't be controlled anyway.
> Here, your integration can't retreive area temperature value. why ? (don't
> know for the moment)
> How many areas did you configured on the integration ? The area radio
> thermostat have enough battery ?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268501783>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BCTQICD7LG3VNYBIJSUHQOTZP43ILAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGUYDCNZYGM>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
sinseman44 commented 1 month ago

OK, start of the problem, why 5 areas configured and only 4 real rooms (wired thermostat) ? can you retry the configuration and give me a screenshot of each step of the koolnova integration configuration ?

Lk1975 commented 1 month ago

I don't know why, but there were always 5 rooms....

if you want I can let you connect using teamviewer

Il giorno lun 5 ago 2024 alle ore 11:00 sinseman44 @.***> ha scritto:

OK, start of the problem, why 5 areas configured and only 4 real rooms (wired thermostat) ? can you retry the configuration and give me a screenshot of each step of the koolnova integration configuration ?

— Reply to this email directly, view it on GitHub https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268539142, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCTQICBXDBQKWSO2ZICRJITZP45KVAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGUZTSMJUGI . You are receiving this because you authored the thread.Message ID: @.***>

sinseman44 commented 1 month ago

if you want I can let you connect using teamviewer

Sorry, i can't, i'm at work and can't use teamviewer. In the fourth area configuration page, did you unchecked the box "add new area" ? I checked my configuration, i have 3 radio thermostat and only 3 areas configured in my home assistant.

Lk1975 commented 1 month ago

Ok, no problem. it's been always like this, and it was working before. the only thing I've done is to keep the ac off for 3 weeks. the unknown area is the second, so I can't avoid including in the devices. I've tried to disable it but it doesn't make any difference. I don't think that is the issue. what else could I check?

Il giorno lun 5 ago 2024 alle ore 11:29 sinseman44 @.***> ha scritto:

if you want I can let you connect using teamviewer

Sorry, i can't, i'm at work and can't use teamviewer. In the fourth area configuration page, did you unchecked the box "add new area" ? I checked my configuration, i have 3 radio thermostat and only 3 areas configured in my home assistant.

— Reply to this email directly, view it on GitHub https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268607914, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCTQICBOIPPOEXNLKE3DJV3ZP5AXZAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGYYDOOJRGQ . You are receiving this because you authored the thread.Message ID: @.***>

sinseman44 commented 1 month ago

I try to understand your configuration steps flow....

In the area step flow.

  1. Configuration of the first area => You write a new name of the area ? you let the area id at 1 ? you check the box for new area and click on the validate button ?
  2. Configuration of the second area => You write a new name of the area ? you let the area id at 2 ? you check the box for new area and click on the validate button ?
  3. Configuration of the third area => You write a new name of the area ? you let the area id at 3 ? you check the box for new area and click on the validate button ?
  4. Configuration of the last area => You write a new name of the area ? you let the area id at 4 ? you uncheck the box for new area and click on the validate button ?

that's right ? or correct the flow.

Lk1975 commented 1 month ago

Ok,

I've talked with the installer, and they have remotely removed the unknown zone. Now I've removed and reinstalled the integration, reconfigured all the areas, skipping the one that has been removed. So area 1 id 1, area 2 id 3, area 3 id 4 and area 4 id 5. Now it is working and I have no errors in the log, so maybe it was that zone. What it would be nice, is when you configure it It ask you for the name of the device and for the names of the areas. After it add anyway the word "area" at the end of the name and the id. the name of the global hvac it put twice the name of the device: switch.condizionatore_condizionatore_global_hvac_state, where condizionatore is the name of the device that I've choosed.

thanks a lot for your help!

Il giorno lun 5 ago 2024 alle ore 12:06 sinseman44 @.***> ha scritto:

I try to understand your configuration steps flow....

In the area step flow.

  1. Configuration of the first area => You write a new name of the area ? you let the area id at 1 ? you check the box for new area and click on the validate button ?
  2. Configuration of the second area => You write a new name of the area ? you let the area id at 2 ? you check the box for new area and click on the validate button ?
  3. Configuration of the third area => You write a new name of the area ? you let the area id at 3 ? you check the box for new area and click on the validate button ?
  4. Configuration of the last area => You write a new name of the area ? you let the area id at 4 ? you uncheck the box for new area and click on the validate button ?

that's right ? or correct the flow.

— Reply to this email directly, view it on GitHub https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268693416, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCTQICAS55Y53AMMHCDZS73ZP5FBFAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGY4TGNBRGY . You are receiving this because you authored the thread.Message ID: @.***>

Lk1975 commented 1 month ago

Another question. I've just installed, and it says version 0.1.0, is it normal?

Also, trying to change the ventilation speed, it reports this error: Failed to call service select/select_option. cannot unpack non-iterable bool object [image: image.png]

Il giorno lun 5 ago 2024 alle ore 13:46 Luca Scotti < @.***> ha scritto:

Ok,

I've talked with the installer, and they have remotely removed the unknown zone. Now I've removed and reinstalled the integration, reconfigured all the areas, skipping the one that has been removed. So area 1 id 1, area 2 id 3, area 3 id 4 and area 4 id 5. Now it is working and I have no errors in the log, so maybe it was that zone. What it would be nice, is when you configure it It ask you for the name of the device and for the names of the areas. After it add anyway the word "area" at the end of the name and the id. the name of the global hvac it put twice the name of the device: switch.condizionatore_condizionatore_global_hvac_state, where condizionatore is the name of the device that I've choosed.

thanks a lot for your help!

Il giorno lun 5 ago 2024 alle ore 12:06 sinseman44 < @.***> ha scritto:

I try to understand your configuration steps flow....

In the area step flow.

  1. Configuration of the first area => You write a new name of the area ? you let the area id at 1 ? you check the box for new area and click on the validate button ?
  2. Configuration of the second area => You write a new name of the area ? you let the area id at 2 ? you check the box for new area and click on the validate button ?
  3. Configuration of the third area => You write a new name of the area ? you let the area id at 3 ? you check the box for new area and click on the validate button ?
  4. Configuration of the last area => You write a new name of the area ? you let the area id at 4 ? you uncheck the box for new area and click on the validate button ?

that's right ? or correct the flow.

— Reply to this email directly, view it on GitHub https://github.com/sinseman44/koolnova-BMS-Integration/issues/6#issuecomment-2268693416, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCTQICAS55Y53AMMHCDZS73ZP5FBFAVCNFSM6AAAAABL7G2ZVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGY4TGNBRGY . You are receiving this because you authored the thread.Message ID: @.***>

sinseman44 commented 1 month ago

Ok, I've talked with the installer, and they have remotely removed the unknown zone. Now I've removed and reinstalled the integration, reconfigured all the areas, skipping the one that has been removed. So area 1 id 1, area 2 id 3, area 3 id 4 and area 4 id 5. Now it is working and I have no errors in the log, so maybe it was that zone. >

Great ! I'm pretty sure the deleted area caused the log error !

What it would be nice, is when you configure it It ask you for the name of the device and for the names of the areas. After it add anyway the word "area" at the end of the name and the id. the name of the global hvac it put twice the name of the device: switch.condizionatore_condizionatore_global_hvac_state, where condizionatore is the name of the device that I've choosed. thanks a lot for your help!>

I noticed that too and I will work on it.

sinseman44 commented 1 month ago

Another question. I've just installed, and it says version 0.1.0, is it normal?

It's a bug, I forgot to change the version number in the file manifest.json when i published the release.

Also, trying to change the ventilation speed, it reports this error: Failed to call service select/select_option. cannot unpack non-iterable bool object

I can't view your screenshot on github. Can you tell me more about this bug and what are the actions before noticed this error ?