Seeking Advice:

[rafale77]

I deleted your double post... Yeah not sure what is going on and what setting could possibly cause this. Maybe try power cycling the switch to see if it goes away? It seems to be stuck somehow.

One other thing to look at is whether you have a scene somewhere trying to send commands to this device at a high frequency since I am seeing also a number of NONCE get calls issued by the controller. Something must be triggering it.

[PerH]

Looked through, and it looks like this is a common thing for all the mains powered units attached secure. a lot of "nonce activity"!

Here's a different fibaro unit:

I can't see why they would have so much back&forth with this, and i don't have any scenes at all, just reactors. And this seems to happen at a steady pace, there's not that automation going on here.

Can you show an example of this "nonce" message communication at your setup?

[rafale77]

I basically see none of it unless a scene triggers them. I for example have an Aeotec HEM which is securely included and I see the exchange when it reports the values of the HEM. I see this also when I trigger a switch on and off or when I trigger a security sensor. It is always connected to an action. Is it always the same type of device?

[PerH]

I think i might have found the "nonce" culprit!
the app "Periodical Sensor Polling" in z-way was set up to poll all devices every 10 minutes.. Why would one want that if the sensors always sends an update on changes (configured on the device)?

[PerH]

I finally made the Domoticz link work, and then ported all Zigbee devices to the much better zigate plugin there. No change in latency at all, very sharp responses to door and motion sensors. Happy!

This plugin has its own GUI, and is almost structurally standalone. I've contacted the developers to ask if its possible with a direct API and to run it as a service to cut domoticz out of the chain..

I can now confirm that TRADFRI and Aqara will work together just fine, with repeaters helping for both systems:

[rafale77]

I have to applaud your resilience in finding yet a novel integration of zigbee into openLuup. I looked at it a while ago for just a few minutes before giving up with the thought that the plugin was broken and moved on to something else.
In many ways I envy your integration. I came to realize that I had mentally split my setup into 2 major controller categories:
The local, z-wave and zigbee which needed to be stable, fast and 100% reliable, almost never requiring any updates.
The cloud side which I tried to minimize to the very essential and would constantly require updates due to cloud APIs changing.
I partially failed by running my zigbee on home assistant which also is my cloud integration portal and is constantly getting updates. You just did exactly what I wanted to do...

[therealdb]

@perh well, there’s space for using it directly, but looking at the code, it’s referencing domoticz, so it may be not so easy to do.

[PerH]

@therealdb: Yes, it would definately require some writing on the plugin, but then it would also open for more users.. we'll see!

There is some really good plugins and features in Domoticz as well, so its OK even if the plugin stays attached to it, as long as the performance stays good. Next plugin for me to install now is the Xiaomi Vacuum.

[PerH]

Finally starting to get the docker thing here, and currently i've got z-way 3.1.3, domoticz and miio-server (for the vacuum) running in dockers. Nice to se that there's no performance reduction with this either. I'd also like to get grafana and influxdb into dockers.

Plan now is to have some daily backup routine. I was thinking mabye just to have Reactor do os.execute cp -rf <docker volume folder> <backup folder on SSD> sometime at night. Any thoughts?

[toggledbits]

Per, how are you planning to handle daemonizing? I've been playing with docker-compose, which seems a good way to remove the need to have a command line with a lot of error-prone parameters that users must type.

[PerH]

Yes, i've made a docker-compose file that brings up all the dockers and set them up on the same internal bridge network with static IP's. Then all intercom is done with the same IP's on any hardware, so theres not much to set up other than copying in the volume backups.

Daemonizing was a new word for me, in this context you were referring to automating the install, right?

[toggledbits]

By "daemonizing" I mean starting them as a daemon, which is in Unix parlance a console-less process that runs in the background (a service, if you will).

[rafale77]

The closest I have come to this has been running them as systemctl services. My single VM actually runs everything that way. I did so for MSR as well but no docker for me. You can put all of these command within the service file? I am actually autostarting all of my services in a sequence with dependencies: example: Do a socat reload before starting z-way. Then when z-way is up start openluup then start habridge then start homekitbridge... etc...

[PerH]

Well, as long as you state restart policy "restart: always" or "restart: unless stopped" in the docker-compose file, it will start that container on reboot as long as the docker daemon itself starts.. docker installed itself as a service, so i haven't thought about it really.

Just to have it said; the docker-compose is just a script to rig up the containers with the correct settings. This is done once, after that the restart policy you set for the containers decides how they will live from there. you can set up as many containers as you like in one compose file.

[PerH]

@rafale77
Haven't thought about dependencies, all the stuff i'm linking together handles if one is missing.. you can set up Startup and shutdown order in the compose file, so i guess that is the docker way to handle it?

[PerH]

I finally reached the finishline for the move-to-docker project!
All applications are now inside dockers, communicating on the internal docker network.

This makes updates easy - just update to a newer docker image. (or update in the app, in the openLuup case)

Backup is done by copying the docker volumes to an SSD along with the indluxDB.

Restore to any machine running docker is in principle just attaching the USB devices - install ser2net, and running one docker-compose file. Everything is set up and ready to go. Tested on an Ubuntu installed machine, and it works!

This will offcourse take a bit more disk-space, havent summed it up yet.. But i have no plans on running this on machines with tiny storage anyway.

One thing i'd like to improve is to get the UZB into Ser2net as well, with the advantage of accessing it from my test-system as well. Z-Way unfortunately can't take IP-serial without Socat? mabye in later updates.

I made this sketch to keep track of the system in progress, it might be usefull to others?

[akbooer]

Really enlightening.

BTW, Where do I go to find out more about “the internal Docker network”. I’m having no end of problems with openLuup not identifying incoming IPs correctly.

[PerH]

I found my info here, and lookung at other docker-compose files. I've only set up a standard "bridge" network, theres more advanced methods available as well. I found that giving the containers static IP worked for me.
You can do that in a run command, in compose or manually in portainer (but that will be gone in a reset of the setup). I'd recommend docker-compose!

[rafale77]

@perh

I am using using my UZB over IP. You do need ser2net on the UZB host but you can then get anything, including socat, to pick up the socket.

[PerH]

But Z-Way needs an address to a device right? haven't looked into it.. tried to put in ip:port, didnt work..