It is of course possible to divide my 32 bit bit on the device side into bits 0/1.
But this will increase network traffic …
this is to help me monitor the control box, where each event (running) of the circuit is to be recorded the time stamp of the occurrence of the event. Then, on the Cayenne side, I would like to show these events in a form similar to a graph but square, just like a logic analyzer does.
The suggested value type in the MQTT message is:
value: $00000000 (unsigned long)
timestamp: $00123333 (unsigned long) time of event occurrence on the device
timetick: $0000 (16 bit unsigned) ticktime (if the event has occurred 3 times per second)
I would be very grateful for the introduction of such a widget … Unfortunately, I am not a professional;) web programmer and therefore I am looking for such functionalities in external data presentation systems. I can only add that if there was such a functionality that I mention above, it would open up many new industries for the Cayenne system.
Oh I see
in one package, more channels can be sent.
now it would be useful to give timestamp and tickstamp, and I would be satisfied.
Because for the presentation on the timeline I would write applications in c # who would download event histories and present them in the form of a graphical event.
I have high hopes that it will happen sooner than later.
it can happen again but again:
events are recorded on the device - value changes.
each change in value has the time recorded when it occurred
then the device if it has an internet connection to its queue cyclically sends recorded values and timestamp
if the device loses access to the internet (there may be many reasons), it still records the value change event … after receiving the connection, it sends the changes in the value from the buffer …
In order not to make a big revolution and not to update cayenne clients, it is suggested that the server / broker register two additional variables in the channel value definition. If we do not give these values, then everything behaves as before. Only in the SQL database will you have to disable the timestamp machine for this column, and timestam broadcast in the server script.
and I have a question, if these additional functionalities that I suggested you implement, will you inform here in this post?
I do not hide that I am waiting for timestamp …
@xbary we just had a web update on wednesday and team is busy with it. So we are not adding any new feature till we have all previous issue fixed. Once we have a very stable platform, we will to added new feature one by one.
Hi @xbary, Thanks for your ideas, we have taken them into consideration.
Like @shramik_salgaonkar said, we just launched a big major back-end update this week that we have been working for a few months, and we have another 2 coming before year end, plus a couple of features in the works.
Next year, we will be more focus on adding lots of features, including the ones suggested. There is a lot we have planned, but time is not our friend at the moment. I appreciate your suggestions. Keep them coming!!!