david@berto.co.uk

Following Control4 dropping the CardAccess keyfobs I ordered an RF bridge, still waiting for delivery. I believe they’ll accept your existing RF remotes. Will be interested in the range. David

I have a native Google Assistant service and driver for Control4 which is currently in beta. If you would like to test then PM me your email address and I will provide details. Thanks David

No, it just does basic control of NowTV box. If I get time I’ll look at app control. Thanks

I have a NowTV driver, see https://berto.io

We use a cloud platform but its design, along with the drivers, ensures that connectivity to the Internet and the platform itself are not required for a driver to operate which I believe to be essential with any online platform unless of course the driver itself is an Internet centric driver. What issues do you have with the DriverCentral platform?

Ping me a mail and I’ll send you the sample. What is the model of the 5ch relay you are using? Thanks David

Amr, Sorry but it breaks C4 policy unfortunately.

Lukas, Not a problem. I actually do have a sample MQTT Client driver that I can email you which provides a template of how you can interface to the MQTT bridge driver, if you send me an email, I'll pass it on. Thanks David

Lukas, I've believe the problem is to do with IP Forwarding which gets turned off by my driver when OpenVPN is disabled, this happens by default when the driver is loaded. I've not be able to test fully but can see that the Navigator on the controller runs in an LXC container and requires that IP Forwarding is turned on otherwise the VM is unable to reach any network address beyond the controller itself. I've now removed this, as it is no longer needed, and will push an update, V9. The iptables changes you refer to is actually the insertion of a Masquerade rule, the same that is required for the LXC containers, so that the VPN subnet can receive traffic back from the local LAN when a client connects. Zuhair, thanks for your testing and support. You may want to check again after turning the OpenVPN server On/Off, not sure if you use or not but regardless the V9 update should sort the problem if it still exists. We don't use the master controller as a Navigator so have never seen this issue but will setup a test configuration to satisfy myself that it is fixed. Thanks for your help. Regards David

Lukas, I've also been in discussion with C4 and with agreement removed certain features from the public version of the driver some time ago. The /etc/crontabs/root entry was missed. The OpenVPN service is inbound only and does not create any tunnels, it allows users to setup their own VPN endpoint but this was disabled also. I have now removed the update to the crontab and also disabled the Watchdog and OpenVPN options on the Properties page. I've not be able to duplicate the camera issue both this version of the driver and previous versions, we have many installs using T3 touchscreen with cameras and EA1 navigators and this issue has not been reported. Can you give the setup you have to duplicate as whilst I've removed this from my public release, in the private version we still have these activated, I'd like to test. Thanks David

Amr, The setup does not sound correct. You should have the MQTT bridge installed purely to connect the Sonoff Relay driver to your MQTT Broker, you do to need to put anthingy in the Topics property on the Bridge, this is for custom message subscriptions. You should put the topic used on the Sonoff into the Topic property on the Sonoff Relay driver, in your case Control4/Sonoff/Flood, they should be identical. The driver will then pass the related subscription topics to the Bridge driver which in turn subscribes to your Broker. Glad your see stability with the Shellies, I have several RGB versions and they do appear to stop announcing now and again and need to reboot them, very strange. My Sonoff is rock solid, great kit. Thanks David

What firmware are you using and is it set correctly on the driver? Is the topic set the same on both the Sonoff and the driver?

Correct. The install.sh script does the appropriate apt-get installs and then gets the flicd daemon etc. As long as the flicd daemon can see the BT adapter then you should be good to go.

Yep, the only reason I use the Pi is for the BLE. I fixed the Hub driver so the install works. If you install a Pi 3b+ with latest Raspbian then follow the Hub install instructions it works a treat. Thanks David

I have just developed a driver for the Shelly relay range, https://shelly.cloud/product/wifi-smart-home-automation-shelly-25-switch-relay-roller-shutter/ See https://github.com/davidmassot/Berto Good piece of reliable hardware