Make entity text input be larger than 255 (otherwise you cant use tuya IR blasters)

[123 (Taras)]

@vespuccio

these variables are bound to the script, right? I wanted them to be gloal and used on other scripts

Your needs are different than mine when I automated the range hood fan.

If I needed to store the IR code strings somewhere accessible to any script, I could create a Template Sensor and store the IR codes in is attributes (allows up to 16K of storage). Then I could reference them by name in any script using the state_attr() function.

Reference

Template Sensor

An alternative is to reconsider your current approach to handling IR codes. Instead of storing the IR codes somewhere accessible to multiple scripts, store them in a dedicated “transmitter” script that is called by multiple other scripts.

@vespuccio

Also I didn’t need to make it as a json message

According to Zigbee2MQTT’s documentation (refer to the link I posted above), you do need to ensure the payload you publish is in JSON format.

To write (/set ) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set with payload {"ir_code_to_send": NEW_VALUE} .

That’s the advice I followed for my project and demonstrated in the short example I posted above.

@vespuccio

when I listened for the topic there was no json structure, just a string publish.

Because a received IR code isn’t in JSON format. I strongly recommend you review Zigbee2MQTT’s documentation for your specific model of Tuya IR device. I read the docs for the Tuya ZS06 and it very clearly explains how IR codes are received and transmitted.