Touch glass 10-button light switch [SB3S] from Aliexpress - setup with Domoticz

Honsu wrote:

(...) 5196193800_1699358972.jpg https://obrazki.elektroda.pl/6840140600_1699358972.jpg https://obrazki.elektroda.pl/5652410000_1699358972.jpg https://obrazki.elektroda.pl/8918380100_1699358975.jpg https://obrazki.elektroda.pl/9950550400_1699358975.jpg https://obrazki.elektroda.pl/7897766700_1699358975.jpg

Hi,

From your description, I understand that you are having trouble fully integrating the 10-button glass switch with your domoticz system. It seems that domoticz can only detect 7 of the 10 buttons and one of them is not working properly. Additionally, you notice some delay when switching all the lights.

Based on this information, let me suggest some potential solutions:

1. Upgrade the domoticz software: There may be a newer version of the software that better supports this particular type of switch. It is always a good idea to check its latest version.

2. Review the configuration of your device in domoticz: Make sure you have configured the device correctly in domoticz. There may be some configuration that will allow all 10 buttons to be read.

3. Use alternative software: There are many alternatives to domoticz that may better support this particular type of switch. Examples include Home Assistant, openHAB and Node-RED. Many of these tools have a wealth of resources and online communities that can help you set up your device.

When it comes to the latency problem, this can be caused by a number of factors. It could be due to the limitations of the inverter, as you suggest, but it could also be due to network link limitations or delays in the software itself.

When it comes to assigning one button to light 5 buttons, this is possible with many home automation systems, but the exact instructions will depend on the software you are using. In the case of domoticz, you will probably need to create a scene or group that contains these five buttons and then assign this scene or group to one of the buttons.

I hope you find this information useful. If you have any more questions, please feel free to ask.

Honsu wrote:

can you help me create an autoexec.bat file for the OpenBeken platform ?

I understand that you want to create an `autoexec.bat` configuration file for the OpenBeken platform. OpenBeken is an open-source software project that allows you to flash and program devices based on Beken chips, which are widely used in low-cost IoT devices such as your glass touch switches.

The `autoexec.bat` file, however, is not something you typically encounter in the context of OpenBeken or other IoT projects. The name `autoexec.bat` is a remnant of older systems, such as MS-DOS, where it was a batch file executed at system start-up.

In the case of OpenBeken and similar projects, instead of `autoexec.bat`, start-up scripts or configuration files specific to the software that manages the device are usually configured. To create a suitable configuration file or script for OpenBeken, you would need to follow the OpenBeken project documentation.

Here are some general steps you can take:

1. Check the OpenBeken documentation : Look in the OpenBeken documentation for information on device configuration and boot scripts.

2. Understand the device configuration : You need to understand what the configuration options are for your device, what options you have available and what the appropriate commands are for your case.

3. Tailor the configuration to your needs : Based on this knowledge, tailor the configuration file to your device and needs.

4. Test in a secure environment : Always test configuration changes on one device before deploying them on a larger scale.

5. Seek help from the OpenBeken community : If you encounter difficulties, seek help from the OpenBeken community who may have experience with similar devices.

If you need more detailed instructions, I will need more information about what exactly you want to achieve with the configuration file, what the specific requirements are for your device and what steps you have already taken. Once I have more data, I will be able to try to help you more specifically.

Honsu wrote:

Added after 45 :

How to configure OpenBeken to connect to Domoticz

Configuring OpenBeken to connect to Domoticz is based on setting the appropriate parameters in the OpenBeken software configuration to allow communication with the Domoticz server. Here are the steps you should follow to configure OpenBeken with Domoticz:

1. Install OpenBeken : You must first install OpenBeken on your device if you have not already done so. Detailed instructions for flashing the OpenBeken software onto Beken chips can be found in the project's documentation or on dedicated websites.

2. Find the documentation : Check the OpenBeken documentation to understand the available configuration options. Look for information on MQTT integration, as this is a common way to integrate various devices with Domoticz.

3. Configure MQTT : Domoticz supports the MQTT protocol, which is commonly used for communication between IoT devices. OpenBeken should also offer the ability to configure an MQTT client. You need to configure the following parameters:
- MQTT server address (IP address or hostname of your Domoticz server).
- MQTT server port (default 1883 if you are not using SSL/TLS, 8883 for MQTT over SSL/TLS).
- User and password (if you are using authentication).
- MQTT client ID (clientId), which will be unique to your device.
- Topics (topics) to which the device will publish data and from which it will subscribe to commands.

4. Configure OpenBeken : Set the appropriate MQTT parameters in the OpenBeken configuration. You may need to adjust scripts or configuration files so that the device sends information to Domoticz in the correct format.

5. Add the device to Domoticz : In Domoticz you need to add an MQTT device:
- Go to "Settings" > "Hardware" in Domoticz.
- Add new hardware by selecting the type "MQTT Client Gateway with LAN interface".
- Enter the appropriate configuration details.

6. Create virtual sensors and switches : In Domoticz, create virtual sensors or switches that correspond to the data published by the device from OpenBeken.

7. Automation and scenes : You can now create scenes or automation rules in Domoticz that will respond to data received from the device or send commands to the device.

8. Testing : Make sure everything is working correctly, testing publishing and subscribing to MQTT topics using an MQTT client, for example mosquitto_pub and mosquitto_sub.

