@gizmocuz If there is a new "stable" build every day, you expect all users to update every day? So how do you expect/promote all users to be close to a recent release? In January 2024, we had 5 stable releases during the month. I would say that was a bit too much. People where starting to wonder ...

I know that the idea is to help the developpments by reporting issues but, i think that most users prefers to have a "stable" version for their home automation system. By default, DomoticZ is configured to folow the stable releases. Without stable release, the general users are left behind. Why not ...

Hello

The 2024.6 was released in july 8th 2024 and the latest stable 2024.7 was released a few days after (on 13th july 2024).

I saw gizmocuz giving this info :

gizmocuz wrote: ↑Sunday 30 March 2025 8:29 And 2024.6 is very old! Time to update

Whats is now the idea about stable releases ? Are they stopped ?

@Rik60, the sudo command is normal.

Can you please run sudo python3 -m pip install -r requirements.txt --upgrade and paste here the results of the command ?

@jacobsentertainment, it we be complicated to solve two problems in the same topic. Can you please open a new one ?

Can you put a screenshot of your DomoticZ plugins parameters page with the plugin selected in order for us to see the parameters ?

i have tried the same plugins as i use for the zigate, but it doesnt seem to work, i get these error messages: 2023-12-09 00:16:44.073 Error: Sonoff: - unplug/plug the zigate 2023-12-09 00:16:49.055 Error: Sonoff: Plugin is not started ... 2023-12-09 00:16:49.055 Error: Sonoff: - Communication ...

Lets say you tried the thing with this order : n°1, n°2, n°3. n°1 is working and not n°2 and n°3. Can you erase all the device from DomoticZ and the plugin and try pairing with another order : n°2, n°3, n°1 (make a plugin reboot between each pairing). If it doesn't work, redo the erase and make the f ...

Have you check the Custom tab in the user parameters ?

It is solved with the latest versions of DomoticZ and the Z4D plugin. Thank you.

I am running the developpment branch with the check of version.

I looked at the source, and it seems that the plugin check the API version and use the old or the new call api. I tried to stop the plugin : almost all the errors stopped, but it is not necessarily the plugin fault. Perhaps it is something using this device and if the plugin is stopped, the device ...

@kiddigital, the request was from 127.0.0.1 so it doesn't help a lot. @Kedi, thank you very much for the explainations. I have isolated the logs : 2023-06-18 11:34:28.970 Status: [WebServer] Depricated RType (devices) for API request. Handled via fallback (getdevices), please use correct API Command ...

Just enable the `webserver` debug flag and you will see a lot more details from the webserver. Where do you do this ? I have about 4 error by minutes and I can not figure out where it comes from. I checked all my scripts, all the scripts links inside the devices, all my external script. I see ...

Thank you for the feedback. It's updated.

Sorry for the inconveniences.

Did you open the 8080 port during the installation ?

Have you tried 192.168.0.200:8080 from your Windows PC ?

I think you have a mistake in the plugin parameter : for the DomoticZ API Port,your screenshot shows http:127.0.0.1:8443 with is the port define just underneath for the plugin WebUI. It should be the DomoticZ port (8080 by default).

keros wrote: ↑Thursday 24 February 2022 21:25 Can we add this information on the Wiki ? I'll add a link to this topic.

We put the information there : https://zigbeefordomoticz.github.io/wik ... ation.html

Sorry for the delay, we waited for stable6 release

Same issue for me with DomoticZ stable 2022.1 on a Raspberry 3B+ with Python 3.7.3.

The name of the html file is the name of the menu

So, if you have a ZiGate coordinator, you can call it ZiGate.html, ZiGate2.thml, Plugin Z4D.html, or whatever you want