Possibility to change Firebase data structure

[Sylvesta]

Hi All,

So I was wandering if it is possible to change the structure of information sent to Firebase.

Currently its something like this, using the default sketch data:

Sensors/config/devices/Node1-ESP-id/channels/0/gpio: etc
Sensors/controls/Node1-ESP-id/channels/channel-id
Sensors/log/Node1-ESP-id/timestamp/channel-id:value

Is it possible to change the structure to the following:

Node1-ESP-id/config/channels/gpio: etc
Node1-ESP-id/channels/channel-id:value
Node1-ESP-id/log/channel-id/timestamp:channel-id:value

Would the new structure require a rewrite of FireSense.h?

The reason is trying to read the log, it goes down to many levels and what I believe, if we could have a shorter and different structure would make it neater and easier to read from a backend etc. If you have any questions/ suggestions or would like me to explain more please let me know.

[mobizt]

The long path is not the problem, you should read this for the limitation of data structure.

However, you can create your own version of FireSense based on your custom path requirement.

Firebase-ESP-Client/src/addons/FireSense/FireSense.h

Lines 3287 to 3378 in 30adc8a

	std::string FireSenseClass::controlPath()
	{
	if (!configReady())
	return "";
	std::string s = config->basePath.c_str();
	s += "/controls/";
	s += deviceId;
	return s;
	}
	std::string FireSenseClass::channelControlPath()
	{
	std::string s = controlPath();
	s += "/channels";
	return s;
	}
	std::string FireSenseClass::configPath()
	{
	if (!configReady())
	return "";
	std::string s = config->basePath.c_str();
	s += "/config/devices/";
	s += deviceId;
	return s;
	}
	std::string FireSenseClass::conditionPath()
	{
	std::string s = configPath();
	s += "/conditions";
	return s;
	}
	std::string FireSenseClass::channelConfigPath()
	{
	std::string s = configPath();
	s += "/channels";
	return s;
	}
	std::string FireSenseClass::streamCmdPath()
	{
	std::string s = controlPath();
	s += "/cmd";
	return s;
	}
	std::string FireSenseClass::statusPath()
	{
	if (!configReady())
	return "";
	std::string s = config->basePath.c_str();
	s += "/status/";
	s += deviceId;
	return s;
	}
	std::string FireSenseClass::terminalPath()
	{
	std::string s = statusPath();
	s += "/terminal";
	return s;
	}
	std::string FireSenseClass::channelStatusPath()
	{
	std::string s = statusPath();
	s += "/channels";
	return s;
	}
	std::string FireSenseClass::lastSeenPath()
	{
	std::string s = statusPath();
	s += "/lastSeen";
	return s;
	}
	std::string FireSenseClass::logPath()
	{
	if (!configReady())
	return "";
	std::string s = config->basePath.c_str();
	s += "/log/";
	s += deviceId;
	return s;
	}

[Sylvesta]

Thank you I will read what you posted.

I am having an issue trying to read past the timestamp entry Sensors/log/Node1-ESP-id/timestamp/channel-id:value. I cannot search for the timestamp and then provide the values for the channel-id.

[mobizt]

Data query is useful if you use it properly.

For JS usage https://firebase.google.com/docs/reference/js/firebase.database.Query.

In FireSense class, we use the query for the log data which the children that its time node is older than the predefined period and will be deleted later.

However, with REST client i.e. this library, the index should set on the child node that being query in the database rules.

This is how it sets the index in database rule with setQueryIndex.

Firebase-ESP-Client/src/addons/FireSense/FireSense.h

Line 4507 in 30adc8a

if (!Firebase.RTDB.setQueryIndex(config->shared_fbdo, logPath().c_str(), firesense_token_t::time, databaseSecret))

This is the function description.
https://github.com/mobizt/Firebase-ESP-Client/tree/main/src#set-the-query-index-to-the-database-rules

For your case, if your timestamp is number which can be easily query as in FireSense do, otherwise your timestamp is date string that can be query based on alphabetical order.

[Sylvesta]

That's what I am trying to figure out, how to query properly.

Here is 2 queries I have tried:
var ref = firebase.database().ref().child("Sensors");
ref.child("log").once("value").then(function(a) {
return a.forEach(function(a) {
return console.log(a.val());
});
});

var ref = firebase.database().ref().child("Sensors/log");
ref.on('child_added', function(childSnapshot) {
return console.log(childSnapshot.val());
});

This is the result:

I am trying to get this data so that I can use it to plot a chart:

I don't know how to look past this:

[mobizt]

This can do easily with orderByXXX.

See the image below, when we use the orderByChild with some child node which need not to know its absolute path.

The database in the image was created by push, the uuid was auto generated as the parent of push data which we don't care if we don't know it.

We only set the ref on its known parent path i.e. "Sensors/log" and use orderByChild() like this.

var ref = firebase.database().ref(("Sensors/log");

ref.orderByChild("time").once("value").then(function(a) {
return a.forEach(function(a) {
return console.log(a.val());
});
});

This blog provides the usage example.