#1036 [bug] π There is a bug where a new workflow is not executed until you switch the Trigger type
Hey y'all π
You, your setup, your use cases... are different from mine and everyone's else's. I also don't like implementing really narrow features, that help only a handful of users.
So I thought, well, how about I let YOU to change the application behavior?
Here come π Workflow Automations π₯³
So, what can you do? You can change any Device field, or delete the Device itself, if any number of custom conditions are fulfilled. For example, you can UN-archive a device if it's detected online. Or group devices with a specific name or vendor into a group. Or assign devices to a location depending on the IP they get...
These are only examples, but I think you get the idea. Happy tinkering and automating! Share your workflows in Discord or GitHub Discussions.
There are also some smaller improvements, so check them out below β¬
πDocs updates
- Better Notification processing docs π
- Workflows Overview π
βSettings
- A new
LUCIRPC_only_reachable
setting on theLUCIRPC
to be able to import reachable or unreachable devices from OpenWRT #1010 π
πPlugins
ICMP
failed if the settingLOG_LEVEL
was set toverbose
or higher #1025 β¨MQTT
didn't send updates for all fields, only some #1019 β¨
πΌ UI
- Cleanup of the Network topology view β¨
π Core app updates
Internal changes affecting the whole app and usually significant to developers π©βπ»π¨βπ»
LOADED_PLUGINS
docker environment variable didn't work with the defaultapp.conf
#1023 β¨- Custom values of the
devParentNode
anddevParentPort
field were overwritten by plugins #1021 β¨
Other Info
π - New features | β¨ - Fixes & Improvements | β - Possibly breaking changes | π§ͺ - Experimental/work in progress |
---|
What's Changed
- Changing absolute path URL to relative path URL in devices.php by @cvc90 in #1022
- Changing absolute path URL to relative path URL in userNotifications.php by @cvc90 in #1024
- Next release - Workflow work by @jokob-sk in #1029
Full Changelog: v25.3.1...v25.4.1