david@berto.co.uk

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

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

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
 

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

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
 

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
 

My Berto Agent driver, https://prod.berto.io/c4z/Berto_Agent.c4z, provides the ability to programatically Refresh Navigators.

My Berto Agent driver, https://prod.berto.io/c4z/Berto_Agent.c4z, provides the ability to programatically Refresh Navigators.

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. 

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. 

Hi all,
I've just released version 1.27 of my IoT Gateway driver which has been opened up to allow other driver developers to access the MQTT functions.
Just a few simple proxy functions to REGISTER and PUBLISH messages and ExecuteCommand handlers to receive MESSAGEs.
Driver available at https://prod.berto.io/download/Berto_IOTGateway.c4z
Sample driver with source code showing integration available at https://prod.berto.io/download/Berto_IOTClient.c4z
Thank you
David

Hi all,
I've just released version 1.27 of my IoT Gateway driver which has been opened up to allow other driver developers to access the MQTT functions.
Just a few simple proxy functions to REGISTER and PUBLISH messages and ExecuteCommand handlers to receive MESSAGEs.
Driver available at https://prod.berto.io/download/Berto_IOTGateway.c4z
Sample driver with source code showing integration available at https://prod.berto.io/download/Berto_IOTClient.c4z
Thank you
David

A major updating adding support for many more devices including TP-LINK and Yeelight.
Zigbee is now supported on the Sonoff Zigbee Bridge and Zigbee2MQTT installs.

The new IoT Gateway driver supports automatic downloadable plugins which means new devices no longer need a driver update.  As new devices become available the driver now checks it’s online database for a supported plugin and downloads as required.
Custom MQTT messages can now be posted to a RestFUL API endpoint to process payloads and return name/value pairs to feedback variable updates to Control4. Process messages and return updates in your own framework and language of choice on your own server.
Performance enhancements to the MQTT client has improved scalability and currently systems with 100+ Tasmota devices and 130+ Shelly devices are running in commercial production environments.

Tasmota 9.2 is now supported although Zigbee support appears more stable with 8.5.1.
A director restart is required.
This is a significant update and in some cases, dependent on devices in use, it may be necessary to clear exiting devices and setup again.
A vey big thank you to all those who provided beta testing, you know who you.
 
David

A major updating adding support for many more devices including TP-LINK and Yeelight.
Zigbee is now supported on the Sonoff Zigbee Bridge and Zigbee2MQTT installs.

The new IoT Gateway driver supports automatic downloadable plugins which means new devices no longer need a driver update.  As new devices become available the driver now checks it’s online database for a supported plugin and downloads as required.
Custom MQTT messages can now be posted to a RestFUL API endpoint to process payloads and return name/value pairs to feedback variable updates to Control4. Process messages and return updates in your own framework and language of choice on your own server.
Performance enhancements to the MQTT client has improved scalability and currently systems with 100+ Tasmota devices and 130+ Shelly devices are running in commercial production environments.

Tasmota 9.2 is now supported although Zigbee support appears more stable with 8.5.1.
A director restart is required.
This is a significant update and in some cases, dependent on devices in use, it may be necessary to clear exiting devices and setup again.
A vey big thank you to all those who provided beta testing, you know who you.
 
David

A major updating adding support for many more devices including TP-LINK and Yeelight.
Zigbee is now supported on the Sonoff Zigbee Bridge and Zigbee2MQTT installs.

The new IoT Gateway driver supports automatic downloadable plugins which means new devices no longer need a driver update.  As new devices become available the driver now checks it’s online database for a supported plugin and downloads as required.
Custom MQTT messages can now be posted to a RestFUL API endpoint to process payloads and return name/value pairs to feedback variable updates to Control4. Process messages and return updates in your own framework and language of choice on your own server.
Performance enhancements to the MQTT client has improved scalability and currently systems with 100+ Tasmota devices and 130+ Shelly devices are running in commercial production environments.

Tasmota 9.2 is now supported although Zigbee support appears more stable with 8.5.1.
A director restart is required.
This is a significant update and in some cases, dependent on devices in use, it may be necessary to clear exiting devices and setup again.
A vey big thank you to all those who provided beta testing, you know who you.
 
David

