Thing is that there is no documentation on how to control these Gen3 devices, so integrating is one thing, we can read the published mqtt messages. But controling a dimmer left us guessing, there's lack of documentation.
Shelly support plays stupid and they're good at it.

I have successfully implemented Shelly1 Gen3 , however i was lucky that i could lift on work that was done. On the new Shelly Dimmer Gen3 i am disappointed by Shelly due to lack of documentation, this is not going to work with shellyteacher4domo , developer gave up. Shelly responded: "We would like ...

So there's a new Shelly Dimmer Gen3 and guess what, i'm not succesfull with Domoticz integration. On the shellyteacher4domo thing i've created an issue and got the motivated response; "As Allterco has no usable mqtt documentation since gen1, i simply give up and now i am using only zigbee devices ...

Just installed shellyteacher4domo and ran it... this first resulted in an error for this new device. So i've created a new entry for the tag [shellydimmerg3] in mqtt_templates_gen2.txt so that it's recognized. This specific file (mqtt_templates_gen2.txt) inside shellyteacher , takes care of MQTT ...

Suddenly it was released so i ordered a couple to replace my older (Gen1 and 2) ones that are sort of dying (dropping connection or not responding at all). Not knowing what i was getting into, i found out that the device isn't as easy as it was before.... so i thought, the functionality "one-button ...

Hi, I was just looking into the setup again... lost my previous config somewhere along the road. Have my NAS configured, this shuts down as configured and sends out a msg on status changes. I have a RaspberryPi setup with NUT as slave, monitoring the server which is running on my Synology NAS. When ...

I'm around the same point... having my devices in MQTT, but not Domoticz. Last weekend i have searched and found documentation in the wiki that said MQTT autodiscovery was not yet added in v 2023.1 which is my current version since i haven't updated (yet). Anyway... i think it was the same ...

I'm around the same point... having my devices in MQTT, but not Domoticz. Last weekend i have searched and found documentation in the wiki that said MQTT autodiscovery was not yet added in v 2023.1 which is my current version since i haven't updated (yet). Anyway... i think it was the same ...

Nice, but needs some work... Last output: /etc/monit/ntpsync.sh: regel 7: /usr/bin/ntpstat: Bestand of map bestaat niet /etc/monit/ntpsync.sh: regel 17: ((: < 200 : syntaxfout: operator verwacht (het onjuiste symbool is "< 200 ") /etc/monit/ntpsync.sh: regel 23: ((: >= 200 : syntaxfout: operator ...

@marmachine If you did a git install you can simply change Dashticz' branch to Beta by typing the following command (Terminal) in the Dashticz folder... Excellent, thanks! git fetch origin git checkout beta M custom_2/CONFIG_DEFAULT.js M index.html M index2.html M jsconfig.json Branch 'beta' set up ...

Have you checked https://dashticz.readthedocs.io/en/beta/blocks/specials/weather.html ? For the new version 3 key you have to add a provider parameter to the block. For OWM the provider parameter seems irrelevant actually, because when i add this -> provider: 'owm', <- the block doesn't work ...

Have you checked https://dashticz.readthedocs.io/en/beta/blocks/specials/weather.html ? For the new version 3 key you have to add a provider parameter to the block. For OWM the provider parameter seems irrelevant actually, because when i add this -> provider: 'owm', <- the block doesn't work ...

Using the default OWM blocks, so in my config file there is; //Configuring the OWM parameters config['owm_api'] = 'put personal API key here'; // Personal OWM API key config['owm_city'] = 'Apeldoorn'; // city or nearby city to use (you can also fill in the city id here) config['owm_name ...

@marmachine If you did a git install you can simply change Dashticz' branch to Beta by typing the following command (Terminal) in the Dashticz folder... Excellent, thanks! git fetch origin git checkout beta M custom_2/CONFIG_DEFAULT.js M index.html M index2.html M jsconfig.json Branch 'beta' set up ...

I am using the default OWM blocks, so in my config file there is; //Configuring the OWM parameters config['owm_api'] = 'put personal API key here'; // Personal OWM API key config['owm_city'] = 'Apeldoorn'; // city or nearby city to use (you can also fill in the city id here) config['owm_name ...

I have found out that a newly generated key on a new account, works with the old link in order to download (json) data. Doesn't work without an aditional subscription to onecall (still free for 1000 calls per day) api.openweathermap.org/data/ 3.0/onecall ?lat=52.211462&lon=5.972701&appid={API key ...

Hi, For some time i am receiving emails from openweathermap's robot which is telling me that i am exceeding the account limit of 1000 calls per day. I am using the API service for two applications; Domoticz (LUA script) and Dashticz, each has it's own key, however the usage for each key is ...

Well, retry on a clean Debian 11 system is now successfull!

The complete compile method, following below instructions is;
https://www.domoticz.com/wiki/Build_Dom ... rom_source

Compiling manually runs into another error... sudo apt-get install build-essential -y sudo apt-get install libboost-dev libboost-thread-dev libboost-system-dev libsqlite3-dev subversion curl libcurl4-openssl-dev libusb-dev zlib1g-dev python3-dev sudo apt-get install cmake sudo apt-get install git ...

Got my hands on an older IoT Edge computer which supports Linux... so i'm trying to install Domoticz... The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian ...