Jump to content
C4 Forums | Control4

david@berto.co.uk

c4Forums Member
  • Posts

    234
  • Joined

  • Last visited

  • Days Won

    1

david@berto.co.uk last won the day on June 12 2022

david@berto.co.uk had the most liked content!

5 Followers

Recent Profile Visitors

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

david@berto.co.uk's Achievements

Community Regular

Community Regular (8/14)

  • Dedicated Rare
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

48

Reputation

  1. This is now fixed. The latest beta 4.2 is a complete rewrite of my MQTT client from the ground up. I've tested connecting to Mosquitto 2.0, unencrypted and over TLS, unauthenticated and using authentication, support over WebSockets and all levels of QOS. You can test connections using https://test.mosquitto.org and https://www.hivemq.com or use your own broker. Whilst the client can connect to the local controller broker I do not advocate this or any chnages to the local mosquitto configuration. A broker on a Pi takes less than 5 minutes to setup. The v2 drivers are still in beta but I hope to release a production version soon, time permitting!! Available at https://beta.berto.io/c4z
  2. All drivers are available are https://beta.beta.io/c4z Still WIP but LIFX and Wiz should be ready soon with Color support.
  3. Yeelight has a rate limit on the requests sent to a bulb. The Color wheel sends requests at a higher frequency than simple on/off and level commands. I suspect the issue you are seeing is the quota restriction on the Yeelight bulb rather than the driver.
  4. This does not look as though the driver has installed correctly. I would delete from project and also /mnt/internal/c4z on the controller and then try again. You should get the drivers from https://beta.berto.io/c4z and change the Release Branch to Beta under Core Configuration in the Berto Agent driver. Thanks
  5. Not sure ref Chowmain driver but think it should be ok to run along side as the Berto driver uses the LIFX LAN not the cloud API. I’ve just pushed a first release with Color support etc. Ready to test and available at https://beta.berto.io/c4z
  6. Amr, v2 will replace v1, in fact I’ll probably make v2 OS 3.3.0 and above only given the great new features with native colour wheel support etc. I’m in the process of adding colour support now. The Mosquitto MQTT broker is bundled with OS 3.3.0 which is fantastic news and a native C4:MQTT() client to interface with. All brilliant additions. The v1 drivers will still work but I’ve stopped development on them. The Cloud driver is replaced by Berto Agent which does all Cloud did and more. No need to register, no restrictions, support for Email, Pushover, MQTT, REST, IFTTT all built in and more. The Gateway driver is being broken out into individual hub drivers eg. LIFX, Shelly, Tasmota, Yeelight, TP Link and Zigbee2MQTT is work in progress. I’ll probably create HA and HomeKit but leave GA and Alexa out, the C4 options are great now. A lot to do and only me to do it unfortunately but I’ll keep you updated. Cheers David
  7. Once OS 3.3 is released I'll add Color Wheel support to the Dimmer driver also. I'm in the process of pushing a v2 release of my drivers which will eventually supersede all v1 drivers. The new Agent driver now has many features bundled in that replaces previous v1 drivers such as IFTTT, Pushover, MQTT, Mail, REST/HTTP Webevents, OwnTracks... See https://berto.io/v2
  8. My Berto Agent driver, https://prod.berto.io/c4z/Berto_Agent.c4z, provides the ability to programatically Refresh Navigators.
  9. The LIFX driver uses the LIFX LAN Protocol, https://lan.developer.lifx.com, so does not use the LIFX Cloud to manage the devices. You do not need Internet access for the driver to work. You do not need any additional hardware such as a Pi for it work. You need to install the Berto Agent driver first, https://prod.berto.io/c4z/Berto_Agent.c4z, and then you can install the Berto LIFX driver from the Feature Management property or download from https://prod.berto.io/c4z Thanks
  10. The Agent driver will attempt to re-connect to the MQTT Broker if it misses a keep alive. Update to Berto Agent Beta 1.3 should fix this issue. You need to have the Keepalive & Timeout set in the Broker configuration. Have you written your own driver to use the MQTT client in the Agent?
  11. You may want to look at the v2 release of my drivers which are still in beta but ready to test. They do not require registration and there is no need for a Premium licence to run multiple instances of the same driver, as with the v1 release. The main driver, a new agent driver called Berto Agent, will provide the ability for any developer to write there own drivers and integrate with features such as MQTT, Mail, IFTTT, Pushover, REST interfaces, installing and renaming drivers etc. I’ll also be providing some example drivers with source code showing how to integrate with Berto Agent. The REST Interface also allows updating of Profile locations from the OwnTrack app or using curl. Effectively this means you can create your own integrations using MQTT. The Berto Agent driver does not need to connect to any authorisation servers to work. Connections are still made to the Berto Cloud but only to use the additional services such as MQTT, Email, IFTTT etc. Find enclosed link to initial release of v2 beta drivers, https://beta.berto.io/drivers. You need to install the Berto_Agent.c4z driver first as an Agent driver in Composer ie. From the Agents tab. See the docs on Berto Agent to explain basic use etc. Source code is provided with the Berto_MQTT.c4z and Berto_Mail.c4z drivers. The other drivers are free to use. Thanks David
  12. The Sky Q boxes will not respond to ICMP requests. You can try an nmap and see what open ports there are, it should something like :- Host is up (0.0030s latency). Not shown: 983 filtered ports PORT STATE SERVICE 80/tcp open http 1234/tcp open hotline 5000/tcp open upnp 5001/tcp closed commplex-link 6000/tcp closed X11 6100/tcp closed synchronet-db 8008/tcp open http 8080/tcp open http-proxy 8081/tcp closed blackice-icecap 9080/tcp open glrpc 9091/tcp open xmltec-xmlmail 9998/tcp closed distinct32 9999/tcp closed abyss 49153/tcp open unknown 49155/tcp open unknown 49160/tcp open unknown 49163/tcp closed unknown You can wget or curl the Sky Q box direct, in your case :- curl http://192.168.0.201:9006/as/system/information This should return your info on the Sky box, if not then you have a network issue.
  13. PM me you email and I’ll send you SDK details. v2 is still beta but the area your looking to develop in, MQTT, is complete.
  14. Mitsubishi uses it’s own M-NET bus protocol. CoolMasterNet connects onto the same bus, see http://www.coolmasternet.co.uk/CoolMasterNet.html The drivers are in the Control4 databases, https://drivers.control4.com/solr/drivers/browse?&fq=manufacturer%3A"CoolAutomation" Works a treat.
×
×
  • Create New...

Important Information

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