After several months of beta testing my new IoT driver suite I’m ready push a production release scheduled for the 5th June.
There are some significant changes to the way the main IoT Gateway driver works and as such I’m advising existing users of these drivers to turn Auto Update Off on all Berto drivers so that you can control when, or if, you update to the latest release.
Details of the update will be available at https://berto.io/c4z/Berto_IOTGateway/www/README.html but to provide a quick flavour...
Support for devices running Tasmota firmware, native support for Shelly and Sonoff DIY devices, Lifx bulbs, Flic buttons, Homekit and Google Assistant integration. Support for Buttons and Contacts connected to the Sonoff RF Bridge. Devices controlled directly with HTTP or using MqTT broker (preferred method). Automatic device discovery using mDNS, MqTT or manual IP address for auto detection. Easy install of Berto Hub on Pi 3/4 or fully configured Pi 4 in case with POE for €150 which includes 1 year Premium subscription, please PM. Just 3 IoT slave drivers providing support for dimmers & RGBW, switch lights, relays and numerous sensors (contact, input, power, voltage, battery, temperature, humidity, flood, vibration, tilt and lux). Custom MqTT message sending and receiving eventually replacing the need for original Berto_MQTTBridge driver. Other integration drivers include :-
WebView to provide the native device web interface on T3 touchscreens, useful for managing RGBW lights realtime. WebServer allowing bi-directional integration with your system controller. Read ALL your system devices and control them using simple HTTP commands. Send GET and POST requests and also establish WebSocket connections. Pushover & IFTTT providing bi-directional messaging with https://pushover.net and https://ifttt.com. Over 100 or so devices have been tested across various manufacturers and protocols, if you have a device that you would like support adding to the gateway then please PM and I’ll see what can be done.
Thank you
David

Then web server driver was written/released a few months ago and has no connection to what you are referring to.
Like I say, it is no more complicated than Ryan’s original HTTP driver.

Not at the moment, it's only my 'ever growing' list...

Yes, the IOT Dimmer driver support dimming and RGBW. The WebView driver provides a native interface on the T3 touchscreens.
I’m working on zigbee2mqtt at the moment along with the Sonoff Zigbee Bridge, zwave2mqtt is in the pipe line.
Thanks
David

My IoT suite supports Sonoff DIY, Shelly, Tasmota, Lifx, Yeelight in progress plus many other features.

Thanks
 
David

After several months of beta testing my new IoT driver suite I’m ready push a production release scheduled for the 5th June.
There are some significant changes to the way the main IoT Gateway driver works and as such I’m advising existing users of these drivers to turn Auto Update Off on all Berto drivers so that you can control when, or if, you update to the latest release.
Details of the update will be available at https://berto.io/c4z/Berto_IOTGateway/www/README.html but to provide a quick flavour...
Support for devices running Tasmota firmware, native support for Shelly and Sonoff DIY devices, Lifx bulbs, Flic buttons, Homekit and Google Assistant integration. Support for Buttons and Contacts connected to the Sonoff RF Bridge. Devices controlled directly with HTTP or using MqTT broker (preferred method). Automatic device discovery using mDNS, MqTT or manual IP address for auto detection. Easy install of Berto Hub on Pi 3/4 or fully configured Pi 4 in case with POE for €150 which includes 1 year Premium subscription, please PM. Just 3 IoT slave drivers providing support for dimmers & RGBW, switch lights, relays and numerous sensors (contact, input, power, voltage, battery, temperature, humidity, flood, vibration, tilt and lux). Custom MqTT message sending and receiving eventually replacing the need for original Berto_MQTTBridge driver. Other integration drivers include :-
WebView to provide the native device web interface on T3 touchscreens, useful for managing RGBW lights realtime. WebServer allowing bi-directional integration with your system controller. Read ALL your system devices and control them using simple HTTP commands. Send GET and POST requests and also establish WebSocket connections. Pushover & IFTTT providing bi-directional messaging with https://pushover.net and https://ifttt.com. Over 100 or so devices have been tested across various manufacturers and protocols, if you have a device that you would like support adding to the gateway then please PM and I’ll see what can be done.
Thank you
David

Zigbee2MQTT is WIP,  just taking longer than expected. Testing product from China and it’s not arriving fast enough surprise surprise!

After several months of beta testing my new IoT driver suite I’m ready push a production release scheduled for the 5th June.
There are some significant changes to the way the main IoT Gateway driver works and as such I’m advising existing users of these drivers to turn Auto Update Off on all Berto drivers so that you can control when, or if, you update to the latest release.
Details of the update will be available at https://berto.io/c4z/Berto_IOTGateway/www/README.html but to provide a quick flavour...
Support for devices running Tasmota firmware, native support for Shelly and Sonoff DIY devices, Lifx bulbs, Flic buttons, Homekit and Google Assistant integration. Support for Buttons and Contacts connected to the Sonoff RF Bridge. Devices controlled directly with HTTP or using MqTT broker (preferred method). Automatic device discovery using mDNS, MqTT or manual IP address for auto detection. Easy install of Berto Hub on Pi 3/4 or fully configured Pi 4 in case with POE for €150 which includes 1 year Premium subscription, please PM. Just 3 IoT slave drivers providing support for dimmers & RGBW, switch lights, relays and numerous sensors (contact, input, power, voltage, battery, temperature, humidity, flood, vibration, tilt and lux). Custom MqTT message sending and receiving eventually replacing the need for original Berto_MQTTBridge driver. Other integration drivers include :-
WebView to provide the native device web interface on T3 touchscreens, useful for managing RGBW lights realtime. WebServer allowing bi-directional integration with your system controller. Read ALL your system devices and control them using simple HTTP commands. Send GET and POST requests and also establish WebSocket connections. Pushover & IFTTT providing bi-directional messaging with https://pushover.net and https://ifttt.com. Over 100 or so devices have been tested across various manufacturers and protocols, if you have a device that you would like support adding to the gateway then please PM and I’ll see what can be done.
Thank you
David

After several months of beta testing my new IoT driver suite I’m ready push a production release scheduled for the 5th June.
There are some significant changes to the way the main IoT Gateway driver works and as such I’m advising existing users of these drivers to turn Auto Update Off on all Berto drivers so that you can control when, or if, you update to the latest release.
Details of the update will be available at https://berto.io/c4z/Berto_IOTGateway/www/README.html but to provide a quick flavour...
Support for devices running Tasmota firmware, native support for Shelly and Sonoff DIY devices, Lifx bulbs, Flic buttons, Homekit and Google Assistant integration. Support for Buttons and Contacts connected to the Sonoff RF Bridge. Devices controlled directly with HTTP or using MqTT broker (preferred method). Automatic device discovery using mDNS, MqTT or manual IP address for auto detection. Easy install of Berto Hub on Pi 3/4 or fully configured Pi 4 in case with POE for €150 which includes 1 year Premium subscription, please PM. Just 3 IoT slave drivers providing support for dimmers & RGBW, switch lights, relays and numerous sensors (contact, input, power, voltage, battery, temperature, humidity, flood, vibration, tilt and lux). Custom MqTT message sending and receiving eventually replacing the need for original Berto_MQTTBridge driver. Other integration drivers include :-
WebView to provide the native device web interface on T3 touchscreens, useful for managing RGBW lights realtime. WebServer allowing bi-directional integration with your system controller. Read ALL your system devices and control them using simple HTTP commands. Send GET and POST requests and also establish WebSocket connections. Pushover & IFTTT providing bi-directional messaging with https://pushover.net and https://ifttt.com. Over 100 or so devices have been tested across various manufacturers and protocols, if you have a device that you would like support adding to the gateway then please PM and I’ll see what can be done.
Thank you
David

After several months of beta testing my new IoT driver suite I’m ready push a production release scheduled for the 5th June.
There are some significant changes to the way the main IoT Gateway driver works and as such I’m advising existing users of these drivers to turn Auto Update Off on all Berto drivers so that you can control when, or if, you update to the latest release.
Details of the update will be available at https://berto.io/c4z/Berto_IOTGateway/www/README.html but to provide a quick flavour...
Support for devices running Tasmota firmware, native support for Shelly and Sonoff DIY devices, Lifx bulbs, Flic buttons, Homekit and Google Assistant integration. Support for Buttons and Contacts connected to the Sonoff RF Bridge. Devices controlled directly with HTTP or using MqTT broker (preferred method). Automatic device discovery using mDNS, MqTT or manual IP address for auto detection. Easy install of Berto Hub on Pi 3/4 or fully configured Pi 4 in case with POE for €150 which includes 1 year Premium subscription, please PM. Just 3 IoT slave drivers providing support for dimmers & RGBW, switch lights, relays and numerous sensors (contact, input, power, voltage, battery, temperature, humidity, flood, vibration, tilt and lux). Custom MqTT message sending and receiving eventually replacing the need for original Berto_MQTTBridge driver. Other integration drivers include :-
WebView to provide the native device web interface on T3 touchscreens, useful for managing RGBW lights realtime. WebServer allowing bi-directional integration with your system controller. Read ALL your system devices and control them using simple HTTP commands. Send GET and POST requests and also establish WebSocket connections. Pushover & IFTTT providing bi-directional messaging with https://pushover.net and https://ifttt.com. Over 100 or so devices have been tested across various manufacturers and protocols, if you have a device that you would like support adding to the gateway then please PM and I’ll see what can be done.
Thank you
David