You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
register for only a specific paramset of a peer and channe
also for specific paramsets in all channels
should also support using MASTER paramset
specific value only
some multiple specific values
maybe the description for registering can be something like a tree array/object which defines what should fire an event, doesn't have to be exact this format, but should support that kind of granularity:
/* get all updates on the specific value STATE of peer 1 channel 1 paramset VALUES */
{
peerId: 1,
event: onUpdate,
channels: {
1: {
paramsets: {
VALUES: STATE
}
}
},
},
/* get all changes on values of peer 2, channel 2, paramset MASTER */
{
peerId: 2,
event: onChange
channels: {
2: {
paramsets: {
MASTER: {}
}
}
},
},
/* get all changes on values of peer 3, channel 2 */
{
peerId: 3,
event: onChange
channels: {
2: {}
},
},
/* get all changes of the value of the system variable */
{
systemVariable: myVariable,
event: onChange
},
/* get all changes of all system variables */
{
systemVariable: {},
event: onChange
},
/* get all changes of all system messages */
{
systemMessage: {},
event: onChange
},
/* get all timed events when triggered */
{ events: {},
event: trigger
}
The text was updated successfully, but these errors were encountered:
Currently:
When I register for events of a specific device, I don't get events for changes I have done.
Also I receive events even the value didn't change.
Even worse... If I change a value (at least by any kind of rpc access) it doesn't fire an event for the change.
Is it possible, that only changes made by the physical device fires an event?
maybe the description for registering can be something like a tree array/object which defines what should fire an event, doesn't have to be exact this format, but should support that kind of granularity:
The text was updated successfully, but these errors were encountered: