MQTT random binary or other formats data about core HOT 3 CLOSED

Nothing changed between the tagged versions of Home Assistant related to encoding.
It seems you are using/wiriting a custom component which we do not support, but I assume you know that.

By default we try to decode incoming payloads as utf-8 on the supported entity platforms. If you do not want that you can either set a custom encoding or set it to None if you want to handle the decoding yourself.

This this signature of API method for async_subscribe:

@bind_hass
async def async_subscribe(
    hass: HomeAssistant,
    topic: str,
    msg_callback: AsyncMessageCallbackType | MessageCallbackType,
    qos: int = DEFAULT_QOS,
    encoding: str | None = DEFAULT_ENCODING,
) -> CALLBACK_TYPE:
    """Subscribe to an MQTT topic.
   ....

from core.

Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

from core.

Nothing changed between the tagged versions of Home Assistant related to encoding. It seems you are using/wiriting a custom component which we do not support, but I assume you know that.

By default we try to decode incoming payloads as utf-8 on the supported entity platforms. If you do not want that you can either set a custom encoding or set it to None if you want to handle the decoding yourself.

This this signature of API method for async_subscribe:

@bind_hass
async def async_subscribe(
    hass: HomeAssistant,
    topic: str,
    msg_callback: AsyncMessageCallbackType | MessageCallbackType,
    qos: int = DEFAULT_QOS,
    encoding: str | None = DEFAULT_ENCODING,
) -> CALLBACK_TYPE:
    """Subscribe to an MQTT topic.
   ....

Yes it is a custom component @jbouwh, the problem was that I had to implement that function as per sometimes the value is output as binary and sometime as string.. anyhow so far the work around works fine and of course if you do not plan to correct it (and thanks for the clarification) it is fine for me too.

• Device connected to HA $state=b'Ready'
• Disconnected ..
• Reconnect to HA, $state="Ready"
  I think this can create problems also to you guys.

Anyhow NodeRed and other "custom components" later on.. did become add-on or integrations, and as soon I can clean the code as it should be I hope to present it to you guys (so far I test it in the real world and it is not creating problems to the core) as per I try to keep up with your development as well.

from core.