Tried everything, can't get CPU and DHT22 sensor temp to show on the picture

[luckylukedev]

Hey!

I am using module (Reads Pi status) for Pi CPU temperature and I have dht22 sensor that writes data to txt file. They both show values in Overlay editor but I only get ??? on the actual picture. I did set-up variable type to number, even tried text. I have set up overlay method to module in settings. In logs it says "ERROR: ${CPUTEMP} has no variable type; check 'userfields.json'. Using '???' instead." But I did set-up variable type and format so I am completely lost now what else can I try. There were also some previous comments about setting Overlay to debug mode. In module manager and Module options I do have debug enabled.

[EricClaeys]

@Alex-developer any ideas?

@luckylukedev, variables have to be defined with a "type" inAll Variables and the added to Allsky Variables. It sounds like you did those, correct?
In the Overlay Editor what shows up for the CPU temperature if you click on the icon to display values?

[luckylukedev]

Correct, I did specify type as Number and then also tried with Text. You mean If I click "display sample data"? It shows me temp value, the same as if I check the cpu temp under System tab. Same happens with DHT22 data, sample data shows the same value I have written in text file. Just not working on the actual picture :(

[EricClaeys]

Can you attach the usefields.json file? It's probably in a subdirectory of allsky/config.
Do any of the other variables in those files work?

[Alex-developer]

Adding to Erics request can you please attach the following two files

~/allsky/config/overlay/config/fields.json
~/allsky/config/overlay/config/userfields.json

The '??' are displayed when the overlay module cannot determine what field type the field is. From memory I think the 'demo' data option defaults to 'text' if it cannot find the field type, this is on my list to fix already

Thanks

Alex

[luckylukedev]

Here are the files: Did I do something wrong as the file user fields is empty? or maybe skipped a step? But the cpu_temp should work out of the box as its part of the module right?
fields.txt
userfields.txt

[Alex-developer]

Here are the files: Did I do something wrong as the file user fields is empty? or maybe skipped a step? But the cpu_temp should work out of the box as its part of the module right? fields.txt userfields.txt

For some reason the field has not been added. Try the following

• In the overlay manager select the 'variable manager'
• Select the 'All Variables' tab and add the variable using the '+' icon. Please make sure you add a description and set the field type
• Save the changes
• Click on the 'variable manager' again and the fields should be in the 'Allsky variables' list, from there you can add it

[luckylukedev]

Yes I did this a couple of times already but the outcome is always the same, fields are not updated on the actual picture :( Something I noted: when I add variable from "All variables" to "Allsky variables" its there and I am able to add it to the overlay, but once I save the overlay changes and variable shows ??? on the actual picture, also the variable is removed from "Allsky variables" so I have to again move it from "All variables" if I want to try it again. Is there some workaround maybe? That I would manually add variables to userfields.json maybe?

[Alex-developer]

After you add the variable try saving the changes in the variable manager then re open the variable manager to add the field.

[luckylukedev]

I did, nothing changes. But I did some more testing and when I add variable from "all variables" to "Allsky variables" its stays there only until I change the screen, even though I select Save on variable manager and then on Overlay editor. When I switch to Live view and back the Overlay manager the variable is gone-like I never added it from "all variables" to "Allsky variables". I might do another clean install of the allsky software but I did that before as well and rebooted PI multiple times but still nothing :(

[Alex-developer]

Could you check the lightpd error log /var/log/lighttpd/error.log and see if there are any errors in it please

[luckylukedev]

checked, attaching the file. I see some errors but can't figure out the reason for them
error.txt

[EricClaeys]

Somehow the files in ~/allsky/config/modules had their permissions changed. The installation script should have set them correctly.
This is what they should be when running as the "pi" user:

To fix:

cd ~/allsky/config/modules
ls -l        # let us know what the output is
sudo chown pi *
sudo chgrp www-data *
sudo chmod 664 *

If you still have allsky-OLD, please run:

ls -l ~/allsky-OLD/config/modules

and let us know what it says.

[luckylukedev]

This is the output after I ran your commands. (Sorry I didn't save the first ls -l output, jumped into the fix too fast):
total 44
-rw-rw-r-- 1 pi www-data 368 Nov 8 18:13 module-settings.json
-rw-rw-r-- 1 pi www-data 2645 Nov 11 17:10 postprocessing_day.json
-rw-rw-r-- 1 pi www-data 2 Nov 11 17:11 postprocessing_daynight.json
-rw-rw-r-- 1 pi www-data 2331 Nov 11 20:41 postprocessing_night.json
-rw-rw-r-- 1 pi www-data 2331 Nov 8 18:13 postprocessing_night.json-last
-rw-rw-r-- 1 pi www-data 2 Nov 11 06:42 postprocessing_nightday.json
-rw-rw-r-- 1 pi www-data 9171 Nov 11 20:41 postprocessing_periodic.json
-rw-rw-r-- 1 pi www-data 8028 Nov 4 20:29 postprocessing_periodic.json-last

But sadly the fix didn't work :( I think I will just do complete clean install again and see if that fixes anything

[EricClaeys]

I prefer you not do a reinstall. We won't know what the problem is so it won't help the next person with the issue.
What does /var/log/lighttpd/error.log say now?
If it's still a permissions issue, run ls -ld ~/allsky/config/modules

[luckylukedev]

It still said permission problem, ran your command and from what I can tell nothing changed, here is the error log after I ran the
errorlog2.txt

[EricClaeys]

There weren't any new errors in /var/log/lighttpd/error.1
To make it easier to see other errors in that file, run sudo truncate -s 0 /var/log/lighttpd/error.1. That will clear the file.

Please run:

ls -ld ~/allsky/config/modules

Mine is:

pi:~/allsky/config/modules $ ls -ld ~/allsky/config/modules
drwxrwxr-x 2 pi www-data 4096 Oct 28 19:31 /home/pi/allsky/config/modules

The "d" means it's a directory.
The first "rwx" means the owner of the directory "pi" can read and write to the directory as well as list files.
The second "rwx" is the same but for the group owner "www-data" which is the web server.
It's possible yours doesn't allow the web server to create temporary files in the directory.

[luckylukedev]

I believe I did as instructed, this is the output I got:
pi@allsky:~/allsky/config/modules $ ls -ld ~/allsky/config/modules
drwxrwxr-x 2 pi www-data 4096 Nov 8 18:13 /home/pi/allsky/config/modules

[EricClaeys]

@luckylukedev, are you still having the problem of the variable you add to the Allsky Variables tab disappearing after you leave the Overlay Editor and then return? And there are no longer any messages in /var/log/lighttpd/error.log?

[luckylukedev]

yes, the problem with variable disappearing is still here. Here is what I have now in error.log file:
2023-11-12 00:00:28: server.c.1787) logfiles cycled UID = 0 PID = 48586

[meins1969]

Hello, I have exactly the same problem, for example I can display the CPU temperature in the editor, but only ??? appear in the image. For me the variables also disappear when I leave the editor. I am also interested in a solution to the problem.
I have another question, how can I display my Extra Text File (/home/servi/Temp.txt) in the Overlay Editor? There are my values ​​from the DHT22 sensor.
Michael from Germany

[Alex-developer]

Can you run a couple of commands for me and add the output

1. From the allsky directory

cd ~/allsky
find . -not -path '*/.*' -type d -ls

2. From the allsky/config directory

cd ~/allsky/config
ls -alR

I have just tried a clean install of Bullseye and its working fine for me with a DHT22 so I suspect some permissions have been messed up somewhere. There is an issue in the modules folder as the error from the lighttpd log is indicating that the module manager cannot create the backup copy of the modules flow

Thanks

Alex

[Alex-developer]

Thanks for the files, all seems ok in them.

Could you do me a favour and follow these steps

1. Goto the overlay manager
2. Click on the 'Variable Manager'
3. Select the 'All variables tab'
4. Pick any field with the plus button enabled and click it
5. Set the description to 'test'
6. Set the field type to 'text'
7. Click the 'Save Chnages' Button
8. Click the 'Save changes' button to save and close the variable manager
9. Post the contents of ~/allsky/config/overlay/config/userfields.json

Thanks

Alex

[luckylukedev]

Did as instructed, its not getting saved, that's all there is in use fields.json:
{
"data": []
}

[Alex-developer]

Thanks for doing that. I have to admit that I am a little stumped by this one so lets try some other things !

Can you run

chmod -R 777 ~/allsky/config/overlay

Then try the field again.

NOTE: This is not a solution and just a test, setting permissions to 777 is a bad idea but I just want to see if it helps

Could you also inspect the page, right click and select 'inspect' and see if there are any errors in the 'console' tab when attempting to add the field.

Thanks

Alex

[luckylukedev]

still doesn't work when I changed permission. I also inspected the website and no errors were seen :(. Maybe it's time I try clean install? :)

[EricClaeys]

@luckylukedev, if you don't mind, we prefer if you don't do a clean install until @Alex-developer fins out what's causing the problem. Someone else reported the same thing so it's something we need to fix asap.

[MadMacMad]

hello,
well had the same because did not read the manual... ;-)
this is my bash script:

#!/bin/bash
set -e  # Script stoppt bei einem Fehler
 
while true; do  # Endlosschleife
    extra="/home/holle/allsky/config/overlay/extra/extra.txt"
 
    # Berechne Uptime
    HH_uptime_seconds=$(awk '{print $1}' /proc/uptime)
    HH_hours=$(echo "$HH_uptime_seconds / 3600" | bc)
    HH_minutes=$(echo "($HH_uptime_seconds % 3600) / 60" | bc)
    HH_uptime=$(printf "%02d:%02d" $HH_hours $HH_minutes)
 
    HH_start=$(sunwait list set angle -6 52.2153N 7.2828E)
    HH_end=$(sunwait list rise angle -6 52.2153N 7.2828E)
    HH_gpu=$(/usr/bin/vcgencmd measure_temp | awk -F "[=']" '{print $2}')
    HH_cpu_raw=$(</sys/class/thermal/thermal_zone0/temp)
    HH_cpu=$(echo "scale=1; $HH_cpu_raw / 1000" | bc)
 
    if [ -f "/sys/bus/w1/devices/28-030497941554/w1_slave" ]; then
        tempread=$(cat /sys/bus/w1/devices/28-030497941554/w1_slave)
        HH_temp=$(echo "scale=1; ${tempread##*=} / 1000" | bc)
    else
        HH_temp="N/A"
    fi
 
    # Lies Daten vom DHT22 Sensor
    read HH_hum HH_temp_int < <(python3 /home/holle/dht.py)
 
    # Schreibe alle gesammelten Daten in die extra.txt-Datei
    {
        echo "HH_up=$HH_uptime"
        echo "HH_Start=$HH_start"
        echo "HH_End=$HH_end"
        echo "HH_Outside=$HH_temp"
        echo "HH_BoxRH=$HH_hum"
        echo "HH_BoxTemp=$HH_temp_int"
        echo "HH_GPU=$HH_gpu"
        echo "HH_CPU=$HH_cpu"
    } > "$extra"
 
    sleep 60  # Warte 60 Sekunden bis zum nächsten Durchlauf
done

it writes a .txt to this location as noted in the manual if you want to read it in Overlay... allsky/config/overlay/extra/extra.txt
the content looks like this:

HH_up=08:47
HH_Start=17:18
HH_End=07:13
HH_Outside=2.5
HH_BoxRH=37.7
HH_BoxTemp=18.8
HH_GPU=40.4
HH_CPU=40.4

important is a proper name and after the = a value like shown...
than you will see those Names with AS_ in front of your name in the Variable Manager under All variables tab ...
you can also search for...

than hit the plus button ... and give it a proper name
Click the 'Save changes' button and than
Click the 'Save changes' button to save and close the variable manager...
now you see you new created overlay in left corner and can change as usual ...
once you know how it works... it's amazing what it has to offer also for the future ...

[luckylukedev]

Hello! I did like you wrote it, or at least I think I did, maybe you can spot some problem in my script. But the thing is that I see variables in the variable manager and they actually show correct values inside the Overlay editor if I select "display sample data" but on the actual picture in live view I only get ???.

<import Adafruit_DHT
import time

# DHT22 sensor configuration
DHT_SENSOR = Adafruit_DHT.DHT22
DHT_PIN = 2  # GPIO pin where the DHT22 sensor is connected

# File path to store the temperature data
file_path = "/home/pi/allsky/config/overlay/extra/temperature_logger.txt"

# Main loop to read and log temperature data every 60 seconds
while True:
    humidity, temperature = Adafruit_DHT.read_retry(DHT_SENSOR, DHT_PIN)

    if temperature is not None:
        # Format the temperature value with two decimal places
        formatted_temperature = "{:.2f}".format(temperature)

        # Write the temperature data to the text file
        with open(file_path, 'w') as file:
            file.write(f'DHT22_temperature:{formatted_temperature}\n')

        print(f"Logged temperature: {formatted_temperature}")

    else:
        print("Failed to retrieve temperature data. Please check the sensor connection.")

    time.sleep(60)  # Wait for 60 seconds before the next reading
>

And the .txt file looks like this:
DHT22_TEMP=18.60

[EricClaeys]

@luckylukedev, how does this line in your script:

file.write(f'DHT22_temperature:{formatted_temperature}\n')

give this line in the output file?

DHT22_TEMP=18.60

I would have thought it would produce DHT22_temperatore:18.60

[luckylukedev]

Sorry, I copied old version of the script from my editor. I changed this part later and here is the script that is actually running on my Pi.

I have this script in the home directory of PI, maybe this is the problem and I should have it in the allsky directory? As I have very limited experience with python and Pi I am sure I might have made some basic mistake in my script or permissions or smth else, but my script does get temperature written in the text file and correct number is shown with the "display sample data" in overlay editor. Further more, the same problem also happens when trying to use Module to show PI CPU temperature, and I didn't create that script so it's probably working as it should be. This is also why I turned for help. The only think I can think off to maybe fix this with my knowledge is performing clean install and write new script, this time using json for data writing. But than again, Reads PI data module uses json and still doesn't work for me :(

import Adafruit_DHT
import time


# DHT22 sensor configuration
DHT_SENSOR = Adafruit_DHT.DHT22
DHT_PIN = 2  # GPIO pin where the DHT22 sensor is connected

# File path to store the temperature data
file_path = "/home/pi/allsky/config/overlay/extra/temperature_logger.txt"

# Main loop to read and log temperature data every 60 seconds
while True:
    humidity, temperature = Adafruit_DHT.read_retry(DHT_SENSOR, DHT_PIN)

    if temperature is not None:
        # Format the temperature value with two decimal places
        formatted_temperature = "{:.2f}".format(temperature)

        # Write the temperature data to the text file
        with open(file_path, 'w') as file:
            file.write(f'DHT22_TEMP={formatted_temperature}\n')

        print(f"Logged temperature: {formatted_temperature}")

    else:
        print("Failed to retrieve temperature data. Please check the sensor connection.")

    time.sleep(60)  # Wait for 60 seconds before the next reading

[luckylukedev]

So, I solved my issue by using legacy implementation as seen from discussion with @meins1969 , adjusted my scripts so they write all parameters I need to one .txt file and it works like a charm with legacy overlay system. @Alex-developer @EricClaeys thank you for all the support you provided. Its great project and thank you for all your effort!

[luckylukedev]

But it does seem there is a bug in there somewhere, I am not using latest Pi OS and had the same problem a while back and clean install didn't solve it, so I am guessing it would not solve it now as well...

[meins1969]

Hello, I hate to get involved in your conversation, but as I mentioned above, I have the same problems with the Pi Status Module. The overlay editor shows me the values ​​such as: CPU temperature is correct in test mode, but in the live image I only see ??? I am also very interested in a solution. Greetings Michael

[Alex-developer]

Can you let me have a little more info

1. What Pi are you using
2. What version of allsky

Thanks

Alex

[meins1969]

Hello Alex I use a Raspberry Pi4 B 4 GB with allsky Version: v2023.05.01_03
Michael

[meins1969]

Hello Alex,
Here are two examples, once in the editor where the CPU temperature is displayed and once in the live image where are only ??? be shown.

[EricClaeys]

@meins1969, @Alex-developer is working hard on several bugs, I believe including this one, so he may not be able to respond for a while.
Quite a few people have installed the new Bookworm operating system and it changed a few things that broke Allsky. Sigh...

[meins1969]

Hello Eric, hello Alex, that's no problem at all, I'm still very proud of your work and that you make all of this available to us. So take it easy. In the meantime I just use the classic overlay method, which works perfectly. So again, big compliments for your fantastic work.
Michael

[MadMacMad]

hello,
well that is not a bug.... ;-)
you have to add all those via Variable Manager...
if you don't do it like that it doesn't work....
everything is working fine ... testet all if you add via Variable Manager...
that's what most doing wrong when first start with the Overlay Manager ;-)

