[Zigbee4Domoticz Plugin] new version annoucement

[pipiche]

We are please to let you know that we have just release the version 6.3 of the Zigbee for Domoticz plugin.

Most of the features added to the plugin are in relation with Texas Instrument deConz and Silicon Labs based Coordinators.

* Automatic backup coordinator (and restore)
* Network Topology based on Routing table (in addition of the neighbourg tables)
* Edition of main-powered Configure Reporting
* Reverse proxy capable of the WEBui component


In order to have a smooth transition when moving to version 6.3 and where there is no data migration, it would be good to take the following steps:

1. Stop the plugin by disabling from the Hardware Domoticz plugin list ( use the enable/disable button and press update).
2. Stop Domoticz as you will have to restart it in order to load a new plugin configuration item .
3. if you are not on 6.1.5 and you didn't use the WebAdmin Plugin Update menu, do the following
`cd Domoticz-Zigbee` (or Domoticz-Zigate for the old installation)
`git config --add submodule.recurse true`
`git pull --recurse-submodules` ( you might have to use the sudo command if you get access right issues)
`sudo python3 -m pip --no-input install -r requirements.txt`
4. Restart Domoticz
5. Go to the Hardware menu , and select the ZigbeeforDomoticz plugin.
Check that the __API bas url__ is correctly setup.
6. Enable the Plugin in order to start it.
7. Check Domoticz logs for any errors
8. Check Plugin logs ( Domoticz-Zigbee/Logs/PluginZigbee_xx.log )

[waltervl]

Just updated the plugin with the wiki instruction https://zigbeefordomoticz.github.io/wik ... gin-update

git submodule update --init --recursive

So it went wrong.....
And had to go all the way through all errors.

My advice: put the above update instruction to 6.3 stable in the wiki as it seems that i have done all steps now by learning on the way

[keros]

Thank you for the feedback. It's updated.

Sorry for the inconveniences.

[waltervl]

Again a minor improvement on the wiki manually update plugin I think.
Current wiki says

Manually
Go in your DomoticZ directory using a command line and open the plugins directory then the Domoticz-Zigate-Plugin directory.
Run: git submodule update --init --recursive
Note : Since version 6, the git pull is no longer enough.
In case you have edited/updated some of the plugin controlled file, you might get an error message protecting any update. In such situation you can reset those files with the latest version with the following commands
git reset –-hard
git pull --force
Run: sudo chmod +x plugin.py
Restart Domoticz.

It suggests that you do not need to do an git pull anymore. But you have to.
I did

Code: Select all

git pull 
git submodule update --init --recursive

Plugin update through website is not running for me as I need to do this update actions with sudo.

[pipiche]

Plugin update through website is not running for me as I need to do this update actions with sudo.

On which system/OS are you ? is Domoticz running with a normal user ?

you need to have all files own by the username running Domoticz, so you might want to do a

Code: Select all

cd Domoticz-Zigbee ; sudo chown xxx:yyy .

with xxx and yy depending on the user running domoticz

[waltervl]

I am running on Ubuntu 18.04.LTS on a X86 system.
Domoticz is running as root (installed with sudo)
I had to do all plugin git install commands with sudo the get things running.

I will try out the chown command this week.

[pipiche]

So plug-in upgrade via webUi > admin > upgrade should work then.
And as DomoticZ is running root indeed some files get own by root

[Fredom]

Dear forum members,

I'm on my test raspberry to make a clean install with Bullseye and Domoticz.
Unfortunately with zigbee4domoticz I have an error that I can't get out of.
Port forwarding is on
What am I doing wrong?
I have tried all my ip addresses and ports but I keep getting an error.

Z4D log

Code: Select all

