Maybe it's the wrong place to ask but out of curious: Does anyone have experience building API for hardware/IoT device? How's the process? How long did it take? How's the investment come back?
@Pettersr Thanks for the answer. This is very detailed.
The IoT device goes into underground. The project was to save thermal heat generated from other sources and use them as central heating/decarbonising spaces and we have built a prototype. It's control and measure. The new version aim to:
Control the heat releasing
Collecting current data and view it in real time(or at least close to real)
Showing how much electricity we are actually saving and the cost we are saving.
But looking to build a more comprehensive/prettier one good for marketing.
InfluxDB doesn't sound very ideal. Is there other product support MQTT? Time series database wise ummmm potentially also other DB we can get it cheaper? Previous one's hardware cost was already rocket high and drains the pocket
Have you tried AWS Fleet Manager? I have seen their demo but not sure how is it in production
I will have more conversations regarding this(MQTT and HiveMQ) next week and get back to this thread later. But agree on the cheaper database solution part.
As a general rule, when a received entity value is identical to an existing entity value, nothing happens to the entity’s existing value. There’s no state-change and the entity’s last_updated value remains the same (basically, the duplicate value is ignored). Try r-j-taylor’s suggestion. MQTT Trigger