benp wrote: ↑Friday 30 August 2024 13:45 Zwave devices not updating state after manual press

Solved: 2 days later, it is possible to change the switches state with a manual press. Why? I don't know because I did nothing special!

Hello, Same problem for me: Failed to open serial port cannot open *dev/zwave(ZW0100) 7 month later: I found the problem for myself. In zwave-js-ui / settings/ zwave , I disable soft reset and it works. Capture.PNG I used the snap method explained in the french forum: https://easydomoticz.com/forum ...

The link to the Arduino forum: https://forum.arduino.cc/t/stange-ghost-interrupt-on-esp32-rainmeter-domoticz/1250942 The ghost interrupt problem is SOLVED: this is an ESP32 bug. Ghost interrupt can occur with wifi sleep so wifi sleep must be disable! I will update the first post with link to working ...

Here is the link to the arduino forum:
https://forum.arduino.cc/t/stange-ghost ... cz/1250942

This may be an electromagnetic interference problem (15 meters is a lot), several checks possible: Thank you. I simplified the wiring: nothing plugged to the ESP32. Only the INPUT_PULLUP: I still have the problem: the interrupt fire 3 times per hour up to one time per 8 hours. But definitely it is ...

Bad new: the ESP32 detect false rainmeter bucket The TFA tfaR.png The ESP32 davis3R.png Maybe the pullup resistor is too high: around 50kohms according to ESP32 users. The wire to the rainmeter is 15 meters long. I tried to add a 1000 ohms resistor as pullup. IMG_20240420_111112bd.jpg But no luck: I ...

This is an update of my Davis+FGBS222 zwave configuration on the french forum: https://easydomoticz.com/forum/viewtopic.php?t=13278 I have no question because my project is supposed to be fully functional according to my test "water in the boottle" but only true rain will tell me... Comments are ...

I migrated somewhere spring last year from a Pine64 to my QNAP NAS. Took me a lot of searching because the Z wave stick was not recognized at first and had to install an additional driver. After that a similar problem as you mentioned and I solved it (again: for a QNAP) by using "devices: /dev ...

I found a problem on my config: ben@domoticz-nas:/opt/zwavejs-ui$ ls /dev/serial/by-id/ ls: impossible d'accéder à '/dev/serial/by-id/': Aucun fichier ou dossier de ce type This can be a bug on Debian 11 Bullseye: https://klipper.discourse.group/t/debian-11-bullseye-udev-bug-no-board-or-serial-found/ ...

Hello, Same problem for me: Failed to open serial port cannot open *dev/zwave(ZW0100) Here is the zwave-js-ui screenshot: Zwave-JS-UI.png I followed: https://www.domoticz.com/wiki/Zwave-JS-UI I am on Synology DS420+ DSM 7.2 Debian Bullseye on virtual machine manager zstick gen5 updated to EUV1.02 ...

That seems strange. Dzvents .level should be the same as API level. Check if you have unique names. Is there another device with the same name? Dzvents cannot handle this and can mix things up. I found my error: I must ask for domoticz.devices('Store').level and not: domoticz.devices('Volet Salon ...

waltervl wrote: ↑Saturday 09 September 2023 19:31 In dzvents it should be domoticz.devices('Volet Salon').level to get the level and domoticz.devices('Volet Salon').setLevel() to set a blind to a specific level.

I tried this
domoticz.devices('Volet Salon').level
return:

• 100 for 100%
• 100 for 95%
• 100 for 65%
• 0 for close

I try to migrate my script from Lua to dzvents I use a blind percentage on a FGRM222 Fibaro zwave Domoticz is 2023.2 with OZW When I set the level to 43% with domoticz widget or physical switch In My automation script/device current state/value: Sate: Open Value 1/100 In Lua script: otherdevices ...

I use the internal System Alive Checker (15 devices) and that works fine for several years now, and is 'flexible' enough. Yes, System Alive Checker(Built in domoticz pinger) is easy to use but some can prefer code because: It is easier to copy (my case, from one domoticz to another) They want to do ...

I found a several Pinger in the forum: Built in domoticz pinger Lua pinger : commandArray = {} + os.execute('ping -c1 -w1 ' .. ip) (my old one until yesterder with possible 10s error) Dzvents pinger with s.execute('ping -c1 -w1 ' .. ip) But not the dzvents with Asynchronous shell Here is one code ...

The Z-rain stopped working at end July.
I return the z-rain to the supplier.
I bought a second hand oregon scientif PCR800 and I am testing the TFA 30.3233.01
News soon after rain...

JackD wrote: ↑Wednesday 14 July 2021 13:10 Did you try to exclude the Z-Rain from your Z-Wave network, then reset it to factory settings, then include it again in your Z-wave network.

z-rain Exclusion/Inclusion performed today. I am waiting for next rains to seeif it's better.

New erroneous value with my z-rain: 144899.1mm for July 13th! Is this a domoticz or z-rain problem? Should I send back the z-rain? I installed my TFA 30.3233.01: RFXCOM connection with pro2 firmware 1044 updated within domoticz. I compared the value with my analog rainmeter. The multiply factor is 2 ...

Which version of Domoticz are you running, I got my first troubles with Beta 13256, the did some work on rainmeters.... coincidence? Domoticz is 2021.1 The negative value was after battery replacement but 17mm rain with no detection was before battery replacement. I bought a TFA rainmeter(not ...

More and more strange:
It rained 17mm June 23th to 24th in my manual pluviometer and nothing in my z-rain
The battery were 1.35V=55% in domoticz
I replaced the battery energizer ultimate lithium
More strange today: 4.5mm in the manual rainmeter and this in domoticz+z-rain: