dvdavide

Results 18 comments of dvdavide

Strange thing happened when configuring the integration from the external address. The integration would install normally, except I didn't get a field for "Home Assistant internal URL" in the config...

See #184 for a possible workaround

For a sensor or a binary sensor, this should work. ``` - platform: mqtt name: "Sensor name" state_topic: "hisense_ac/[macaddress]/[property]/status" (this bit only for binary_sensor) payload_on: "on" payload_off: "off" ``` Also...

It's been accounted for in the last change to the code. I changed it manually in my installation, don't know if it's included in the latest docker image

They are not implemented in the HA climate entity, but you can still control them via separate mqtt entities. I provided a small example in reply to issue #184

It would help a lot if you could find out what wifi module is installed in your AC. However, FGLair is in the list of supported apps, so you could...

Does the AC works with the mobile app? Does it have a fixed IP address? Delete the config_[ac_name].json from the configuration folder; while you are there also double check that...

See if my suggestion in #184 helps for a workaround

Not sure why it does that from the thermostat card, but I found a workaround by adding a separate [MQTT select](https://www.home-assistant.io/integrations/select.mqtt/) Code in configuration.yaml is like: ``` mqtt: select: -...

All I can suggest is checking these steps: - stop the container; - make sure that all your AC units are installed, configured, and reachable in your mobile app; -...