Options cannot be saved

Homepage Forums Generally Options cannot be saved

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #35830
    Frank
    Participant

    Hello,

    Since the update 2.4.0.(190) you can no longer save the options.  “Please check your entry and try again” What is this message about, I haven’t changed anything. From the PC as well as in the app. Hardware 3.2AC. Does anyone have an idea?

    And why is the system asking me “I’m not a robot” 5 times while I’m writing this?

    Thanks

    Frank

    #35832
    Admin
    Keymaster

    Hi, there is already firmware update 192, which works better

    #35833
    Frank
    Participant

    When I go to online firmware update, it says firmware is up to date.

    #35878
    Mathias Stöber
    Participant

    Hello,

    I also have the problem that some of the options are still not saved. Sometimes they are there, but after a restart they are gone again. This means that options and settings from the analog sensor configuration are always reset. Is there a way to debug this a little better?

    I have an Ospi here with a current checkout from the Github.

    VG Mathias

    #35879
    Mathias Stöber
    Participant

    Hi,

    I just tried something again. I had the entire config output via API. I first defined “Manual” as the watering method. There were no entries for the value “wto:{}” in the config that gave me the API. When I changed and saved the weather provider, the value was gone after I reopened the options and was reset to “apple” as the provider. I couldn't see any changes in the output of the config via API either. Next, I set the watering method to “ETO”. Afterwards I could also see settings under “wto:{…}” in the config from the API. When I then set the weather provider to “openmeteo”. This was in the config on the one hand

    “wto”: {
    “baseETo”: 0.15,
    “elevation”: 262,
    “key”: “”,
    “provider”: “OpenMeteo”
    }

    but then also displayed below

    “wtdata”: {
    “wp”: “OpenMeteo”,….}

    Is it possible that some options are saved in areas that are not always present in the config and there are gaps here? If I understand it correctly, the web interface is just the js file that runs on the web server, which then uses the API to actually make the changes. It seems as if there is a difference between what the interface shows, possibly as default, and what is then written to the sprinkler via API. Or if you change something in one place but then the default values ​​are written back in another place.

    If I can help in any way or test further, just let me know.

    VG Mathias

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.