Jump to content


c4Forums Member
  • Content Count

  • Joined

  • Last visited


About david@berto.co.uk

  • Rank
    Control4 End User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. Thanks. Applied patch, event though already on latest 2.10.6 and 24 hours later all my remotes now show 2.1.117, automatically updated from 2.1.109.
  3. I have the same issue on several sites. I can not see the article you are referring to on the support link at all. I’m on EU site so not sure if that is different. Could you post a link to the actual article? Thanks
  4. I've bought several of the UE75NU7100 and 65 versions in the UK, specifically as they are supported by C4, but none of them have the IP Remote option so have had to resort good old one way IR. Not a C4 problem but more Samsung model variation in the UK despite the model number being totally supported by C4. Why do manufacturers do this!
  5. Adam, V4 available and working as you suggest. Thanks David
  6. Vert interesting! Will take a look.
  7. Adam, I'll look at changing this to update on receipt of last PINGRESP packet. That makes more sense. Thanks David
  8. Any beer. Is the issue fixed? Thanks
  9. Problem duplicated, will investigate.
  10. Mmm, not sure what would cause programming to disappear, that's a new one on me. How are you updating the driver?
  11. I stumbled across this earlier and thought you may be interested. My Berto IFTTT driver, https://github.com/davidmassot/Berto/blob/master/src/Berto_IFTTT/README.md, enables secure HTTPS connections direct to the Control4 director, an IFTTT webhooks driver using an SSL server on the Control4 side. I have a library that handles HTTP and HTTPS server connections so creating an SSL version of the web events driver would be relatively straight forward but given IFTTT I've never really bothered about it but if there is a requirement... MQTT is also covered, see https://github.com/davidmassot/Berto. Thanks David
  12. 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.
  • Create New...