Dear all, I'm using a TS0601_thermostat_1. This radiator/thermostat valve exposes, amongst others, "preset" and "system_mode". In Zigbee2MQTT, the selector "preset" can be set to auto , manual , off and on ; the selector "mode" can be set to auto , heat and off . However, not all of these selector ...

Hi all, I would like to clean my code a bit by replacing local devicesThermostatTemperature = {'Thermostat (Room1) - Temperature', 'Thermostat (Room2) - Temperature', 'Thermostat (Room3) - Temperature', 'Thermostat (Room3) - Temperature'}; with local devicesThermostatNames = {'Room1', 'Room2 ...

Hi Folks I've got two types of thermostats: Tuya-type TS0601_thermostat and Tuya-type TS0601_thermostat_1. The later is an updated version but not fully supported in the zigbee2mqtt plugin in Domoticz. Some items are (yet) not available (max_temperature, min_temperature, window, heating, boost ...

Why didn't I know this? I'm gonna try immediately. This is might be the solution. Great.
Thanks!

Dear all, Many physical devices comes with many (sub) devices showing as separate devices in the device list. If you want to use then you'll have to add them as 'used' but some are rarely necessary. This ends up with an enormous large list and causes issues for readability and clarity. Also when ...

Thanks for the reply. Apparently I don't understand the MQTT idea. I thought it should be a kind of "man in the middle" but according to the comments it works a bit different. However, the errors does not appear when the MQTT is disabled. But it does not tell me where to solve the issue. The ...

Thanks for the MQTT-tool. I've used it to find any lines to the corrupted idx (115 in my case). Subsequently, I performed an action in Domoticz in which the corrupted idx is send to MQTT. MQTT reports the following: in = {"idx":115,"nvalue":1,"svalue":"","Battery":100,"RSSI":5} So I considered to ...

Thanks for your response. After cleaning the DB and a reboot the first error message has been vanished but the second one (" Error: Mosquitto: MQTT: unknown idx received! (idx 115) ") refering to a deleted dummy device with the index 115 still remains. Anybody another idea? Looking forward to it ...

Dear all, I've removed a virtual device (for Tasmota) as I'm using "Autodiscovery of Tasmota" now. However, the virtual device appeared to have a reference to MQTT and now giving errors in the log: 2021-09-12 20:26:07.229 Error: Tasmota: (Tasmota) tasmota::updateInfo1Devices: Set module and version ...

Mission accomplished! I've got the system working. Some of the pitfalls I trapped in were: The mentioned token is not the key that is required. The token can change from time to time. What is required is the "LAN key" which cannot be obtained on a different way than the old Xiaomi version. You don't ...

hi erem,

that's exactly what I've tried but without success. I don't understand why.
Might it be that an additional tag is send over RF433 that is not recognized by the RFLink receiver?

Hi All, In our kitchen we have a Wave Design SF-01 Ventilation/Hood that comes with a RF 433 remote control. I'm able to receive the messages from the remote control (20;5B;Bosch;ID=6e43;SWITCH=1;CMD=UP;) but I'm not able to send those using RFLink. According to the support list both directions ...

Hi all, I found somewhere in the basement an old CDB-6500 door chime using the Kaku protocol. The button-part is gone unfortunately so I cannot snoop the RF transmission codes. Googling found some information ( X , X , X ) but not sufficient to let the bell ring. I'm using RFLink and the RFLink ...

Great! thanks. Life can be so easy, sometimes.

Hi all, I would like to test if a device is online. More specifically a WiFi light bulb. I could retrieve the last-updated-time as well as the state, but both parameter give normal values when the device is on or offline (power is off). A method might be to ping on the IP address but I couldn't find ...

In conjunction to my previous mail above, I was wondering if the password I'm using is not the correct one. The app has changed considerably over the last few years. All internet instructions for the gateway refer to the 2017/2018 version of the Mi Home app. However, many of the notes does not apply ...

Hi All, I've purchased the Xiaomi Gateway 2 and have been successful in opening the 9898 port using the UART and soldering procedure. (following the instruction from a German site or the HA-site ). Subsequently, in Domoticz the Xiaomi Gateway has been added to the hardware according to these ...

Just playing around a bit, with some trial and error I found out the cause. In my script I started with "adb kill-server" then continued with start-server etc... By applying once at the start, then skipping this call resulted in a working script. so the proper script should become: #!/bin/sh echo ...

Alas, it's not solved yet :( . so this is the shell script #!/bin/sh echo "::: Start ADB connect script :::" adb kill-server adb start-server adb connect 192.168.2.7 adb shell input keyevent KEYCODE_POWER echo "::: End ADB connect script :::" With owner/mode as: 4 -rw-rw-rw- 1 pi pi 261 Apr 22 10:58 ...

Thanks Rob for consideration. Effectively my shell script isn't more then the manual handled lines. But your comment about the user is pointing me probably to the right direction. The "manual lines" were executed as user pi, however, the shell script was executed as root (sudo) as the owner/modes ...