My main use case for EMQX is using it as a broker for MQTT. In our projects, we use EMQX as an MQTT broker because we are an IoT-based company where devices are provisioned or connected to our cloud through MQTT, allowing devices to send data to our services, back-end service, or cloud using an MQTT connection through EMQX.
EMQX is a unified architecture and unified namespace based on MQTT broker, primarily using EMQX or HiveMQ. We use EMQX for the communication of factory data, sensors, and PLCs. We track data on sensors and MQTT data by collecting MQTT data for sensors and publishing it to the MQTT broker. We then fetch MQTT data again, calculate some KPIs, and publish these KPIs back to the MQTT broker. We primarily use energy data for reducing energy costs and calculate the machine state of machines. We use EMQX and MQTT mostly for the machine state of machines. We collect machine data, such as temperature or pressure and sensor values in machines, and then calculate the machine state of the machines or lines. We collect energy data of these machines in energy analyzers and calculate the total energy of the products.
My main use case for EMQX is for communicating with ESP32 devices and sharing messages from one device to another device at the central level. Our company is a fuel automation company, and we will have dispenser units where we connect one ESP32 for each dispenser unit. We get all the data from the dispenser unit and share it to the server via EMQX.
EMQX is a scalable open-source MQTT broker designed to connect millions of IoT devices reliably. It is known for its high availability and robust performance, making it a go-to choice for enterprises seeking efficient data transmission across IoT ecosystems.EMQX offers advanced features supporting complex IoT use cases and ensures seamless data flow with low latency. It supports a wide range of protocols and is suitable for industrial IoT, smart homes, and automotive sectors. Developers favor...
My main use case for EMQX is using it as a broker for MQTT. In our projects, we use EMQX as an MQTT broker because we are an IoT-based company where devices are provisioned or connected to our cloud through MQTT, allowing devices to send data to our services, back-end service, or cloud using an MQTT connection through EMQX.
EMQX is a unified architecture and unified namespace based on MQTT broker, primarily using EMQX or HiveMQ. We use EMQX for the communication of factory data, sensors, and PLCs. We track data on sensors and MQTT data by collecting MQTT data for sensors and publishing it to the MQTT broker. We then fetch MQTT data again, calculate some KPIs, and publish these KPIs back to the MQTT broker. We primarily use energy data for reducing energy costs and calculate the machine state of machines. We use EMQX and MQTT mostly for the machine state of machines. We collect machine data, such as temperature or pressure and sensor values in machines, and then calculate the machine state of the machines or lines. We collect energy data of these machines in energy analyzers and calculate the total energy of the products.
My main use case for EMQX is for communicating with ESP32 devices and sharing messages from one device to another device at the central level. Our company is a fuel automation company, and we will have dispenser units where we connect one ESP32 for each dispenser unit. We get all the data from the dispenser unit and share it to the server via EMQX.