PISTATUS?

[Jonk2]

@Alex-developer what happened to PISTATUS?

[Alex-developer]

@Alex-developer what happened to PISTATUS?

If you mean the pistatus module its moved into the core allsky rather then the user modules

Alex

[Jonk2]

ok thanks I'll dig a bit deeper.

[Jonk2]

Comparing the 2 PIs, both have AS_CPUTEMP with a value.

On the 'non working' PI1 it shows this:

On the 'working' PI2 it shows this:

[Jonk2]

In the overlay editor:

On the actual overlay:

[EricClaeys]

@Jonk2 the variable has to be in the Allsky Variables list which means it's defined. Did you look in the log file per my last post?

@Alex-developer both screenshots show an active plus sign button which implies the variable is NOT in Allsky Variables on either Pi. Any ideas?

[Alex-developer]

@Jonk2

This looks like you have differing setups between the two Pi's so a few things to check.

The allsky_pistatus.py module should be in the ~/allsky/scripts/modules directory. If its in either /etc/allsky/modules or /opt/allsky/modules then please remove it from those directories.

The module locations have moved and some modules moved into core allsky. If you have a /etc/allsky directory then you are not running the latest, If this is the case then let me know and I will let you know how to sort it.

Alex

[Jonk2]

@Alex-developer On the PI that won't show the CPU temp on the overlay, I don't have /etc/allsky/modules but I do have /opt/allsky/modules, but that folder is empty.

The allsky_pistatus.py file is in the /allsky/scripts/modules folder:

The version I have was installed on 19/03/23.