i mean the standard build in support like on the screenshot. it is some kind of "build in"plugin

i checked my settings and as remote address i just have the plani ip address 192.168.1.80, not the string as in the manual. i think the plugin was changed later on so that it can work with both the old and the new intergas gateway. so just plain ip adress, admin and password and then it should work ...

here is the script again in a more readable format. -- DzVents script for setting new thermostat temperature and updating setpoint of LAN2RF Incomfort Gateway Intergas -- V1.3 (oktober 2022. gateway thermostat override device does not update so using dummy thermostat) -- original V1.0 script made by ...

new manual with changed values so it works with latest plugin Intergas Incomfort koppelen aan Domoticz-v4.docx hi all, ik krijg de lan2rf gateway (Intergas) niet gekoppeld aan Domoticz. ik krijg steeds de melding 2024-06-01 12:57:47.102 Error: Intergas Incomfort: Error getting current state! 2024-06 ...

docker only runs on synology with an intel cpu
this one has an marvell armada

this is the reason i changed to a DS718+ years ago

platform is very stable and is also being used for data, video etc so no extra investment.

maybe someday i will tryout an rpi(if synology decided to kill usb connections)

i think you need to install the usb drivers separately

i believe there is a 6.2 package for that in syno communities

this works with IO/ URL actions

however you can only switch things on/ff with this
i do not think you can send power usage or temperatures with this.

so yes, basic switching works

your welcome.
to be more specific, i checked and i have the sensor hooked up to D5(not D13)

i am using a nodemcu unit but a wemos d1 mini will work as well

input NodeMCU and Wemos D1 mini both have 3.3 inputs
sensoren work correctly on 5V

attach sensor to 5V but inputs through a pullup resistor to 3.3V

Hello, i am using a nodemcu unit buy a wemos-d1-mini will work as well it is running ESPeasy software as a sensor i am using a LJ12-A3 proximity sensor which picks up magnetic disturbance proximity-aansluiting.JPG proximity-aansluiting.JPG this thread will help you i did not use a voltage converter ...

glad i could help

ok, if you did not manually fixxed things in edomoticz that's your problem

look at this thread

you can solve the issue by manually changing the domoticz.js file IN HOMEBRIDGE.

https://github.com/PatchworkBoy/homebri ... issues/265

that looks fine, i use the same command

do you have the edomoticz plugin in homebridge?

not sure but as far as i can tell you get that error when trying to access domoticz through http or https this script looks like it is accessing something else(unifi controller) so i doubt it is causing this error(don't shoot me if i'm wrong) i would check everything which is trying to acces ...

i havr a shelly 1pm and that one works perfectly with the old plugin.

yes it is not updated anymore but still supported
as long as you do not have/buy newer shelly types in the future i would advice to use the current plugin.

all this MQTT auto discovery stuff is still under development

i am using the same command and it is runnig fine

192.168.1.50,8084,/json.htm?type=command&param=udevice&idx=344&nvalue=0&svalue=[Watermeter#Total]

you do know that you need to turn on ALLOW BASIC-AUTH in the domoticz settings.

things will not work anymore without it.

i only had a couple of zwave devices so i moved to the new standard, zigbee(and hue)

working perfectly(as it did with zwave)

please note that the domoticz team can not support technology what is not maintained anymore by other people
at least that is what i was told.

ok that part is clear. … I don’t understand what you mean here. You should preferably use user/pass (or other forms of authentication) OR use Trusted network. Not both to give acces to a system/plugin. And again if any kind of authentication is provided, regardless valid or invalid, Trusted network ...

ok that part is clear. so somehow the new domoticz can not handle it when no user:password is specified with this plugin it can be that there still is a bug in the plugin it could also be that the security in 2023.1 was not functioning properly ang now in 2023.2 they fixed it. then it is still ...

thanks if you do not need a username password when everything is in the trusted network i suspect there is something wrong with this thermostat plugin. with domoticz 15092(2023.1) and plugin without user:password(left blank) basic auth off: no error everything working basic auth on:error 401 with ...