Shannon
Not reliable enough for agricultural control or critical monitoring
I used UbiBot equipment in a small mushroom farming environment for monitoring and automation. The products have some good ideas, especially the API access and the ability to integrate data into an external monitoring system, but my experience has left me unable to trust the platform for production agricultural control. The biggest issue I experienced was with a UbiBot smart plug controlling an ultrasonic fogger in a mushroom fruiting room. The plug could report as ON while the fogger was not effectively operating and room humidity continued to fall. Independent monitoring showed the room was not recovering as expected. The condition was only resolved by cycling the smart plug OFF and back ON. After investigation, UbiBot support advised that my SP1 10A smart plug may not be suitable for this type of fogger load because ultrasonic foggers / PSU loads can create capacitive inrush and long-term relay stress. That explanation may be technically valid, but this limitation was not clear to me at the time of purchase. The product is positioned around smart control, environmental monitoring, agriculture, and ordinary appliance automation. For a small grow room or hobby farming customer, a fogger or humidifier is an obvious device to automate. Seeing a 10A smart plug used with a roughly 370W running load, I do not think it is obvious that this application may be unsuitable unless UbiBot clearly states that upfront. Support did engage and reviewed backend data, which I appreciate. However, the process also highlighted how much investigation I had to do myself. I had to provide screenshots, monitoring evidence, physical observations, raw data exports, and perform requested tests to demonstrate the failure pattern. I would also rate the setup and platform configuration as at least intermediate. I am technical, and after spending time reading through the options, tabs, alert settings, API options, and device configuration pages, I was able to find the settings that mattered for my setup. But for a non-technical farm operator, I can see this being a stopper. I would not expect my wife, who actually runs the mushroom farm day to day, to confidently set up and maintain the sensors, loggers, smart plugs, alert rules, and platform settings herself. I have also observed cloud/platform behaviour that makes troubleshooting harder. In separate incidents, devices or sensors appeared online in some ways but disconnected or stale in others. In one case, alerts could still come through while dashboard/app telemetry did not appear to reflect the live state clearly. That kind of partial failure state is difficult to trust in an operational environment. Another limitation is the handling of repeated / continuous alerts. In a production room, if humidity remains below a critical threshold, I need reliable escalation until the issue is resolved. Alert suppression or limiting may make sense for reducing noise in casual use, but it is a serious concern for production monitoring. Overall, I think UbiBot may still be useful for basic non-critical monitoring, trend visibility, or hobby use where occasional ambiguity is acceptable. Based on my experience, I would not rely on it for agricultural control, fogger automation, production grow rooms, or any situation where an incorrect device state or limited alerting could lead to losses. I am now planning to phase UbiBot out of my mushroom farm setup and move toward local monitoring, local alerting, and independently verifiable control hardware.

