Telemetry widget fails to load on dashboard

[MaxMax99]

Hi,

I have telemetry enabled for the ET Pro ruleset, but the telemetry widget fails to load with this error in the backend logs.

I'm running OPNsense in a VM for tesing and I am on the Dev branch.

Thanks for your help.

[franco]

Can you run that command in single quotes manually and see what it complains about?


Cheers,
Franco

[MaxMax99]

Sure, here's what it complains about (the screenshot is too large to be uploaded here) :

"root@ClosedSense:~ # /usr/local/opnsense/scripts/etpro_telemtry/sensor_info.py

Traceback (most recent call last):
  File "/usr/local/opnsense/scripts/etpro_telemtry/sensor_info.py", line 33, in <module>
    import telemetry
  File "/usr/local/opnsense/scripts/etpro_telemtry/telemetry/__init__.py", line 34, in <module>
    import netaddr
ModuleNotFoundError: No module named 'netaddr'
root@ClosedSense:~ # "

[franco]

To my surprise you seem to be using the development version (and checking again you said so, sorry for not seeing it earlier) and it was already fixed for upcoming 25.7.4 but it also didn't break in 25.7.3:

https://github.com/opnsense/plugins/commit/877ebf20e

That's not patchable, but you can use the following for now:

# pkg install -A py311-netaddr

The -A is for automatic. If you perform an update it may be removed again but in 25.7.4 the commit above will cause the dependency to be registered again.


Cheers,
Franco

[BrandyWine]

The widget for me never worked
https://forum.opnsense.org/index.php?topic=48493.msg244920#msg244920

[MaxMax99]

yeah, it display "proofpoint" if you remove it then add it again but with no info and when you leave the dashboard and come back it fails to load again

[BrandyWine]

yeah, it display "proofpoint" if you remove it then add it again but with no info and when you leave the dashboard and come back it fails to load again

Yep. It's broken.

[franco]

Now a proper bug report would go a long way compared to bro-opting on an already fixed issue reported here walking back concluding "it" is "broken". I mean you just saw how the support process works and chose to undermine it.


Cheers,
Franco

[MaxMax99]

Do you need any more infos guys?

[BrandyWine]

Now a proper bug report would go a long way compared to bro-opting on an already fixed issue reported here walking back concluding "it" is "broken". I mean you just saw how the support process works and chose to undermine it.


Cheers,
Franco

Again, a widget, which has nothing to do with the functionality of the actual plugin, hence I am not doing the effort to create a bug report for a non-working widget. I only do effort on functionality issues (i226-V nvm, text that is not readable in gui, etc), and even then I probably won't open a bug report.

I stated the facts, widget is(was) broken.
Where/when did it get fixed?

Cheerio.