9. Debugging : If you encounter problems, use tools such as MQTT.fx or other MQTT client for communication monitoring and debugging.

Please note that details may vary depending on the version of Domoticz, the specific OpenBeken firmware and the specifics of your device. You will need to adapt the above steps to your specific situation. If you don't find the information you need in the OpenBeken documentation, it's a good idea to seek help on forums and community groups related to IoT and home automation.

Honsu wrote:

How to configure OpenBeken to connect to Domoticz

Integration of OpenBeken-based devices with Domoticz can be achieved using the MQTT protocol, which is a common communication standard for IoT devices. Domoticz has a built-in MQTT broker and can also connect to an external MQTT broker. Below you will find the steps needed for configuration:

1. Install and configure an MQTT broker:
- If you do not already have an MQTT broker, install one, such as Mosquitto.
- Configure the broker according to its documentation, including authentication and encryption if needed.

2. Configure Domoticz to use MQTT:
- In Domoticz, go to "Settings" -> "Hardware" and add new hardware of type "MQTT Client Gateway with LAN interface".
- Enter the data required to connect to the MQTT broker (IP address, port, user, password).

3. Configure OpenBeken to communicate with the MQTT broker:
- In the OpenBeken software, set the MQTT connection parameters to point to the MQTT broker you have configured in Domoticz.
- These settings can include the broker's IP address, port, login details (user and password), and the topic on which the device will publish its states, and the topic from which it will receive commands.

4. MQTT publishing and subscription:
- The device should publish messages to the topic in a way that Domoticz understands, i.e. according to the accepted MQTT topic convention in Domoticz.
- Also the device should subscribe to the topic on which Domoticz will send commands.

5. Create virtual devices in Domoticz:
- In the Domoticz user interface, add virtual devices that replicate the physical buttons and switches of your device with OpenBeken.
- Assign each virtual device an MQTT topic under which it will publish or from which it will receive commands.

6. Automation and rules:
- Using scripts in Domoticz or creating "Scenes" and "Groups", you can set up automation rules, such as turning on lights at certain times, responding to other sensors, etc.

7. Test the configuration:
- Test the entire configuration, checking that the communication between OpenBeken and Domoticz works correctly. Verify that MQTT messages are correctly published and subscribed to, and that virtual devices in Domoticz respond appropriately to state changes.

Please note that configuration details may vary depending on the specific OpenBeken implementation, Domoticz version and specific MQTT broker. The steps above are general guidelines that you should adapt to your specific configuration. If OpenBeken does not have direct support for MQTT, you may have to use some indirect communication mechanism or use additional scripts for integration.

Honsu wrote:

4. Publish and subscribe to MQTT:

Honsu wrote:

4. Publish and subscribe to MQTT:

Speak more about how to configure OpenBeken MQTT to work with Domoticz.

OpenBeken's MQTT integration with Domoticz requires that OpenBeken-based devices publish data in a format that Domoticz understands, and subscribe to the relevant MQTT topics so that they can receive commands from Domoticz. Here is a detailed description of the configuration process:

## OpenBeken MQTT configuration for data publication:

1. Select MQTT topics for publication and subscription:
- Specify which MQTT topics will be used for communication. Domoticz uses a specific topic structure, for example:
- `domoticz/in` - for commands sent to devices
- `domoticz/out` - for data published by devices

2. Message format:
- Messages published to `domoticz/out` should be in JSON format and must contain the IDX, which is the device identifier in Domoticz, and the state or value we want to communicate. Example of a message:

- `idx` is the identifier of the virtual device in Domoticz.
- `nvalue` is a numeric state value, for example 0 or 1 for a switch.
- `svalue` is a value as a string, it could be e.g. temperature or other measurement.

3. Configure OpenBeken to publish:
- Configure OpenBeken to publish MQTT messages to the broker according to the agreed topics and format. The exact instructions depend on the software you are running on OpenBeken, but generally you will need to set up scripts or configuration to send data at specific intervals or at specific events.

## OpenBeken MQTT configuration for command subscription:

1. Subscribe to command topics:
- Configure OpenBeken to subscribe to the `domoticz/in` topic to receive commands from Domoticz.
2. Command handling:
- Upon receiving a command in JSON format, your OpenBeken device should interpret this message and perform the appropriate action. For example, if it receives a command to turn on a light, it should activate the appropriate relay.

## Integration with Domoticz:

1. Add devices in Domoticz:
- In Domoticz, add virtual devices that correspond to your physical devices from OpenBeken. Each device will receive a unique IDX.

2. Synchronise IDX:
- Ensure that the IDX assigned in Domoticz to the virtual device is used in the MQTT messages sent by the OpenBeken device.

3. Automate operation: .
- You can now configure Domoticz to either respond to data received from the OpenBeken device or send commands to the device based on different rules or scenes.

## Debugging and testing:

- Once everything is configured, test the system by sending test messages from OpenBeken to the MQTT broker and checking that Domoticz receives and correctly processes this data.
- Use tools such as MQTT Explorer to monitor MQTT traffic and make sure that messages are being published and subscribed to correctly.

The above steps assume that OpenBeken has MQTT support implemented. If this is not the case, you may need to implement an MQTT client in your OpenBeken software first. In any case, the implementation details will depend on the specific firmware you are using with OpenBeken.