Thanks for posting that… my code was “F” and my values were showing in C also. However, even after changing all of the values (for three heat pumps) to “C”, my temps are still showing in C even after a HA restart. Weird.
EDIT: Restarted the Hisense add-on… and now I’m getting Fahrenheit.
EDIT 2: I’m not seeing my horizontal fan swing setting. swing_modes, when manipulated, turn vertical swing on and off. No other swing mode shows up in the attributes:
hvac_modes: off, fan_only, heat, cool, dry, auto
min_temp: 61
max_temp: 86
target_temp_step: 1
fan_modes: auto, quiet, low, medium, high
swing_modes: on, off
current_temperature: null
temperature: 72
fan_mode: high
swing_mode: off
friendly_name: Heat Pump
supported_features: 41
I’ve installed https://github.com/nervetattoo/simple-thermostat and I get nice card, but it seems I can’t get vertical swing modes positions, it’s only “vertical swing” with on/off. Any ideas how we can control vertical position?
Can you post the yaml of your thermostat card, please? I use the same card from an year and i like the setting with icons instead of name. If i set name: false as you the in HVAC buttons there are icons as yours but fan buttons are blank.
how can i put icons like yours?
Note that my sensors come from a completely different device. The Fujitsu heat pumps don’t provide a push of current temperature… they will report it on request only (which I think is silly).
Hi Tim, thanks for the efforts sorting this out with deiger to get this going in Australia. I’ll be switching tomorrow
As FYI I mostly stopped using the the FGLAir integrations as I found best of all worlds was a simple IR blaster and a few scripts for summer, winter etc.
I’ve this problem since a few days.
The Aircon doesn’t respond anymore.
Do you have this problem, a solution?
Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:746
Integration: Thermostat (documentation, issues)
First occurred: 16 août 2022 à 06:36:29 (7421 occurrences)
Last logged: 10:18:22
Updating fujitsu_general_heatpump climate took longer than the scheduled update interval 0:01:00
I have the same Problem for a long time. This happens after a day, when the API key renewal take place (API key for FGLAIR is only one day valid).
A workaround is to rebooting Home Assistant, but that is not a good solution. I do not want to reboot Home Assistant every day.
So if anyone have a structural solution for this problem, please share in this community.
I’m also having issues seeing anything from my Fujitsu heat pumps, where they were working previously. I’ve made no changes except for HA upgrades. MQTT seems to be working correctly:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[08:34:15] INFO: Setting up user hisense
[08:34:16] INFO: Certificates found: SSL is available
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[08:34:16] INFO: Starting NGINX for authentication handling...
[08:34:17] INFO: Starting mosquitto MQTT broker...
2022-09-06 08:34:17: Warning: Mosquitto should not be run as root/administrator.
[08:34:18] INFO: Successfully send discovery information to Home Assistant.
[08:34:18] INFO: Successfully send service information to the Supervisor.
Simon,
I have been having the same frustrations keeping FGLAir integrations working consistently. I really like the idea of the IR blaster solution. Can you share some specifics and tips on your implementation? I had already planned to add an ESP32 in the room with the HVAC and can easily add a remote board.
Much appreciated. - Brian
How do you know what port to use in the addon (hisense)? Mqtt and hisense is set up correctly i think.
First i had the same port as mqtt (1833) then i changed the port til 3805 in hisense.
The log only gives me this feedback: E0912 20:12:20.833 notifier.py:121] Failed to connect to 192.168.21.23 maybe it is offline?
Its a shame this can’t be made, or retrofitted into an Integration - that way you can just call a service to reload the integration every few hours rather than having to reboot home assistant!
Unfortunately I don’t have the technical skill to achieve such a thing
Hi Brian,
Sorry for the delay I got a little busy I don’t really do anything to complicated I’m using a broadcomm remote and learn the common commands from the remote that came with the A/C - very low tech.
I then wifi enabled a second AC (by installing a UTY-TFSXZ1 device)
I got it plugged with FGLair, so far so good my FGLair can pilot the Two AC
Then i want to have this second AC piloted through HA
i rebooted HA, uninstalled-re installed the add on
it keep on seing my first AC but not my second one
under config/hisense/
i see one Json file with one line for the config of the 1st AC
i suppose for a normal behavior there should be two lines (or two json files)
Hello. I’ve been trying to get my AC fglair recognized on homeassistant for two days. Here is the report I have in my HiSense Air Conditioners module log:
I don’t really do anything to complicated I’m using a broadcomm remote and learn the common commands from the remote that came with the A/C - very low tech.