10: Object {"0":{"Time":"19/02/2023 23:13:36","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676844851},"Thread":"MainThread"},"1":{"Time":"19/02/2023 23:13:36","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676844851},"Thread":"MainThread"},"LastLog":1,"StartTime":"19/02/2023 23:13:36","FirmwareVersion":"Z-Stack 3.30+ (build 20220219)","FirmwareMajorVersion":"20","PluginVersion":["stable6-6.3.010"]}
11: Object {"0":{"Time":"20/02/2023 15:12:11","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676902366},"Thread":"MainThread"},"1":{"Time":"20/02/2023 15:12:11","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676902366},"Thread":"MainThread"},"LastLog":1,"StartTime":"20/02/2023 15:12:11","FirmwareVersion":"Z-Stack 3.30+ (build 20220219)","FirmwareMajorVersion":"20","PluginVersion":["stable6-6.3.010"]}
12: Object {"0":{"Time":"20/02/2023 15:37:30","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>","PermitToJoin":{"Duration":0,"Starttime":1676903882},"Thread":"MainThread"},"1":{"Time":"20/02/2023 15:37:30","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://127.0.0.1:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>","PermitToJoin":{"Duration":0,"Starttime":1676903882},"Thread":"MainThread"},"LastLog":1,"StartTime":"20/02/2023 15:37:30","FirmwareVersion":"Z-Stack 3.30+ (build 20220219)","FirmwareMajorVersion":"20","PluginVersion":["stable6-6.3.010"]}
13: Object {"0":{"Time":"20/02/2023 15:39:46","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://192.168.1.15:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>","PermitToJoin":{"Duration":0,"Starttime":1676904018},"Thread":"MainThread"},"1":{"Time":"20/02/2023 15:39:46","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://192.168.1.15:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>","PermitToJoin":{"Duration":0,"Starttime":1676904018},"Thread":"MainThread"},"LastLog":1,"StartTime":"20/02/2023 15:39:46","FirmwareVersion":"Z-Stack 3.30+ (build 20220219)","FirmwareMajorVersion":"20","PluginVersion":["stable6-6.3.010"]}
14: Object {"0":{"Time":"20/02/2023 15:42:25","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://192.168.1.15:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676904177},"Thread":"MainThread"},"1":{"Time":"20/02/2023 15:42:25","Module":"DZDB","nwkid":"None","PluginHealth":"Startup","message":"Urlopen to http://192.168.1.15:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized","PermitToJoin":{"Duration":0,"Starttime":1676904177},"Thread":"MainThread"},"LastLog":1,"StartTime":"20/02/2023 15:42:25","FirmwareVersion":"Z-Stack 3.30+ (build 20220219)","FirmwareMajorVersion":"20","PluginVersion":["stable6-6.3.010"]}
LastLog: 14

Domoticz log

Code: Select all

2023-02-20 15:12:11.879 Error: Z4D: Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized
2023-02-20 15:12:11.890 Error: Z4D: Urlopen to http://127.0.0.1:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized
2023-02-20 15:37:30.278 Error: Z4D: Urlopen to http://127.0.0.1:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>
2023-02-20 15:37:30.290 Error: Z4D: Urlopen to http://127.0.0.1:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>
2023-02-20 15:39:46.586 Error: Z4D: Urlopen to http://192.168.1.15:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>
2023-02-20 15:39:46.594 Error: Z4D: Urlopen to http://192.168.1.15:8080/json.htm?type=hardware rejected. Error: <urlopen error [Errno 111] Connection refused>
2023-02-20 15:42:25.815 Error: Z4D: Urlopen to http://192.168.1.15:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized
2023-02-20 15:42:25.825 Error: Z4D: Urlopen to http://192.168.1.15:7878/json.htm?type=hardware rejected. Error: HTTP Error 401: Unauthorized

[pipiche]

I guess you have a problem which is related to the new security fashion from Domoticz.
So you have to have the IP address to be on the "trusted IP list" from Domoticz

[manjh]

I guess you have a problem which is related to the new security fashion from Domoticz.
So you have to have the IP address to be on the "trusted IP list" from Domoticz

I had some problems with this as well, had multiple IP addresses in the trusted networks field.
Found out that they should be separated by a semicolon, and NO spaces! (I had originally inserted a space for readability)
It now works OK.

[Fredom]

I guess you have a problem which is related to the new security fashion from Domoticz.
So you have to have the IP address to be on the "trusted IP list" from Domoticz

Hoi pipiche,

What I have now entered is,
login name(domoticz):password(domoticz):IP address(domoticz):port(domoticz).
Still the same error.
The plugin does work, I can add parts and they work well.

[pipiche]

Domoticz 2023.1 requires https if the IP address is not trusted. from what I saw in your log you are using only http, so make sure that the IP are Trusted.

[kiddigital]

Or if the plugin is using Basic Authentication over http (and not https) you need to enable it in the security section.

But it is more secure if you would do things over https instead of http.

[Fredom]

Domoticz 2023.1 requires https if the IP address is not trusted. from what I saw in your log you are using only http, so make sure that the IP are Trusted.

thanks for the tip

[Fredom]

Or if the plugin is using Basic Authentication over http (and not https) you need to enable it in the security section.

But it is more secure if you would do things over https instead of http.

I know that's better. But to do that is quite complicated I understand. I have yet to find an easy description for this

[waltervl]

Or if the plugin is using Basic Authentication over http (and not https) you need to enable it in the security section.

But it is more secure if you would do things over https instead of http.

I know that's better. But to do that is quite complicated I understand. I have yet to find an easy description for this

Check this wiki: https://www.domoticz.com/wiki/Native_HT ... SL_support for just using https. When using HTTPS for outside with a self signed cerificate see wiki https://www.domoticz.com/wiki/Native_se ... ts_Encrypt (also mentiond in the native https page)

[Fredom]

Or if the plugin is using Basic Authentication over http (and not https) you need to enable it in the security section.

But it is more secure if you would do things over https instead of http.

I know that's better. But to do that is quite complicated I understand. I have yet to find an easy description for this

Check this wiki: https://www.domoticz.com/wiki/Native_HT ... SL_support for just using https. When using HTTPS for outside with a self signed cerificate see wiki https://www.domoticz.com/wiki/Native_se ... ts_Encrypt (also mentiond in the native https page)

Thanks for the tip.
I will definitely do something with it.

[monette999]

See my error codes in log file

IMG_20230402_124327.jpg (247.67 KiB) Viewed 1984 times

I have similar issues with login of Solarmax Plugin with Lan
Shall I open a new tread or can you help me.

In the Domoticz Add screen I write following
admin:[email protected].

Port 50x

Is that wrong to do.

Domoticz Screenshot

IMG_20230402_124449.jpg (199.55 KiB) Viewed 1984 times

[Sjonnie2017]

IMG_20230402_124327.jpgI have similar issues with login of Solarmax Plugin with Lan
Shall I open a new tread or can you help me.

In the Domoticz Add screen I write following
admin:[email protected].

Port 50x

Is that wrong to do.IMG_20230402_124449.jpg

Please open a separate thread for your issue as it is not related to the Zigbee4Domoticz plugin.

Thank you!