https://raw.githubusercontent.com/thomasjacquin/allsky/master/html/documentation/overlays/overlays.html

[MadMacMad]

If you see a variable displayed on the overlay as ??? it usually means the variable is undefined - either it's not in the Variable Manager at all (could be a typo), or is only in the All Variables tab. The variable needs to be defined and copied to the Allsky Variables tab.
Undefined variables will have a line in /var/log/allsky.log like: ERROR: ${T2} has no variable type; check 'fields.json'.
If a variable is displayed as ?? it usually means the variable's formatting is incorrect, for example, you tried to display a number as a date. Make sure the formatting is valid for the type of variable - click on the [?] icon to see valid formats for each type of variable.
Incorrectly formatted variables will have a line in /var/log/allsky.log like: ERROR: Cannot use format '%a' on Number variables like ${GAIN}..

that's from the documentation...
check the log first : /var/log/allsky.log

how can I display the data from my txt file in the overlay manager?
you have to write the text file with the values to this folder:

and here is how the text file looks:

[meins1969]

So I've now managed to get the CPU temperature to be displayed. I actually always forgot to save the variable table. I always thought that if I saved the variable then that was it, I had to save the whole table, I never noticed. Nevertheless,

[meins1969]

Now everything works as it should for me :-)
I would like to thank you all once again for being so patient with me, I´m a beginners. Kind regards from Germany, Michael

