Based on our record, Firebase seems to be a lot more popular than MQTT Explorer. While we know about 248 links to Firebase, we've tracked only 14 mentions of MQTT Explorer. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Sounds like you're on a good path tracking the problem to aws, not the esp. First of all, I'd try to make it work with a "proven" solution, then move on to your own implementation. I have had good success using http://mqtt-explorer.com/ on windows to diagnose a similar situation. Mqtt explorer gives you very granular control over endpoints and topics, so might be helpful to you too. Source: about 1 year ago
I would suggest using Mqtt explorer (http://mqtt-explorer.com/) to see how often the sensor updates its values. This as a first step to narrow down the problem. Source: about 1 year ago
Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/. Source: about 1 year ago
You can write test programs to send very specific messages to simulate errors, or simulate entire components that aren't written yet. There are also free programs like MQTT Explorer that will let you browse the message traffic, generate messages manually, log whatever you cant, and even graph your values if you happen to send numerical values (that is really cool when you do some long-term testing). Source: over 1 year ago
To use a local server can let you control all details of your full messaging chain. Try other clients can make you away from the ill behaviors or bugs of specific client. I recently demonstrate how easy a free MQTT client (MQTT explorer) send to a free MQTT database on Windows 10 in my video. Source: over 1 year ago
Head over to Firebase Developer Console homepage, sign in using your Gmail address, and click the Go to Console button to navigate to the console's overview page. - Source: dev.to / 18 days ago
I didn't really give much thought as to which backend I would use. I already had 2 projects in Supabase (BOXCUT & MineWork), but also a few projects in Firebase too. I was more concerned at the time at actually building the product. - Source: dev.to / 20 days ago
Firebase, a well-known backend platform, is widely utilized for building Serverless or Headless web and mobile applications. This discussion will delve into executing comprehensive CRUD (Create, Read, Update, Delete) operations within Firebase. CRUD operations serve as fundamental building blocks for both web and mobile applications. To initiate this process, create a new project in the Firebase Console.... - Source: dev.to / 2 months ago
For example, you can rely on the powerful OAuth by Okta to handle your Auth services, Flutterwave payment gateway to accept payment, and Google Firebase Messaging to manage notifications. - Source: dev.to / 3 months ago
Backend as a Service (BaaS) goes back to early 2010’s with companies like Parse and Firebase. These products integrated everything a backend provides to a webapp in a single, integrated package that makes it easier to get started and enables you to offload some of the devops maintenance work to someone else. - Source: dev.to / 3 months ago
mosquitto - Eclipse Mosquitto is an open source (EPL/EDL licensed) message broker that implements the MQTT protocol versions 5.0, 3.1.1 and 3.1. Mosquitto is lightweight and is suitable for use on all devices
Supabase - An open source Firebase alternative
MQTTBox - MQTTBox enables to create MQTT clients to publish or subscript topics, create MQTT virtual device...
OneSignal - Customer engagement platform used by over 1 million developers and marketers; the fastest and most reliable way to send mobile and web push notifications, in-app messages, emails, and SMS.
HiveMQ - HiveMQ is the MQTT based messaging platform for fast, efficient and reliable data movement to and from connected IoT devices and enterprise systems
Android Studio - Android development environment based on IntelliJ IDEA