F.A.Q
Frequently Asked Questions
Yes, you definitely need the Access Point. The adapter solely establishes the connection to the OEPL Access Point, and communication between the display and iobroker always occurs through this Access Point. It's crucial for transmitting information between the iobroker system and the display via the OEPL Access Point.
The displays based on the ZBS243 chip aren't compatible with the standard Zigbee gateway because they utilize a different protocol and firmware compared to most Zigbee devices. The protocol and firmware are proprietary and not publicly accessible, hence they can't easily communicate with a different gateway. To control the displays, one needs a dedicated access point that understands the protocol and firmware, interacting with the ZBS243 chip. The access point might be based on an ESP32 microcontroller, also employing a ZBS243 chip as a radio module. Using a specific device called ZBS_Flasher, it's possible to overwrite the ZBS243 chip's firmware and install an alternative firmware and protocol reverse-engineered by some developers. One of these projects is OpenEPaperLink, enabling fast, low-power, low-latency communication between the displays and the access point. It also supports various display types like 4.2-inch, 2.9-inch, and 1.54-inch displays, including segmented displays. More information and guidelines can be found on the project's GitHub page."
WebSocket and MQTT are both protocols used for communication but serve different purposes.
WebSocket provides a bidirectional, full-duplex communication channel over a single, long-lived connection. It's designed for real-time, interactive web applications where data exchange happens instantly between a client and a server. WebSocket is well-suited for applications requiring continuous, low-latency data updates, such as live chats or real-time notifications.
On the other hand, MQTT (Message Queuing Telemetry Transport) is a lightweight, publish-subscribe messaging protocol ideal for IoT (Internet of Things) and sensor networks. MQTT follows a pub/sub model, where devices publish messages to specific topics, and subscribers receive messages from topics they're interested in. It's efficient in low-bandwidth, high-latency, or unreliable networks and is commonly used in scenarios like remote monitoring, telemetry, or connecting various IoT devices.
In summary, WebSocket focuses on real-time bidirectional communication for web applications, while MQTT is optimized for efficient messaging and data exchange among IoT devices in resource-constrained environments.
VIS and JSON serve different purposes within ioBroker, depending on the requirements and the nature of representation:
VIS (Visualisation): VIS is ideal for creating visual user interfaces to graphically represent data and control elements. It's particularly suitable for designing dashboards, visualizing sensor data, device control, and user interaction in smart home environments.
JSON (JavaScript Object Notation): JSON is commonly used for storing and exchanging data in a machine-readable format. In ioBroker, JSON is used for configuration files, scripting control, data organization, and communication between different adapters.
In general, VIS is used to design graphical interfaces for user interaction, while JSON is utilized for data organization and exchange in a structured form. When creating user interfaces and visually representing information, VIS is the preferred choice. However, when organizing data structures or exchanging data between different systems, JSON serves as the suitable solution.
When it comes to displaying simple values like temperature readings or messages, using JSON provides a straightforward approach. JSON is well-suited for organizing and exchanging such data in a machine-readable format. It's efficient for storing and transmitting basic data points between different systems or applications.
(https://github.com/jjwbruijn/OpenEPaperLink/wiki/Json-template)
On the other hand, if you aim to present this information graphically or in a more visually engaging manner, VIS becomes valuable. VIS allows the creation of user-friendly interfaces, enabling you to display these values using widgets, charts, or graphical elements. This is particularly beneficial when you want users to interact with and interpret data more intuitively, making it ideal for graphical representation and user interface design.
In summary, JSON serves well for managing simple data points or messages, while VIS is advantageous for creating graphical representations and user interfaces for a more engaging user experience, especially when dealing with visualizing data like temperature trends or message logs.
Regardless of your preference, both options are feasible using the adapter. Whether you choose to visualize data through screenshots using Puppeteer or handle and exchange data in JSON format, the adapter supports both functionalities. It offers the flexibility to accommodate different methods based on your specific needs. Whether you opt for graphical representation through Puppeteer screenshots or manage data exchange using JSON, the adapter facilitates both approaches seamlessly.