I'm not sure what you mean by stuck, if you say that all devices works. The bottom part of web admin panel is blue and says "Startup" and doesn't change to green or whichever other colour it needs to be (depending if it needs update or not). Also, network topology scan doesn't work. It says in the ...

ANy error in the Domoticz logs ? I don't see any issues in the plugin logs I suggest that your remove all of the OTA firmware if there are not needed ... No errors in domoticz log... Status: PluginSystem: Started, Python version '3.8.10', Is the python version a supported one? Could the OTA files ...

Hi, After the last upgrade the Z4D plugin is stuck in "Startup" mode, as seen on the web administration interface (picture). Plugin: 7.1.009 [4.237] Domoticz version: 2023.1 (build 15254) Any idea why it's stuck in Startup mode? I tried the Network Topology scan, but it did not execute anything. All ...

For now, I wouldn't change much, because I'm waiting for a sample from Sonoff, so I can cleanup the integration. And last I still don't see any plugin rationals to get some confusion. The only thing I can think is that with the branch we were pushing some settings to the Sonoff device (like ...

JanZorz wrote: ↑Monday 05 February 2024 20:16

pipiche wrote: ↑Monday 05 February 2024 16:28

If you could just change in the code that the Sonoff uses the Presence and not Motion for flipping the switch we could say that the basic functionality works...

Cheers, Jan

Pipiche - would this small change be possible? That would render the Sonoff sensor usable.

Cheers, Jan

can you try the following switch to stable7 git checkout stable7 sudo python3 -m pip install -r requirements.txt --upgrade the restart the plugin in that context you won't get the recent changes for the Sonoff, but the basic functionallity should work. how does the Aqara vs. Sonoff behave Now the ...

If I switch off (disconnect) Sonoff sensor but do not disable it in the Z4D web admin panel - the Aquara sensor still doesn't work. I'll do more tests today. Cheers, Jan Hum, the fact that the Aqara sensor doesn't work, as nothing to do with the Sonoff presence sensor. Did you try to put the plugin ...

I got the documentation, and they are mentioning that you need to be carreful when 2 Presence sensors are in the same room are close to each other, because they can impact the other one. If you switch off all and you keep only one, do you still see strange behaviour ? I took the Sonoff presence ...

I have disabled the SonOffUltrasonicIllumination in the recent push can you try how does it behave ? Same problem... and it's clashing/affecting just just one other motion sensor, not all of them. I have a feeling that we pushed something into the SNZB-06P that is causing problems. Is there any way ...

pipiche wrote: ↑Friday 02 February 2024 16:13 I have disabled the SonOffUltrasonicIllumination in the recent push
can you try how does it behave ?

Testing...

Cheers, Jan

Sorry, didn't see your post. Ok, I'll set the Fading Time to 60 by default. For the others I do not have any documentation. I set the default as the one I got from you (after the pairing). If that is find for you I would push this branch onto the Release Candidate for 7.1.009. Let me know what you ...

just pushed an update on the that branch you can try the following parameter "SonOffUltrasonicIllumination": 1 bright, 0 dim As usall, when you change the parameter value and you validate twice ( once on the pop-up window, and then once in the page top-right), it could take couple of seconds to ...

pipiche wrote: ↑Thursday 01 February 2024 16:07 That is a good news.
There is an attribute that sonoff named Illumination, but I don’t what it is.
Can we get de device illuminated when presence ?

Yup, got some light on the device now - what type of export do you need?

Cheers, Jan

Done. I have merged the changes on the 'tuya-motion-radar-parameters ' the parameters to play on the SonOff are: { "UltrasonicOccupiedToUnoccupiedDelay": 60, "UltrasonicOccupancySensibility": 1. ( can be 1, 2 or 3) } You can use the debug parameter occupancySettings to get a bit more log. To debug ...

{ "TuyaFadingTime": 2, "SmallDetectionSensitivity": 1, "MediumMotionDetectionSensitivity": 1, "LargeMotionDetectionSensitivity": 1, "SmallDetectionDistance": 0, "MediumMotionDetectionDistance": 8, "LargeMotionDetectionDistance": 1 } Do you have any idea what the ranges of those parameters might be ...

pipiche wrote: ↑Wednesday 31 January 2024 17:24 could be related that the plugin use the Motion and not the Presence.

I don't have the device myself, and the other user I started the integration for is not responding anymore

Can you add those changes to yuya-motion-radar-parameters branch and I'll tell you if it works?

Cheers, Jan

Yes, I know and I'm working on that one as well, but on a different branch. So I suggest that we finished the 1st one and then we can move to the Sonoff. However would be interested to know what is not working properly ? Sensor is sitting on my desk in front of me and despite the fact that I'm here ...

The logs sound ok, they are many data points provided by this device, and someone of them are unknown The sensor still works, I'll play with the settings in the evening. While we are at it - I also got the Sonoff SNZB-06P presence sensor now in my network that is not properly implemented yet in the ...

Have fun and let me know how it goes. Probably the best is of course to do it one by one. When you change a parameter the change is not necessarly immediate. Check eventually the plugin log, you should see some messages like 2024-01-30 20:37:14,229 INFO :b'sanity_check_of_param TuyaFadingTime, 60 ...

pipiche wrote: ↑Saturday 27 January 2024 10:12 Woudl appreciate if you could drop here an export.json :

WeUI > Tools > Plugin Raw Devices

Export attached. The presence sensor device id is 28, ZDeviceName: "Presence sensor - Kopalnica".

Does that help?

Cheers, Jan