[Vejbymats]

Thank You meins1969!
I had the same problem!

[brianboru82]

Yes thanks, that 'Save Changes' button at the bottom right I missed as well.

[meins1969]

OpenWeatherMap Module
Hello, I have installed the OpenWeatherMap module. The wind direction is shown to me as a number. Shouldn't a letter be displayed here as the cardinal direction?
Michael

[EricClaeys]

@Alex-developer, comment?

[Alex-developer]

No the wind direction is reported as a decimal degrees. We just return the raw data from the API. We could add a cardinal heading based off of the decimal degrees

{
    "coord": {
        "lon": 0.2,
        "lat": 52.4
    },
    "weather": [
        {
            "id": 803,
            "main": "Clouds",
            "description": "broken clouds",
            "icon": "04d"
        }
    ],
    "base": "stations",
    "main": {
        "temp": 7.63,
        "feels_like": 4.79,
        "temp_min": 7.12,
        "temp_max": 8.66,
        "pressure": 1002,
        "humidity": 36
    },
    "visibility": 10000,
    "wind": {
        "speed": 4.63,
        "deg": 230
    },
    "clouds": {
        "all": 75
    },
    "dt": 1704368090,
    "sys": {
        "type": 2,
        "id": 2012440,
        "country": "GB",
        "sunrise": 1704355732,
        "sunset": 1704383908
    },
    "timezone": 0,
    "id": 2633751,
    "name": "Witchford",
    "cod": 200
}```

[meins1969]

Hello Alex,
I have now written myself a small script to display the wind in cardinal directions and to convert the wind speed from m/s to km/h.

Wind.sh

# read prameter from json-file
import json

def convert_wind_dir_deg_to_wind_dir_str(wind_dir_deg):
    # return 'N/A' if something goes wrong
    wind_dir_str = "N/A"
    # array of wind directions as strings
    wind_dir_strings = ['N', 'NNO', 'NO', 'ONO', 'O', 'OSO', 'SO', 'SSO', 'S', 'SSW', 'SW', 'WSW', 'W', 'WNW', 'NW', 'NNW']
    # empty dict
    wind_dir_dict = {}
    # initialize dict with degrees 
    for i in range(16):
        wind_dir_dict[wind_dir_strings[i]] = {'s':i*22.5, 'e':(i+1)*22.5}

    # find matching by looping over all
    for wd in wind_dir_dict:
        if (wind_dir_deg+11.25)%360>=wind_dir_dict[wd]['s'] and (wind_dir_deg+11.25)%360<wind_dir_dict[wd]['e']:
            wind_dir_str = wd
            # break if found
            break

    return wind_dir_str

while True:

    # Opening JSON file
    f = open('/home/servi/allsky/config/overlay/extra/openweather.json')

    # returns JSON object as a dictionary
    data = json.load(f)

    # Closing file
    f.close()

    # access the parameter we are interested in
    wind_direction_deg = data['AS_OWWINDDIRECTION']['value']
    windspeed = data['AS_OWWINDSPEED']['value']
    windmax = data['AS_OWWINDGUST']['value']


    # convert to 'normal' wind-direction via function convert_wind_dir_deg_to_wind_dir_str()
    wind_direction_str = convert_wind_dir_deg_to_wind_dir_str(wind_direction_deg)
    # do whatever with the variable


    # Werte in  wind.txt schreiben
    wind_speed = windspeed *3.6
    wind_max = windmax *3.6
    datei = open ("allsky/config/overlay/extra/wind.txt", "w")
    datei.write ("nHH_Windspeed = {}\nHH_Windmax = {}\nHH_Windirection = {}\n".format(
wind_speed, wind_max, wind_direction_str))
    datei.close ()

    time.sleep(60.0)

Best regards from Germany
Michael

https://zinke-berlin.de/weathercam/index.php

[Alex-developer]

Looks good :-) I'll add something to the ,module to do the same

[Alex-developer]

I have added the cardinal wind direction to the module, it will be a few days before its available as its alongside a lot of other changes. I'll let you know when its available. In case you are interested I did it like this

    try:
        cardinals = ['N', 'NNE', 'NE', 'ENE', 'E', 'ESE', 'SE', 'SSE', 'S', 'SSW', 'SW', 'WSW','W', 'WNW', 'NW', 'NNW', 'N']
        cardinal = cardinals[round(degrees / 22.5)]
    except Exception:
        cardinal = 'N/A'
    
    return cardinal

[ws7m]

Hi all,

I'm getting the same issue without a resolution yet. Sorry to open what may be an older thread.

I believe I am on the latest version of allsky. I am using the overlay module.

I have a python script writing this data to an extra text file:

WS7M_TEMP=41.36
WS7M_DEWP=26.42
WS7M_HEAT=Off
WS7M_WIND=1.0
WS7M_WDIR=339
WS7M_WGST=1.9

The file is ~/allsky/config/overlay/extra/wxinfo.txt

When I go into the overlay editor, bring up variable manager, all variables. No matter what I try for a variable name, hitting save highlights the variable name field in red. So obviously its not happy. But NOTHING seems to make it happy.

So I am pretty sure my issue is I cannot add the variables from the above file because I can't get them in past the variable manager editor.

And like the others in this thread currently the values are displayed as ??? on the image.

[ws7m]

Ok sorry... After some poking around I found that when putting your varaible in the variable manager editor you need to include the ${} on it. That made it work. Might suggest adding that to the editor dialog as an example.

[meins1969]

Hello Alex, I now have a weather station from Thinkerforge. https://www.tinkerforge.com/de/shop/outdoor-weather-station-ws-6147.html.This works very well with a Raspberry and the Allsky software. If you are interested in writing a module for it, I can send you my existing script files. Greetings Michael
https://zinke-berlin.de/Wetterstation/

[jsanchez73]

Was this issue ever solved? I see some people were not properly saving the Variable table and others moved to Legacy module. But Is there a fix or an explanation of how to solve the problem? Me and a friend are trying to make this work but keep stumping with the same problem. The variable appears in All Variables, we add the variable to Allsky Variables, populating the type, description and format, we save evertyhing, the variable appears with the current value in the editor, but in live view it only shows ???. The allsky.log says the same as described in the OP, ERROR: ${CPUTEMP} has no variable type; check 'userfields.json. When we check user field.json it is empty. We are temped to manually edit userfield.json. Thanks in advance,

Jose

[Alex-developer]

Thanks Alex, just let me know

Try setting the permissions to 664

I dont currently have a pi running the current release, I have upgraded them all but if that doesnt work will install the current release to check the permissions for you

[jsanchez73]

Thanks a lot Alex, We'll do that and try again

[jsanchez73]

Hello again Alex,

We tried with the new permissions and still get the same issue. Even when we save the overlay editor work, when trying to exit that page to go to live view it warns that some information might be lost if we leave the page. But the save button is disabled at that point, so no way to save again the work.

As this is not my allsky it is a little difficult to make tests, as I need access from the owner. He also does not feel like making a clean install of the allsky to see if this solves the issue. For the time being we can manage to add fields in the overlay by editing the userfields.json file. So we can live with that.

Thanks again for all the support,

Jose

[Alex-developer]

Hello again Alex,

We tried with the new permissions and still get the same issue. Even when we save the overlay editor work, when trying to exit that page to go to live view it warns that some information might be lost if we leave the page. But the save button is disabled at that point, so no way to save again the work.

As this is not my allsky it is a little difficult to make tests, as I need access from the owner. He also does not feel like making a clean install of the allsky to see if this solves the issue. For the time being we can manage to add fields in the overlay by editing the userfields.json file. So we can live with that.

Thanks again for all the support,

Jose

Jose

I have done a clean install of the current release and below are all of the permissions, owner and groups for all files in the config folder.

Hope it helps

Alex

pi@pi4:~/allsky $ tree -pugfi ./config/
[drwxrwxr-x pi www-data] ./config
[-rw-rw-r-- pi www-data] ./config/cc.json
[-rw-rw-r-- pi www-data] ./config/cc_ZWO_ASI120MC-S.json
[-rw-rw-r-- pi www-data] ./config/config.sh
[-rw-rw-r-- pi www-data] ./config/ftp-settings.sh
[drwxrwxr-x pi www-data] ./config/logs
[-rw-rw-r-- pi www-data] ./config/logs/install.sh.log
[-rw-rw-r-- pi www-data] ./config/logs/libatlas.log
[-rw-rw-r-- pi www-data] ./config/logs/lighttpd.install.log
[-rw-rw-r-- pi www-data] ./config/logs/make_all.log
[-rw-rw-r-- pi www-data] ./config/logs/make_deps.log
[-rw-rw-r-- pi www-data] ./config/logs/make_install.log
[-rw-rw-r-- pi www-data] ./config/logs/msttcorefonts.log
[-rw-rw-r-- pi www-data] ./config/logs/PHP_modules.log
[-rw-rw-r-- pi www-data] ./config/logs/python3-full.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.10.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.11.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.12.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.13.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.14.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.1.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.2.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.3.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.4.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.5.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.6.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.7.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.8.log
[-rw-rw-r-- pi www-data] ./config/logs/Python_dependencies.9.log
[-rw-rw-r-- pi www-data] ./config/logs/rsyslog.log
[-rw-rw-r-- pi www-data] ./config/logs/status.txt
[drwxrwxr-x pi www-data] ./config/modules
[-rw-rw-r-- pi www-data] ./config/modules/module-settings.json
[-rw-rw-r-- pi www-data] ./config/modules/postprocessing_day.json
[-rw-rw-r-- pi www-data] ./config/modules/postprocessing_daynight.json
[-rw-rw-r-- pi www-data] ./config/modules/postprocessing_nightday.json
[-rw-rw-r-- pi www-data] ./config/modules/postprocessing_night.json
[-rw-rw-r-- pi www-data] ./config/modules/postprocessing_periodic.json
[-rw-rw-r-- pi www-data] ./config/options.json
[drwxrwxr-x pi www-data] ./config/overlay
[drwxrwxr-x pi www-data] ./config/overlay/config
[-rw-rw-r-- pi www-data] ./config/overlay/config/autoexposure.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/fields.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/formats.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/oe-config.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/overlay.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/overlay-RPi.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/overlay-ZWO.json
[-rw-rw-r-- pi www-data] ./config/overlay/config/userfields.json
[drwxrwxr-x pi www-data] ./config/overlay/extra
[drwxrwxr-x pi www-data] ./config/overlay/fonts
[-rw-rw-r-- pi www-data] ./config/overlay/fonts/moon_phases.ttf
[drwxrwxr-x pi www-data] ./config/overlay/images
[-rw-rw-r-- pi www-data] ./config/overlay/images/compass-blue.png
[-rw-rw-r-- pi www-data] ./config/overlay/images/compass-green.png
[-rw-rw-r-- pi www-data] ./config/overlay/images/compass-grey.png
[-rw-rw-r-- pi www-data] ./config/overlay/images/compass-red.png
[drwxrwxr-x pi www-data] ./config/overlay/imagethumbnails
[-rw-rw-r-- pi www-data] ./config/overlay/imagethumbnails/compass-blue.png
[-rw-rw-r-- pi www-data] ./config/overlay/imagethumbnails/compass-green.png
[-rw-rw-r-- pi www-data] ./config/overlay/imagethumbnails/compass-grey.png
[-rw-rw-r-- pi www-data] ./config/overlay/imagethumbnails/compass-red.png
[drwxrwxrwx pi pi ] ./config/overlay/tmp
[drwxrwxrwx pi pi ] ./config/overlay/tmp/overlay
[-rw-r--r-- pi pi ] ./config/overlay/tmp/overlay/de421.bsp
[drwxrwxrwx pi pi ] ./config/overlay/tmp/overlay/tle
[-rw-rw-r-- pi www-data] ./config/settings.json
[-rw-rw-r-- pi www-data] ./config/settings_ZWO_ASI120MC-S.json

[jsanchez73]

Thanks a lot Alex!!! It certainly can help.

[EricClaeys]

@jsanchez73, please also run:

grep ERROR /var/log/allsky.log