Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error #19

Closed
wifi75 opened this issue May 29, 2020 · 12 comments
Closed

Error #19

wifi75 opened this issue May 29, 2020 · 12 comments

Comments

@wifi75
Copy link

wifi75 commented May 29, 2020

From mqtt explorer there are all command.. and if i change mode from remote controll on mqtt explorer change correctly... but from HA not work maybe the config it is not correct?

see below

Cattura

only temperature work....
hik

@ck007max
Copy link

The problem is that hassio can't identify the status of the AC because the value topic is written in capitol letter. The author of the script could transform the topic in a way that hassio can use for update the status and for the command. Infact the only function that works is a number status.

@wifi75
Copy link
Author

wifi75 commented May 29, 2020

Hi @ck007max my topic it is lowecase:
see below:

./hisense.py --port 8888 --ip 192.168.1.251 --config config_stanzetta.json --mqtt_host 192.168.1.52 --mqtt_user user:password --mqtt_topic hisense_stanzetta

@deiger
Copy link
Owner

deiger commented May 29, 2020

The data provided to HA is always in lower case, see the explanation in #15.
@wifi75, which configuration are you using for HA? If you are using mine, and change the mqtt_topic, you should also change the prefix for all the topics in the configuration.

@ck007max
Copy link

I use your config and your original topic, but when I launch the hisense.py script I receive these following messages from HA: 2020-05-29 20:15:29 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid swing_modes mode:
2020-05-29 20:15:29 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid fan_modes mode:
2020-05-29 20:15:31 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid modes mode:
So I think that there is a problem with HA and mqtt topic

@deiger
Copy link
Owner

deiger commented May 29, 2020

IIUC, the error message for e.g. "Invalid fan_modes mode:" should end with the invalid mode. It seems that it got an empty string...
I think I understand the issue. Try removing the value_template row from the config. The response should not be escaped as JSON.

@wifi75
Copy link
Author

wifi75 commented May 29, 2020

@deiger Of course I have already done it but it doesn't work see below:
1
very strange because in mqtt explorer there is all the data!
2

@wifi75
Copy link
Author

wifi75 commented May 29, 2020

@deiger Read also this message afgter status service command:

3

@deiger
Copy link
Owner

deiger commented May 29, 2020

I see in your screenshot value_template is set. Could you try removing that line?

@wifi75
Copy link
Author

wifi75 commented May 29, 2020

@deiger I have tryed to remove that line but doesn't work

@ck007max
Copy link

ck007max commented May 30, 2020

@deiger I've followed your change and I've removed "value_template". Now, the HACV component reads the status, but there is a problem with the command line. I can't change the status of the settings via HA. If I push "cool" button, nothing happens. And there is a problem with fan_only mode: 2020-05-30 08:29:45 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid fan_modes mode: fan_only. It happens when AC is off or after switch off.
status
t_fan_speed

@wifi75
Copy link
Author

wifi75 commented May 30, 2020

@ck007max @deiger , yes true! Also for me sam problem...there is little to get everything working.

@deiger deiger closed this as completed in 268d0e1 May 31, 2020
@deiger
Copy link
Owner

deiger commented May 31, 2020

Ah, found the bug - please re-download the server script and retry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants