Practical recipe
Add feedback with Events.
Make the panel show what actually happened on the connected device or application.
Why feedback matters
A sent value is not always the current value.
A command expresses what DeviceJockey wants the target to do. An event reports a state or value and lets the item show the result. This also keeps the panel correct when someone changes the target elsewhere.
General pattern
Connect an incoming message to an item change.
Identify the returned state
Find the interface event, path, topic, address, or function that represents the state you need.
Show the interface-specific event or address and a real received example value.
recipe-feedback-01-source.jpegAdd the Event to the item
Select the interface and configure the fields required to match the incoming information.
Show the complete Event configuration and clearly identify the matching fields.
recipe-feedback-02-event.jpegChoose a Remote Option
Decide which item change the Event should perform, such as setting a value, changing a light, or updating displayed text.
Show the Remote Option list and highlight the option used by the example.
recipe-feedback-03-remote-option.jpegTest outside DeviceJockey
Change the target from another controller or directly in the application. Confirm that the DeviceJockey item updates without being touched.
Show the target and DeviceJockey item with the same reported state or value.
recipe-feedback-04-result.jpegReference
Understand the two parts in detail.
Continue with the conceptual pages when you need every available behavior rather than one practical recipe.