Jump to content
C4 Forums | Control4

david@berto.co.uk

c4Forums Member
  • Posts

    234
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by david@berto.co.uk

  1. On 5/27/2019 at 3:05 AM, Pounce said:

    Your question doesn't make sense to me. The firmware mentioned for the bridge supports MQTT. As you know that is sort of generic. Davids driver has nothing to to with the bridge.

    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

  2. 14 hours ago, jcmiro said:

    I was wondering if I added a samsung smart hub to my apartment if it would recognize the z wave light switches? Would I have to call my C4 guy to install it....Just installed a somfy mylink and got my curtains and blinds going so Im kinda on a DIY run.

    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

  3. 5 hours ago, ILoveC4 said:

    Agreed. I just think DriverCentral is a terrible platform and unfortunately, if that’s the only way to buy them I won’t be buying any. It’s a shame. Same with Alans stuff - several I’d love to buy but (unless I’m missing something) that platform just does not work for me. 

    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? 

  4. Just now, lukas.polivka said:

    Hello David,

    thank you for addressing the issue so quickly. I was (and still am) unfortunately overloaded with our dealer training so I was not able to reply with updates in timely manner.

    You got it right - only the navigator on the primary/director EA controller was affected. Slave controllers and T3 touch screens were unaffected.

    I've documented the whole troubleshooting process on the official Control4 dealer forums I've linked in the original post. Not sure if you have access.

    As for the 'backdoor-ish shenanigans' - I was almost certain the intent was not malicious (you wouldn't have made a backdoor so obvious), but it sure did raise my suspicions as such modifications of the controller/OS by drivers are highly… *unusual*.

    Looking forward to using your drivers again. Any plans to document the binding/'API' for the MQTT driver so we can develop 3rd-party device drivers?

    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

  5. 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

     

     

     

  6. 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

     

  7. 10 hours ago, Amr said:

    Tasmota firmware, Topic on Sonoff is Control4/Sonoff/Flood, On Berto MQTT driver topic is Control4/#, all Shelly’s are working no issue whatsoever, Sonoff’s require programming I believe, I did couple of programing routines as per your posts but cannot get it to work? So what to review and do I need Nodered to troubleshoot? Also the driver have 4 connections for Sonoff basic I used channel 1, so is this correct?

    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

  8. 4 hours ago, Amr said:

    All Shelly's are working beautifully without any issue or programming, on the other hand Sonoff's are a pain in neck, can't seem to get a basic On/Off light to work with them? I used most of the steps described, not working, am I missing anything?

    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?

  9. 9 hours ago, sthembiso said:

    I assuming the UDL number I  must ask from installer Gary? 

    I think there was a point where I inserted a 1234 UDL. Got a connected status on composer but couldn’t go any further

    With the latest C4 driver using the new security proxy you need Texecom firmware version 4 or above.

    The UDL code is only available from the Engineer's menu so you will need the six dight code to access that or hope your installer will share it with you.

     

  10. On 2/24/2019 at 12:37 AM, AdamD said:

    Hey David,

    I am loving your drivers! Really awesome work! I have just setup the MQTT Bridge which is working great with my Sonoff devices and Mosquitto Broker running on a Raspberry Pi.

    Is the "KeepAlive Age" suppose to count up beyond 60 if no packet is received? I'm sure I saw it count up beyond 60 once but it now seems to reset to 0 when a KeepAlive packet is sent even if no response is received.

    I wanted to send a push notification to my phone via the C4 app if the C4 loses connection with the Broker. I was hoping to use the "KeepAlive" variable and send a message if KeepAlive > 300 for example. However when I watch debug the "KeepAlive Age" always resets to 0 after each "Keepalive Packet Sent" even if it doesn't receive a "KeepAlive Packet Received".

    Is this how you intended it?

     

    Adam,

    V4 available and working as you suggest.

    Thanks

    David

  11. 6 hours ago, AdamD said:

    Hey David,

    I am loving your drivers! Really awesome work! I have just setup the MQTT Bridge which is working great with my Sonoff devices and Mosquitto Broker running on a Raspberry Pi.

    Is the "KeepAlive Age" suppose to count up beyond 60 if no packet is received? I'm sure I saw it count up beyond 60 once but it now seems to reset to 0 when a KeepAlive packet is sent even if no response is received.

    I wanted to send a push notification to my phone via the C4 app if the C4 loses connection with the Broker. I was hoping to use the "KeepAlive" variable and send a message if KeepAlive > 300 for example. However when I watch debug the "KeepAlive Age" always resets to 0 after each "Keepalive Packet Sent" even if it doesn't receive a "KeepAlive Packet Received".

    Is this how you intended it?

     

    Adam, 

    I'll look at changing this to update on receipt of last PINGRESP packet. That makes more sense.

    Thanks

    David

  12. 2 hours ago, christophe@soundimage.be said:

    Hi David,

    Not Loosing MQTT connection anymore, but still loosing my programmation under "When A General Message is Received"... really don't know why...

    Outgoing programmation stay ok

    Thanks

    Mmm, not sure what would cause programming to disappear, that's a new one on me.

    How are you updating the driver?

  13. 3 hours ago, NextGenAV said:

    Thanks David,

    That's seems to have done the trick. Didn't see in documentation (which means it may be obvious and I'm dumb), what is the difference between DEVICE MESSAGE and GENERAL?

    Cheers.

    Great.

     The GENERAL_MESSAGE_RECEIVED event is fired when a message is received on the one of the topics specified in the Topics property whilst the DEVICE_MESSAGE_RECEIVED is fired when a message is received on the topic from a specific bound device such as the Berto Sonoff Relay.

  14. 17 hours ago, NextGenAV said:

    Hi David,

    Not sure if something has changed with the driver or it's me, but I'm not seeing messages from topics on the MQTT Driver properties page. The Sonoff relay driver is showing connected to broker and control works.

    I'm using a Pi as a MQTT broker running Mosquitto (no username or password) and Node-RED for testing. Node-RED shows the messages from Control4 in debug but sending messages from Node-RED shows nothing in the driver. Topic subscribed is cmnd/#  (Sonoff with Tasmoto firmware)

    Only started messing about with it on Thursday and same settings were working then ... 

    Great driver!

    Please update to V2, see https://github.com/davidmassot/Berto/blob/master/src/Berto_MQTTBridge/README.md.

    Thanks

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.