waaren wrote: ↑Monday 01 February 2021 18:04 As always; please make sure you have a recent and tested backup !

Sure, that is automated once a day. I'm a bit afraid of messing up my 8 somfy devices but will take the chance.

Thanks again for your help!

First of all I have no intention to hijack this thread but the question I have is almost the same. Does your answer also apply to version 3.6675? I'm happy to say that I have version 3.6675 running continuously from feb 2017 with only a handful of reboots in the past 4 years. Unfortunately of ...

Not sure why you post this in dzVents if you want to call the API but you could use Although you are not interested in sunrise or sunset there is also a 'ServerTime' attribute with the current time.

--Gerard

ok, moved it to execute and it works (of course, it's only a one-liner).
Maybe in a future release there will be a place for some logic in the on= event part to get "cleaner/leaner" code.
Thanks again for your help.
--Gerard

Thanks for your reply. Although I have to test I think your nice example could/should work. My use case is in short: In our building there are a lot of PIR, door and window sensors. These are passively monitored 24x7. During the nighttime I want to monitor a subset of doors and windows and when ...

Hi All, De (partial) code below I use to check a device during nighttime. This works great. return { on = { devices = { ['FrontDoor'] = {'at 23:00-06:30'}, } }, execute =....... However I would like to add some logic to check an additional parameter or switch to disable or ignore the time limit. So ...

ok, fair enough. Thanks for the suggestion.

Indeed this is my opinion and is not only related to zwave. In mysensors something alike happens. And for that, my opinion is that there is a design flaw in the code (/hardware/MySensorsBase.cpp). For types V_TEMP and V_HUM the code searches for other children. This ludicrous. Since a mysensor node ...

Thanks for reporting back on this.
Maybe the sensor is a bit sensitive on 3.3v. Most likely a Chinese clone(?) These components usually work fine unless you are on the boundary of the specs.

Hi I can only also confirm I have weird temp+hum zwave qubino ZMNHADx (relay with DS18B20 temp sensor)..... Same here. This is definitely a Domoticz issue... Well may be not an issue but a design flaw. Sensors shouldn't be combined unless explicitly done by the user. Automatically combining sensors ...

If you look as the MYS gateway sending messages to the Domoticz/in topic then I agree with you. But in my opinion this is not the case. The MYS system is seen as separate hardware and therefore is treated the same as all other hardware. The common thing is MQTT and might 'feel' strange seeing the ...

Sorry too :-) I think this is "by design" to publish all messages within Domoticz to the topic domoticz/out. So even when a MYS node publish' a message to Domoticz on the (default) topic domoticz/in/MyMQTT you should see that message also on the topic domoticz/out. In some configurations this might ...

Not really. How is your Gateway config? Mine is:

4,7k is the normal value so you can eliminate that. Hopefully you have a oscilloscope on hand to check how "clean" the 3.3V is. If not you could set you DM on AC and see if there is some ripple. If there is a high freq. ripple, only a cap is not enough, you have to add a small coil to get an LC ...

This is called a "process of elimination"

R1 is a bit high. Try a 4K7 resistor.

You could go way cheaper, simpler and less power with an ESP8266 and one or more ds1820.
Or if you intent to use more sensors in the future you could have a look at Mysensors.
I use both but will migrate in time all sensors to the Mysensors network.

Try ["nearest-station"]

Most likely the power is despite the capacitors still not stabilized enough. Try a larger cap. Also a 100k pull-up seems a bit high.
Please share the schematic so we could get a better picture.

I do almost the same to measure the temperature of the cabinet where the pi is situated and use a simple quick and dirty python script. import os import glob import time import requests # sometimes needed #os.system('modprobe w1-gpio') #os.system('modprobe w1-therm') base_dir = '/sys/bus/w1/devices ...