That was totally it. After that I got an error because I tried adding a NAME field to the integration in the CONFIGURATION.YAML file. Once I got rid of that, a quick reboot and the integration was recognized!
Hi Phil,
Wondering if you have given more thoughts to extending this PR, Iām sure there are others among this community that would be happy to test any code revisions and help where possible
My units support ambient and 0.5deg target temp. On my side Iāve modified the climate.py to display ambient and have set 0.5deg target temp however I realise this isnāt supportable by every unit therefore much more development would be needed.
cheers Simon
Hi All,
Thanks for this fantastic component - its been working on my Split system for a number of weeks - and today I added the following code into āclimate.pyā to get the room temperature:
@property
def current_temperature(self):
cur_temp = self._fujitsu_device._get_prop_from_json('display_temperature', self._fujitsu_device._properties)
return round((cur_temp['value'] / 100 - 32) * 5/9, 1)
This worked perfectly, as when I rebooted home assistant I can see the room temperature showing on my thermostat cardā¦
However, this temperature hasnāt been updated since I started Home Assistant - is there any way to get the temperature to update at a certain interval, as I can currently only get it to update if I turn the air con either on or off?
Thanks
Leacho
Just as an FYI, API is a bit wonky with special chars in password. Login works fine on app and website, but fails via api post.
Hello,
i loved this integration, but it stopped working. This seems to be the problem:
does somebody know how to solve it?
Same thing hereā¦ After some hours, the plugin doesnāt want to start the AC anymore, and I have to use FGLair insteadā¦
sorry for the noob question but is there a trick to actually see the integration once ive followed all of this thread and ensured all the files are in the correct place and up to date?
Ive added a version number in the manifest too and that error is now no longer present in the logs. Just a 'integration hasnt been tested ā warning and my config yaml is preventing me from restarting the server due to āno fujitsu_general_heatpump integration foundā so i comment the credentials out temporarily so that I can restart the server.
Im running on VirtualBox Ubuntu and its pretty fresh so im not sure if i need any other pre requisites to actually find and install the integration.
Finally had some time to update to 2021.6, and of course this integration no longer worked.
Looking at everyone elseās comments, I realised that a version tag was needed in the manifest.json file.
Added a version, but still āno fujitsu_general_heatpump integration foundā. After a bit of searching in the forums, discovered that the ādomainā key in the manifest.json needs to be the same as the folder name in the custom components folder.
After doing this, it went back to working perfectly again.
Here is my manifest,json file in case it may help anyone:
{
"domain": "fujitsu_general_heatpump",
"name": "fujitsu_general_heatpump",
"documentation": "https://github.com/Mmodarre/pyfujitsu_for_homeassistant/blob/95e3ba879214aa9abf70979185ae189776ba4846/README.md",
"dependencies": [],
"codeowners": ["@Mmodarre"],
"requirements": ["pyfujitsu==0.9.0"],
"homeassistant": "0.96.0",
"version": "0.0.0"
}
Cheers
Rebel Elephant
thanks!! that works
Hi! I also have this issue! After couple of days, i cannot stop and start my AC, only with FGLair. Did anyone find a solution for this? Thank you for your help!
Update: at my side only cool is not working, i can turn it off, set to fan_only heat, but cool setup is not working after a couple of hours, days! :S Do you have any hint?
Thanks! Have a nice day!
Iām having the same issue. All features work except setting the mode to āCoolā. I can put the AC into any other mode, power on/off, and change temp no problemā¦but as soon as I select cool nothing happens and I have to use the fglair app
Running HA Core on a Docker (Synology).
Wanted to run HA OS so installed it, but I canāt get my airconditioning to work on HA OS. I simply copied everything but I keep getting the same error, ācomponent not foundā. Guess iāll keep my HA Core for a while.
I saw @Mmodarreās original thread, but then found this one and have been muddling through. Iām in the US, running HA on a Synology VM. Iāve attempted to follow the comments above. Iām getting the following error when checking config:
Platform error climate.fujitsu_general_heatpump - cannot import name 'ATTR_AWAY_MODE' from 'homeassistant.components.climate.const' (/usr/src/homeassistant/homeassistant/components/climate/const.py)
Iāve done this:
ā¦and this:
(
_pycache_
was automatically created)
ā¦and my configuration.yaml
has this:
climate:
- platform: fujitsu_general_heatpump
username: !secret fglair_username
password: !secret fglair_password
region: 'us'
tokenpath: '/config/token.txt'
Iām also using @rebelelephantās manifest.json
file from comment # 208 and @leacho73ās code from comment # 203 in my climate.py
file to get current temperature.
I donāt see this error anywhere above. Any ideas?
EDIT: Itās workingā¦ mostly.
Hi, I am Chris and got my Fujitsu ACs recognized in Home Assistant today.
The strange thing is, that I can view the status of the ACās, but I can not send commands to them. Also the FGLair APP on my Android phone has the same problem. When sending commands (e.g. Heat or FAN or change temperature) I get a network error on the smartphone. On HA I do not receive errors
But when I send commands to the AC with the IR remote control, I see the changes appear in the FGLair App and a few seconds later also in the Home Assistant dashboard.
Does anyone has this behavior to? Any suggestions?
Problem disappears after a few days. I did not change anything. I suppose there was a problem at fglair server side.
Iāve just installed this successfully for the first timeā¦ but I have the same issue as described above.
@philwilldo thanks for this cool add-on. Worked flawlessly the first time.
Minor change required though in the instruction:
The correct installation would be
A) Download and install the files
B) Restart HASS This is missing in your instructions The restart forces the HASS to recognise the new component although the configuration is missing.
C) Configuration.yaml changes
D) Restart Hass
If users follow the instructions given, HASS wonāt let the server to restart due to the configuration error !!
Hope this helps
Hey there, I just recently got this to work with my Home Assistant install on Debian 11. Iām having an issue where I can only adjust the temperature in celsius, and only a few temperatures in Fahrenheit. 68F & 69F work, 77F sets it to 78F in the FGLair app, 78F sets it to 79F, and 86F sets it to 88F.
Does anyone else have this issue or know of a solution?
Thank you!
Hi there. Want to use this to make automations for my home. Following functions do not respond (in automations and UI) climate turn on and mode heat. Anyone else who has this problems?