🖱️ Discover the Clicksensor Plugin – Your Solution for Precise Click Event Detection

The Clicksensor Plugin is a powerful tool designed to manage and configure click event sensors. With its intuitive, flow-based programming, you can effortlessly set up workflows to efficiently process detected click events.

🌟 Why Choose the Clicksensor Plugin?

  • ⚡ Real-Time Click Detection: Instantly capture click events as they occur and respond in real-time.
  • 🔍 Advanced Event Filtering: Filter click events based on various criteria, ensuring only relevant data is processed.
  • 💾 Data Management & Storage: Securely store all captured click events in the database and access them anytime through the provided API.
  • 🤖 Automated Workflow Integration: Seamlessly integrate Clicksensor into your existing workflows to automate event management.
  • 🎵 Acoustic Signal Detection: Utilize highly accurate acoustic signals for reliable click event detection.

✨ Your Benefits at a Glance

  • 📈 Enhanced Tracking: Optimize the capture of click events and gain valuable insights into user behavior.
  • 🎯 Increased Accuracy: Minimize false alarms and ensure only relevant click events are recorded.
  • ⏳ Time Savings: Automate repetitive tasks and focus on what truly matters.
  • 📞 Reliable Support: Enjoy 24/7 customer service and a 1-year warranty for peace of mind.
  • 🔄 Easy Updates: Stay up-to-date with regular updates, including the latest version 1.0.3.

🚀 Perfect for Your Needs

Whether you’re looking to improve event tracking systems, enhance detection accuracy, or automate event management workflows – the Clicksensor Plugin offers the flexibility and performance you need.

Start today with the Clicksensor Plugin and turn acoustic click signals into valuable data for your business! 💡

💥 Highlights:

  • 💪 Powerful & Flexible: Ideal for a wide range of applications in click event detection.
  • 🖱️ User-Friendly: Easy setup and integration thanks to flow-based programming.
  • 🔒 Secure & Reliable: Robust data management and continuous support ensure smooth operation.

Take the next step in precise and efficient click event detection with the Clicksensor Plugin! 🖱️✨

| Field | Value | |-----------------------|---------------------------------------------------------------------------| | NAME | clicksensor | | VERSION | 1.0.2 | | ALIAS | Clicksensor Plugin | | TAGS | sensor, event, click, acoustic, detection, workflow integration, event analysis | | SHORTDESCRIPTION | Detects and filters click events using acoustic signals. | | DESCRIPTION | The Clicksensor Plugin is a robust tool designed to manage and configure click event sensors. Leveraging flow-based programming, users can effortlessly set up workflows to process detected click events. This plugin is perfect for enhancing click event tracking, improving detection accuracy, and automating event management workflows. Click events are detected through acoustic signals and can be filtered based on various criteria. The plugin stores detected click events and provides an API for seamless access, management, and analysis. |

Module Nodes

the module nodes are the building blocks for the flow-based programming. Each node represents a specific task or operation that can be performed by the module. The following table lists the available nodes for this module.

AI-based Click Detection

Detect click events using AI algorithms.

Metadata:

  • Name: ClickDetection
  • Tags: producer, sensor, click event
  • Category: Producer
  • Subcategory: Hardware > Clickevent

Description:

This node uses AI-based algorithms for click detection. Configure it with a version, name, and path before initiating the click detection process. Once initiated, the node outputs a click event.

Inputs: (1)

  • Get ClickEvent : Trigger to get ClickEvent data

Outputs: (1)

  • ClickEvent : Output for ClickEvent data

Configuration:

The following configuration parameters can be set for this node:

ClickModelConfig: { 
	
	# The version of the click detection model.
  version: string,
	# The name of the click detection model.
  model: string,
	# The minimum confidence level required for click detection.
  confidence: double,
	# The size of the model; valid options are small, medium, or large.
  size: string,
}

Report Click Event

Send a pre-configured notification for a click event.

Metadata:

  • Name: ClickEventNotification
  • Tags: notification, click event, frontend
  • Category: Notification
  • Subcategory: Frontend > Clickevent

Description:

This node sends a pre-configured notification for a click event. You can set the title, message, and level of the notification. It is useful for alerting the User Interface or other systems when a click event is detected.

Inputs: (1)

  • Trigger : The trigger for the notification.

Outputs: (1)

  • Notification : Output for Notification data

Configuration:

The following configuration parameters can be set for this node:

NotificationClickEventConfig: { 
	
	# The title of the notification.
  title: string,
	# The message content of the notification.
  message: string,
	# The severity level of the notification.
  level: string,
}

Click Sensor

A sensor that tracks clicks and creates click events.

Metadata:

  • Name: ClickSensor
  • Tags: producer, sensor, click event
  • Category: Producer
  • Subcategory: Hardware > Clickevent

Description:

This node detects click events using sound-based sensing. It can be configured with a version, name, and path, and then sends the click event to the subsequent node. It is useful in scenarios such as monitoring button presses or mechanical interactions.

Inputs: (0)

