After my the discovered problems with reliability of the logged data (regarding support the data a stored “compressed” by an unrevealed method), the recommendation is to utilize an IBS-M1 gateway to get access to uncompressed data.
Now reading about this gateway in manuals and in the forum, I noticed that there are two different revisions of the IBS-M1 gateway, that are not easy to tell apart, as the have the same model number. To tell them apart you have look an the Inkbird print on the device (blue or grey).
Now I have a questions to the the storage of data:
1.) Where is the “real logged” data stored (device, gateway, cloud-account) and how/when is promoted forward?
2.) If the data is directly transferred to the cloud, why is there a limit at all?
And also to the connection of devices:
One support statement tells, that one sensor can be connected to two gateways at the same time. Is this true?
How can data promoted from the sensor to one gateway also be promoted via the other?
How long does data stay on the sensor device itself?
Can the Engbird app directly connecting to the sensors be used in parallel with the use of the same sensor via the IBS-M1 gateway(s)?
The data acquired by IBS-M1 will be stored inside IBS-M1 and uploaded to the cloud of the corresponding account. Because the IBS-M1 itself has a storage limit, it has a data quantity limit.
If you don’t want a limit, perhaps you could consider the IBS-M2, which is a new release. The IBS-M2 has no internal storage, it uploads data directly to the cloud, so there is no limit to the amount of data it uploads, and the data can be stored for one year. However, please note that it can only be connected to a maximum of 9 sensors.
For the sensor IBS-TH1 PLUS, which can be connected to 2 gateways at the same time, it can store up to 30,000 data points, the storage time depends on the set time interval. It can be connected directly to the Engbird app to view the data or connected to the INKBIRD app through a gateway to view data.
If the IBS-M1 has a storage itself, how much is it and does this apply to each linked device or is it a total common storage space for all linked devices?
Since I have bought one of rev2, it looks as if historic data can be deleted per device.
looking at the architecture, it seems that uploading to the cloud is not a must. I wonder what happens if the internet connection breaks (or is intentionally not present, because the device is offsite)?
Will the data still be collected inside the IBS-M1, as long as it stays close to the “linked” devices?
Will it be accessible after the IBS-M1 is brought back to WiFi coverage?
When starting up the IBS-M1, it had to be linked to my account and my home WiFi. However the 4 IBS-TH1 Plus devices have been listed automatically in the IBS-M1 part. So it seems that there is no real “link” between the gateway and the T/H sensor, but the IBS-M1 is just reading the BT advertisement data which are sent automatically by the BLE devices. Consequently there should be no limit of IBS-M1 - simply as it forwards all visible identifiable device data - even if these devices would not be my own, but of my neighbor.
I will now compare the T/H logs received either directly via Engbird app or stored from IBS-M1 from the read BLE data.
The IBS-M1 (blue INKBIRD logo) can connect up to 50 sensors, and it can store 30,000 data points for each sensor.
If the internet connection breaks, but the gateway is connected to power and remains connected to the sensor, it will continue to record data from the sensor. It will re-upload the data when the internet is reconnected.
IBS-M1 will automatically search for surrounding sensor signals and connect automatically. If there are other sensors around it, it might connect.
My questions were around the obvious fact that during power outage nothing happens. When testing the scenario, It seems that after return of power, the devices get identified back to their original names and settings and logging continues from the moment of re-discovery. The time during power outage does not log anything, as the IBS-M1 just listens to what the T/H sensors are broadcasting and it does not have access to the internal memory of the T/H sensors like e.g. the Engbird app has.