when you switch back the firmware back to 0223 did you do the Erase EEPROM (and then Initialize it with the plugin ) ? That would be a must when changing from OPTIPDM to Legacy and also when downgrading. Consequently, you'll have to repair all devices Yes i have erased eeprom, at the beginning of ...

I reinstalled the firmware and plugin today, back to legacy 0323. At first i could pair nothing. I set the devices in pair mode, zigate in accepting hardware, but zigate finds nothing...not the switches, not the lightbulb, not any device. Rebooted a couple of times. Now i can pair devices. But still ...

Today i updated the Zigate plugin to 6.3.012 and one of the 2 bulbs i tested is working now. The other one still giving the error.
They are excacly the same model. I dont know what to do, i think i'm going to reinstall the firmware.

Thank you for responding.

Yes i have read that too. But because it is a new firmware and database. i have only one group, it is the 0000 group. and only 2 devices connected.

Sadly i can not find anything useful on the internet.

Should i go back to the old firmware to test if it is a bug?

Ok I tried Provisioning-> 'Prepairing device for full reset', deleted the widget. Reset the bulb, and then repaired it. It did not create widget anymore, but i can put it on and off with the zigate's tools-> commands now. Wich i could not do yesterday Recreated a widget with Provisioning - Recreate ...

Did you fix this problem? I get allmost the same errors with aqara bulbs 2023-03-13 20:29:54.920 Error: Zigate: Decode8000 - PacketType: 00e0 TypeSqn: 01 sqn_app: 00 sqn_aps: 7a Status: [06] 2023-03-13 20:32:00.550 Error: Zigate: Decode8000 - PacketType: 00e0 TypeSqn: 01 sqn_app: 00 sqn_aps: ba ...

The first bulb that failed was a E27 Now i tried to pair a E14 bulb. And the log was filled with the same response.... After 2 minutes i tried to repair it again. And now i have a error too. The log is so long i cant scroll back anymore, but is i filter on errors, i get two errors 2023-03-13 20:30 ...

I had problems with my Zigate USB, there was a error, witch i do not remember. But after a long search i find somewhere that there was a possibility that the ?PDC? was corrupted. I tried to fix it and then i broke my pi OS... :roll: A good time to start fresh. So i have a new pi OS installed and ...

That did not work too. I will reinstall again. [emoji28]

Verstuurd vanaf mijn SM-G991B met Tapatalk

even the var/www/ directory is gone and still getting the apache webpage.... (cookies cleared)

Tank u for a answer. I fully removed apache. The files you are talking about do not exist anymore.

Verstuurd vanaf mijn SM-G991B met Tapatalk

Because my pi 3 died I have bought the pi 4 and start the installation. For using controlllicz I installed the certificate with certbot. But I used the wrong command. I used auto certbot for apache. And now if I use my domain name I get on the apache site. I think the auto install made a change to ...

After a year of good work, the notification has stopped completely. In the log it says notification succeed. But nothing happends. Am i the only one?

okey, thank you!

Today the notification was translated to english, but my systems works on dutch, it was very funny. I was happy, because the speech was finally working again. I found out that domoticz was displayed in english too. I put my domoticz back in dutch, and the speech was stop working again. I hear a ...

thanks, i have changed my versoins of pychromecast and Zeroconf. somehow in english it work, but in dutch language it is not working

I get errors in my zigate. There is a red warning icon in the dasboard. But i can not find what i can do about it. Does someone undersatand what is in the logs and what i can do about it?

I have tried your version. With .afterMinutes. It does not work properly because it only activates when the sensor is detecting motion. Maybe i can fix it with a variable that update +1 when te timer get on 4 min or above. And if the variable gets on 2 the lights go off. So that is between 5 or 8 ...

Thanks! I merged it right now! ( i will look into the difference between dz.log and print later) I thought i found in the video somewhere i could rename the function. But i did not used it properly because i have two triggers. I will stay with the variables untill i understand it better. Thank you ...

I'm sorry, i thought did understand :roll: 2021-02-03 14:21:00.604 Status: dzVents: Info: schuur logic: ------ Start internal script: Script #2:, trigger: "every minute" 2021-02-03 14:21:00.629 Status: dzVents: Debug: schuur logic: Processing device-adapter for Schuur: RGB(W) device adapter 2021-02 ...