May be a good idea. Just one other remark: The plugin translates the state of a Domoticz device from the Domoticz language to the Rhasspy language. But I think device states are always reported in english and Domoticz uses the language setting only for the frontend. In my case the Domoticz language ...

Good point Walter, I was already thinking if this has to be a plugin since it uses the API to access Domoticz.

It wasn't a difficult fix.
I am going to experiment a little further, all my temperature sensors are temp/hum. I'll see if I can add them to the validation.

I did not try speech recognition yet for lack of a suitable microphone.

I've changed if domoticz_result.ok and (domoticz_usrvar := searchJSON(f"result[?Name=='{domoticz_device}'].Value", domoticz_result.json())): domoticz_device = domoticz_usrvar into if domoticz_result.ok: domoticz_usrvar = searchJSON(f"result[?Name=='{domoticz_device}'].Value", domoticz_result.json ...

Ok, I tried again but I do not think it is working as you described. To test I added some debug statements in the plugin and also commented the 2 lines that lookup the uservar. def domoGetIDX(domoticz_device): domoticz_idx = 0 # first try to translate the supplied device name to the value of a user ...

That is what I first expected but the plugin did not find my device until I added a uservariable with the device-name as name and value.
I will look again if something else was the problem.

I tried to use Rhasspy and your plugin but setting all up is not quite easy. But I think I have it almost running. One thing I do not understand is the use of a user variable for every device. Until now I did not use user variables at all and having to define one for each (new) device seems a lot of ...

What is the trigger for your script?
You can use print statements for debugging, they show in the log.

Did you enable Home Assistant Integration in Zigbee2MQTT?
This generates the discovery topics that Domoticz auto discovery is using. Also make sure the topic name in Z2M is the same as in Domoticz AD hardware.

You probably have set port 8080 for Domoticz web-interface as well as for Z2M frontend. So you have to change the Z2M frontend port in configuration.yaml.

I think you need to use: sudo npm install -g pnpm

I think you have to set 'prevent loop' to false on the Domoticz MQTT Client Gateway in Hardware settings.
But beware that this can result in the message looping with other devices acting on domoticz/in and out.

most of the esp8266 are working with mqtt. the strange thing is that it only works one way Did you use a device Domoticz MQTT Helper? That type of device can act on the MQTT messages on /domoticz/out. I think this is the most easy way to implement this. As an alternative you can use Generic - MQTT ...

I did just now but it was still the same garbled screen.
Since I have a previous version with driver ILI9341 that is working I will stick to that.

Ah, I thought I needed to change it TO zero. If I change it to 1, 2 or 3 the screen is still not good. But when I change the driver from ILI9342 to ILI9341 (which is in my other version) the screen is readable but rotated (heigth and with swapped?). Again, I can put 1, 2 or 3 in screen_driver.cpp ...

I downloaded the latest test branch, just to make sure no changes are missing.
Line 526 in sreen_driver.cpp was already as you described, but it did not change anything.


The version of the test branch that I used before works on both units, only the colors are different.

Well, I don't understand which json you mean. I can only find the board definition in esp32-2432S028R.json which mentions DILI9342_DRIVER=1. Changing DTFT_ROTATION in this definition does not change anything (on both boards) so maybe this is not the right place. For now I will stick to the previous ...

I tried with another unit and everything was fine, so maybe I made some mistake the first time. Sadly, I have to correct my previous post. I tried the first unit once more and the display looked like below. Both are ESP32-2432S028 but one is USB-C and the other is micro-USB, so the hardware/display ...

I tried with another unit and everything was fine, so maybe I made some mistake the first time.

The latest test branch does not work on my esp32-2432S028R. Even after erasing flash it shows a malformed display.