Outputs: (1)

  • ClickEvent : Output for ClickEvent data

Configuration:

The following configuration parameters can be set for this node:

SensorConfig: { 
	
	# The unique identifier of the Sensor.
  sensor_serial: string,
	# The version of the Sensor.
  version: string,
	# The name of the Sensor.
  name: string,
	# The path of the Sensor.
  path: string,
}

Filter Event by Concurrency

Detect concurrent click events.

Metadata:

  • Name: FilterConcurrencyClickEvent
  • Tags: filter, concurrency, click event
  • Category: Filter
  • Subcategory: Timediff > Clickevent

Description:

This node detects concurrent click events by comparing timestamps from different sensors. When the time difference between events is less than the configured time window, a concurrency event is generated.

Inputs: (1)

  • ClickEvent to filter : The ClickEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

ConcurrencyConfig: { 
	
	# The concurrency level for the ClickSensor.
  concurrency: int32,
	# The time window in milliseconds used to evaluate concurrency.
  timewindow: int32,
}

Filter Event by Direction

Filter click events by direction.

Metadata:

  • Name: FilterDirectionClickEvent
  • Tags: filter, direction, click event
  • Category: Filter
  • Subcategory: Direction > Clickevent

Description:

This node filters click events by direction. You can configure it to filter events based on directions such as left, right, up, or down. Only events matching the configured direction will pass through.

Inputs: (1)

  • ClickEvent to filter : The ClickEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeDirectionFilterConfig: { 
	
	# The direction to filter. Valid options are left, right, up, or down.
  value: string,
}

Filter Click Event by Probability

Filter click events based on probability.

Metadata:

  • Name: FilterProbabilityClickEvent
  • Tags: filter, probability, click event
  • Category: Filter
  • Subcategory: Probability > Clickevent

Description:

This node filters click events based on a probability value between 0 and 1. If the event’s probability exceeds the configured threshold, the click event is passed on.

Inputs: (1)

  • ClickEvent to filter : The ClickEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeProbabilityConfig: { 
	
	# The probability threshold
  probability: int32,
}

Filter Event by Workspace Name

Filter click events by workspace name.

Metadata:

  • Name: FilterWorkspaceClickEvent
  • Tags: filter, workspace, click event
  • Category: Filter
  • Subcategory: Workspace > Clickevent

Description:

This node filters click events by comparing the workspace name. The filter is case-sensitive and will only pass through events that exactly match the configured workspace name.

Inputs: (1)

  • ClickEvent to filter : The ClickEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeWorkspaceFilterConfig: { 
	
	# The case-sensitive workspace name used for filtering.
  value: string,
}

Filter Click Event by Worktime

Filter click events based on work hours.

Metadata:

  • Name: FilterWorktimeClickEvent
  • Tags: filter, worktime, click event
  • Category: Filter
  • Subcategory: Worktime > Clickevent

Description:

This node filters click events based on work hours. Work hours are defined using a start and end time in the format HH:MM and can be configured for each day of the week.

Inputs: (1)

  • ClickEvent to filter : The ClickEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeTimeConfig: { 
	
	# The start time of the day in the format HH:mm:ss.
  start: string,
	# The end time of the day in the format HH:mm:ss.
  end: string,
}

Random Click Event

Generate a random click event for testing purposes.

Metadata:

  • Name: RandomClickEvent
  • Tags: producer, random, click event, test
  • Category: Producer
  • Subcategory: Random > Clickevent

Description:

This node generates a random click event for testing. The event contains information such as timestamp, sensor ID, workspace, and click direction. The rate at which random click events are generated can be configured via an input trigger.

Inputs: (1)

  • Get ClickEvent : Trigger to get ClickEvent data

Outputs: (1)

  • ClickEvent : Output for ClickEvent data

Configuration:

The following configuration parameters can be set for this node:

RandomClickEventConfig: { 
	
	# The direction of the click event, which can be left, right, up, or down.
  direction: string,
	# The unique identifier for the sensor.
  sensor_identifier: string,
	# The version of the sensor.
  sensor_version: string,
	# The probability or confidence level that the event is correctly identified.
  confidence: int32,
	# The type of the click event. Examples include single, double, long, plug_connection, xlr_plug, lan_plug, click, pen, or bag_clip.
  click_type: string,
	# The workspace in which the click event occurred.
  workspace: string,
}

Save Click Event

Save a click event into the database and output a success message.

Metadata:

  • Name: SaveClickEvent
  • Tags: save, database, event, sql
  • Category: Consumer
  • Subcategory: Database > Clickevent

Description:

This node saves a click event in the database. It stores details such as timestamp, sensor ID, workspace, and click direction. The data is validated and stored in a SQLite database without any additional configuration. On a successful save, a success message is output. If the click event is not in the correct format, an error message is shown.

Inputs: (1)

  • ClickEvent to save : The ClickEvent to save in the database or file.

Outputs: (1)

  • Is Success : Success

Configuration:

No configuration required for this node.

Appendices