I have another problem, when I install climate_ip with HACS it seems there is a background process that implements a loop with a responsiveness delay, I mean, if I switch on and switch off a light through HA I can do it in a very responsive way during 8-10 seconds and after that time it does not repond during 5 seconds. Any similar behaviour? How to fix/debug it?
I’m keep getting the:
2019-12-16 01:10:43 ERROR (SyncWorker_9) [homeassistant.util.yaml.loader] while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 18, column 1
2019-12-16 01:10:43 ERROR (MainThread) [homeassistant.components.homeassistant] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 18, column 1
2019-12-16 01:12:49 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 12, column 1
2019-12-16 01:12:49 ERROR (MainThread) [homeassistant.components.homeassistant] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/configuration.yaml”, line 3, column 1
expected , but found ‘-’
in “/config/configuration.yaml”, line 12, column 1
I also had to work with the CPURAM post regarding:
near line 25, remove “ATTR_HVAC_ACTIONS” and its preceding comma
near line 251, commnet/delete the below 3 lines
@property
def hvac_action(self):
return self.rac.get_property(ATTR_HVAC_ACTIONS)
re-start HA
Guys, I’m really sorry but at this moment I have no free time for this component. There is a lot of private stuff in my live to organize.
Additionally I’m not using HA anymore. Support for Z-Wave is very poor so I decided to stop using it. I’m not sure if I will come back to HA later or move to something else.
@wifi75 You need to call service climate_ip_set_property on you entity with dedicated params, eg:
@SebuZet, thanks again, and understand you have moved on from this. Are you open to receiving pull requests to fix issues that crop up with the climate_ip component over time? Or would you prefer someone to just fork your repository?
I was trying to use sebuzet’s custom integration for Samsung AC, and had a hard time with it: my HA slowed to a crawl, with updates taking 5-10 seconds.
Would take me too long to learn enough HA infrastructure to debug it, and with it unsupported at the moment, I wrote my own, this time it’s a small Go bridge that runs in a separate process and connects to HA through MQTT. Seems to work.
Very pleased with this component. I have two Samsung A/C units both the older generation on port 2878. Getting the token was easy once I found out about the Homebridge method.
I was eventually going to purchase another two Sensibo Sky units (I already have one) to control the two Samsungs and a Fujitsu AC. I can now use the existing Sensibo for the Fujitsu, so this component has just saved me about $318 AUD!
is it working fine for you? i got it to work even send/receive commands, but Current temperature displayed on HA is showing on F* (instead of C*), all other temps are fine on C*.
Im trying to create an automation to turn on the heat for when the current_temperature drops below a value, but I’m not finding a way to read the value for the trigger, or to add it as a condition.
Hi, after HomeAssistant 109 update, I have this issues on Climate_IP:
Please how can i solve it?
Thanks.
Dettagli registro (WARNING)
Logger: homeassistant.util.async_
Source: util/async_.py:120
First occurred: 11:02:22 (1068 occurrences)
Last logged: 16:16:11
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for climate_ip doing I/O at custom_components/climate_ip/connection_request.py, line 89: resp = session.request(**self._params)
Dettagli registro (ERROR)
Logger: custom_components.climate_ip.climate
Source: custom_components/climate_ip/connection_request.py:123
Integration: climate_ip (documentation)
First occurred: 11:05:47 (106 occurrences)
Last logged: 16:15:12