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
I note the discussion around creating sensors here #9 , and also that commit aaddd2b implemented capture of the openwrt.exec service call stdout return on the event bus.
The resulting event from calling the /usr/bin/uptime command example from the readme is:
However I have confirmed that the terminal command ubus call system info | jsonfilter -e "@['uptime']" directly returns OpenWRT system uptime in seconds, and suggest that implementing this as a sensor within the integration is a more elegant and user friendly solution.
Thank you for your work on this in any case; it is already very useful in monitoring OpenWRT connectivity within Home Assistant.
The text was updated successfully, but these errors were encountered:
I note the discussion around creating sensors here #9 , and also that commit aaddd2b implemented capture of the
openwrt.exec
service call stdout return on the event bus.The resulting event from calling the
/usr/bin/uptime
command example from the readme is:For those with a moderate amount of Home Assistant knowledge, it should therefore be possible to setup an automation to periodically call the
openwrt.exec
service (https://www.home-assistant.io/docs/automation/trigger/#time-pattern-trigger), and capture the output within a template trigger sensor (https://www.home-assistant.io/integrations/template/#trigger-based-template-binary-sensors-buttons-images-numbers-selects-and-sensors). I haven't tried it yet; capturing and reformatting the output looks a little tricky, but doable.However I have confirmed that the terminal command
ubus call system info | jsonfilter -e "@['uptime']"
directly returns OpenWRT system uptime in seconds, and suggest that implementing this as a sensor within the integration is a more elegant and user friendly solution.Thank you for your work on this in any case; it is already very useful in monitoring OpenWRT connectivity within Home Assistant.
The text was updated successfully, but these errors were encountered: