[BUG] - MQTT Prefix - App/Host and prefixcommand not working as expected - Also add a custom Prefix about esp32-faikin HOT 22 CLOSED

OK, yes, HA confirm messages did not allow for prefixapp or prefixhost at all.

I have changed to fix this in latest beta.

Also fixed the order of appname and hostname when prefixapp and prefixhost are set.

Also changes HA status messages to be a state message rather than top level MAC, so they follow the same rules for prefixapp and prefixhost.

Please test latest beta. Thanks.

from esp32-faikin.

It is called topiccommand now, but I have not changed how that works for this, just what is sent to HA.

So let me know if that does not sort it, and I'll look more in to that. Basically all the HA confirm assumed command/hostname/... which is wrong if different topiccommand or prefixapp or prefixhost set. Sloppy, sorry.

from esp32-faikin.

Latest faikin code allows / in command and setting names.

from esp32-faikin.

I've already updated to the latest.

I was trying the beta, which had the problem above, so I changed to non beta and updated this morning. Unfortunately it's still the same.

from esp32-faikin.

I'll look in the morning. The latest code really should cover all of this quite well. But I'll take a look.

from esp32-faikin.

Thanks! I appreciate it.

Just in case I'm wrong on this...

I was expecting the HA discovery payload to change from:

"~": "command/Villacana AC Back Bedroom",

To:

"~": "site3/command/Villacana AC Back Bedroom",

As it didn't, I assumed that's why AC commands aren't working. Similarly with the App/Host, it renders the AC control inoperable.

from esp32-faikin.

Yeh, it could be an error in my HA config stuff.

from esp32-faikin.

Thanks @revk, does this also fix the prefixcommand etc ?

I'll be able to test this afternoon.

from esp32-faikin.

Commands are now working in HA. 👍

However, I don't think the messages are formatted quite correct though:

Faikin > Faikin > {HOST}
State > Faikin > {HOST}

from esp32-faikin.

Also,

Let me double check I've updated to the latest Beta...

Yes: Faikin-S3-MINI-N4-R2: b1a9db5 2024-06-03T08:35:42

from esp32-faikin.

The buttons not allowing a save is weird. But yeh, check latest beta.

from esp32-faikin.

Yes, latest beta: Faikin-S3-MINI-N4-R2: b1a9db5 2024-06-03T08:35:42

from esp32-faikin.

I'll do some tests here and confirm.

from esp32-faikin.

OK complicated.

We have a periodic report that is sent as Faikin/ as the prefix. When using without prefixapp that would be Faikin/hostname, but with prefixapp it becomes Faikin/appname/hostname.

I am making a special case for not duplicating the appname if appname is used as the main topic, which should address that.

Beta in a moment.

from esp32-faikin.

Thanks...

Does that fix Command > Faikin > {HOST} as well:

from esp32-faikin.

OK command/Faikin/hostname would be if prefixapp set.

Where do you see that, as the Faikin does not send commands, it receives them.

(Sorry not familiar with whatever your are using to log things)

from esp32-faikin.

I'm using MQTT Explorer, and the command is coming from Home Assistant when I change the climate state.

The climate entity is publishing to command/Faikin/hostname so HA can't sent the command over a bridge when the remote bridge has topic Faikin/# in 0. I think it should publish to Faikin/hostname/Command, that way all statuses and commands can be segmented with Faikin/#

I believe this is what happens with Zigbee2MQTT base topic and ESPHome topic_prefix .

Note: topic Faikin/# in 0 is a hack. I really need to set the base topic to my site name.

from esp32-faikin.

OK, the prefixapp and prefixhost settings allow a number of combinations which can be adjusted to suite your needs.

The latest beta should consistently report a config to HA matching what the Faikin is set to do.

from esp32-faikin.

Bingo! The messages are now routed correctly for me. Thanks

And if I set topiccommand etc.. with a prefix and deselect prefixapp and prefixhost that works as well, and means I can use my site name z2m_villacana to segment: 👍

Thanks for your help

from esp32-faikin.

Sorry to raise another problem.

With the latest beta: Faikin-S3-MINI-N4-R2: b1a9db5 2024-06-03T08:35:42
I've lost the current temperature for both Faikin units:

"curr_temp_t": "34B7DA588E44",

Should be:

"curr_temp_t":  "Faikin/Villacana AC Back Bedroom/state/ha",

"Faikin/Villacana AC Back Bedroom/state/ha"

{
  "unique_id": "34B7DA588E44",
  "dev": {
    "ids": [
      "34B7DA588E44"
    ],
    "name": "Villacana AC Back Bedroom",
    "mdl": "FTXM20R",
    "sw": "b1a9db5",
    "mf": "RevK",
    "cu": "http://Villacana AC Back Bedroom.local/"
  },
  "icon": "mdi:thermostat",
  "~": "Faikin/Villacana AC Back Bedroom/command",
  "min_temp": 16,
  "max_temp": 32,
  "temp_unit": "C",
  "temp_step": 0.5,
  "temp_cmd_t": "~/temp",
  "temp_stat_t": "Faikin/Villacana AC Back Bedroom/state/ha",
  "temp_stat_tpl": "{{value_json.target}}",
  `"curr_temp_t": "34B7DA588E44"`,
  "curr_temp_tpl": "{{value_json.temp}}",
  "mode_cmd_t": "~/mode",
  "mode_stat_t": "Faikin/Villacana AC Back Bedroom/state/ha",
  "mode_stat_tpl": "{{value_json.mode}}",
  "fan_mode_cmd_t": "~/fan",
  "fan_mode_stat_t": "Faikin/Villacana AC Back Bedroom/state/ha",
  "fan_mode_stat_tpl": "{{value_json.fan}}",
  "fan_modes": [
    "auto",
    "low",
    "lowMedium",
    "medium",
    "mediumHigh",
    "high",
    "night"
  ],
  "swing_mode_cmd_t": "~/swing",
  "swing_mode_stat_t": "Faikin/Villacana AC Back Bedroom/state/ha",
  "swing_mode_stat_tpl": "{{value_json.swing}}",
  "swing_modes": [
    "off",
    "H",
    "V",
    "H+V",
    "C"
  ],
  "pr_mode_cmd_t": "~/preset",
  "pr_mode_stat_t": "Faikin/Villacana AC Back Bedroom/state/ha",
  "pr_mode_val_tpl": "{{value_json.preset}}",
  "pr_modes": [
    "eco",
    "boost",
    "home"
  ]
}

from esp32-faikin.

Oops, let me fix that now. Next beta, in a few minutes.

from esp32-faikin.

Thanks! All sorted

Faikin-S3-MINI-N4-R2: 57fcc76 2024-06-04T09:06:53

from esp32-faikin.