Configure RM Mini ir blaster (no Broadlink)

Hello guys,
I have a cheap ir blaster named IR Mini (it is not Broadlink, like in all youtube videos and all other posts from the whole internet), managed to flash it via tuya-convert, configured it to work with mqtt, so I can send a mqtt.publish message to the ir blaster and added it in a card (button) in HA to trigger it from there, it is working well.
I think I didn’t configured something well because in HA I don’t see an entity for the device and when I go to Configuration > Integration > Tasmota and I click o the device, if I want to create an automatization or a script I get this message: There are no automatizations enable for this device!

I want to use Amazon Alexa to control this ir blaster and in the future to make some automatizations and I think that I need like HA to see the device entities for that (it’s just an assumption), can you please help me make HA to see the ir blaster entity?

EDIT 1 (solution of the main post): Found a solution for this, I reinstalled Home Assistant and started from 0 but I think reinstalling MQTT only can fix the issue. If you want to control it via Alexa you don’t need an entity for the ir blaster, using a configuration and a script like this one of @ben0551 it will create a “switch device” in HA so it will be visible in Alexa.

EDIT 2: In this post this guy have a similar ir blaster and in his case HA found an entity for the device.
In one of the answers I saw that you can make the ir blaster as a switch using yaml configuration file, can you please tell me where do I have to put that configuration file?

EDIT 3 (solution of EDIT 2): To edit configuration file you need an addon (File Editor / VS Code), when you open one of this addons you will see all the yaml files. Hope this will help someone new like me :smiley: !!!

Thank you!

HA infos:

System Health

version: core-2021.5.5
installation_type: Home Assistant Supervised
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.9
os_name: Linux
os_version: 5.4.0-1035-raspi
arch: aarch64
timezone: UTC

logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

host: Raspberry pi 4 4gb
host_os: Ubuntu 20.04.2 LTS
update_channel: stable
supervisor_version: supervisor-2021.04.3
docker_version: 20.10.6
disk_total: 56.8 GB
disk_used: 6.0 GB
healthy: true
supported: failed to load: Unsupported
supervisor_api: ok
version_api: ok
installed_addons: Mosquitto broker (6.0.0), Check Home Assistant configuration (3.7.1), motionEye (0.13.0), TasmoAdmin (0.15.0)

Ir blaster infos:

10:22:29.450 CMD: status 0
10:22:29.458 MQT: stat/ir_remote/STATUS = {"Status":{"Module":0,"DeviceName":"IR Remote","FriendlyName":["IR Remote"],"Topic":"ir_remote","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
10:22:29.464 MQT: stat/ir_remote/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"","RestartReason":"Software/System restart","Uptime":"0T01:49:22","StartupUTC":"2021-05-20T07:33:07","Sleep":50,"CfgHolder":4617,"BootCount":23,"BCResetTime":"2021-05-11T16:31:42","SaveCount":60,"SaveAddress":"FB000"}}
10:22:29.468 MQT: stat/ir_remote/STATUS2 = {"StatusFWR":{"Version":"9.4.0(ir)","BuildDateTime":"2021-04-23T10:07:18","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"341/699"}}
10:22:29.473 MQT: stat/ir_remote/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00028009","2805C8000100060000005A0A000000000000","00000380","00006000","00000000"]}}
10:22:29.480 MQT: stat/ir_remote/STATUS4 = {"StatusMEM":{"ProgramSize":588,"Free":412,"Heap":21,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540C8","FlashFrequency":40,"FlashMode":3,"Features":["00000809","0F5A0582","04000001","00000002","00000000","00000000","00000000","00000000","00000000"],"Drivers":"1,2,4,5,7,9,10,12","Sensors":""}}
10:22:29.485 MQT: stat/ir_remote/STATUS5 = {"StatusNET":{"Hostname":"ir_remote","IPAddress":"","Gateway":"","Subnetmask":"","DNSServer":"","Mac":"24:62:AB:04:41:6E","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
10:22:29.490 MQT: stat/ir_remote/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_04416E","MqttUser":"mqtt","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
10:22:29.499 MQT: stat/ir_remote/STATUS7 = {"StatusTIM":{"UTC":"2021-05-

Do you mean you don’t see an entity for the blaster itself, or you don’t see entities for the devices it is controlling?

If the latter, I think this is correct. As far as HA is concerned, the only device available is the blaster

Hello, I don’t see an entity for the ir blaster.
Edited the main post to avoid confusions, thank you!

Try this command in console of the ir blaster Commands - Tasmota

SetOption19 Set Home Assistant discovery protocol.
0 = use Tasmota integration (default)
1 = use MQTT discovery

In this example I have a IR controlled LED strip which I have made a switch in HA for

my config yaml has

- platform: template
          service: script.ir_kitchen_strip_on
          service: script.ir_kitchen_strip_off
        friendly_name: "Kitchen Strip"

and scripts has

  - data_template:
      payload: '{"Protocol":"NEC","Bits":32,"Data":"0x00FFB04F"}'
      topic: 'cmnd/IRBlaster2/IRSend'
    service: mqtt.publish

  - data_template:
      payload: '{"Protocol":"NEC","Bits":32,"Data":"16758855"}'
      topic: 'cmnd/IRBlaster2/IRSend'
    service: mqtt.publish

It’s already set to 0.
If it’s set to:
0 - I see the ir blaster at devices but no at entities
1 - I don’t see it at devices or entities, so a ghost :smile:

About the scripts, I don’t know where to put or how to use them but I understand what they are doing…

Thank you for you answer!

EDIT: Find the solution like an EDIT of the main post.