[Samer]

There is no reason to use the image, honestly.

Just instal OSPi yourself which uses already installed tools.

Simply run: git clone https://github.com/Dan-in-CA/OSPi

[Samer]

@ottorino Sorry to hear about your issue. Which device are you on? Also, the link should open an email composer with the data inside the body of the email. Before sending it, is the body filled out or empty?

Which firmware and device are you using?

Thanks!

[Samer]

The idea behind the XML/JSON is you can add things like modules. You basically build a small installer in OSPi that reads the info and does what’s needed. For example:

OSPi-Plugins <--- Main repo

weather_adj/   <---top dir, represents plugin

templates/   <--- subdirectory containing template files (the installer can auto prefix them to prevent collision)

modules/   <--- subdirectory containing modules to be installed (the installer can check if already installed and skip)

source/   <--- subdirectory containing python code (installer will move this to the plugin directory with the plugin name)

weather_adj.py  <--- main plugin code

package.json   <---- holds info represented below

That would be the basic layout and the package.json would have the info for OSPi to use like this:

{

"name": "Weather Adjust",

"version": "1.0.0",

"description": "Allows weather based rain delay activation.",

"author": "Samer Albahra"

"modules": "apscheduler"

}

The modules can be just a name and the installer would grab them or you can add a folder and manually install them as suggested above. I think in the long run this system will be easier to find and use plugins.

Update: I already see ways to clean that up so of course this isn’t a final implementation by anyways but an example to represent what I had in mind.

[Samer]

First, welcome to OpenSprinkler.

Second, which OpenSprinkler product to you own? The Arduino or the Raspberry Pi based OSPi? Also, which software are you using?

It sounds like you are using OSPi and need the latest version. Please let me know.

[Samer]

Ah, if you are interested in the rain delay feature than you are correct for the Arduino that is currently the only way to achieve that. Glad it works!

[Samer]

Hello, the PHP version of the app is no longer in development. So before you spend too much effort trying to get it working I suggest you hold off as another solution is coming soon.

If you want the PHP copy to run you will need to add JSON support to your PHP install. That is the error you are getting.

Note: If you are using OSPi, the PHP app does not support the 2.x versions.

Thanks

[Samer]

KanyonKris,

I think the filename makes 100% sense! In regard to the Github approach, the XML file will define which files go where (and they can have generic layout such as subdir in main plugin folder: templates, plugin, etc) and the installer can move them when installed (from the menu).

[Samer]

I wouldn’t rule out version control (Github) yet. I think using a Github repository with a folder for each plugin is ideal for development. Also, Github has an API and has methods to grab raw files. I think you can place an XML document in the root of each plugin folder that has info on the plugin and the OSPi will just connect to repo and get folder list (aka plugin list) thats available. The user sees this picks the ones they want and OSPi just copies that portion of the repo into the plugins dir and does chmod a+x to the directory and reboot OSPi. This allows easy plugin install and easy development and management. No one has to worry about making packages, uploading them etc.

Ultimately, you will merge each request to the repo. Me, you and Ray can use an organization repo to manage the plugins (making the pull request process easier). Each developer would then submit their plugin via a pull request to a new directory in the main repo.

[Samer]

Based on what I am seeing in the debug session (assuming it is in fact you) appears to be an incorrect password. Manual mode, once enabled, does not require a password to toggle on/off which is why that works fine. However, turning on/off manual mode itself requires a password and when you tried to toggle it off it failed (401). This is directly from the OpenSprinkler. So please check the password in the app under Manage Sites. Hopefully, this will fix the issue.

[Samer]

Ignore the version number when using the PhoneGap link. You can clearly see it is not the same build by going to the manual mode page and toggling a station. I have updated the visual and backend methods so it should stand out as different.

[Samer]

Can you please try the new beta? I made the changes below but I also added a debugger which lets me have some information about the app’s status. For this to work though we both have to be on at the same time therefore let me know when would be a good time. All you have to do is install the newest beta (same link).

I added a yellow status indicator when toggling stations. During this phase, it has sent the request but awaiting confirmation. Also, it uses the status from the device instead of the background color to determine what a station is currently doing (clearing up some confusion). If this isn’t working then something different is causing issues, possibly a caching issue. I hope to resolve it by using the above strategy.

By the way, please note the app expects all control to be done through one device at a time. If you are changing things on the PC, the app continues assuming the previous state. With that said, information is updated periodically and during page changes (applicable info only).

Update: By the way, I did a diff on 1.1.5…1.1.6 and nothing was changed in the manual mode behaviour or error checking. So not sure if that’s when the problem was introduced.

[Samer]

The only way for the password message error to show up is if the device returns a 401 (unauthorized). Unfortunately, the firmware also returns a 401 when manual mode is disabled and a station is toggled.

It sounds like the controller isn’t in manual mode but the app thinks it is. During this state, you will get password errors. Is that what’s happening? I guess I need more information as to the state of the device because this is not a normal behavior and I’m not able to recreate it.

Thanks

[Samer]

Awesome, no problem!

[Samer]

Have you updated to the latest version of OSPi? If so, try deleting: data/weather_adj.json

[Samer]

For iOS you can private message me your UUID and I will add you to my list of approved devices. Then, you can use the Phonegap link to test/update as necessary.

Thanks!

[Samer]

@TechFan wrote:

Got up to date. Nice to be able to export. Any way to export all logs instead of just one week worth?

Sure, just select a wider range. It is exporting the range it’s requesting. For OpenSprinkler on Arduino the limit is in the firmware for one week (otherwise will return 404).

@TechFan wrote:

Btw, missing the red highlighted schedules that help make it clear they are disabled.

Where is this not working exactly?

[Samer]

Can you please post the error message from the Python program? Run it manually so you can see the program output: python ospi.py

[Samer]

It doesn’t export to a file instead it saves it in localstorage. This is because not all devices allow file manipulation.

[Samer]

I believe I have fixed the issue however before I do any releasing I would like to ask if you’re interested in beta testing it for me. I have an APK I can send you and to install you just need to enabled 3rd party developers in the settings.

Thanks!

Update: Here is the link for the betas https://build.phonegap.com/apps/793070. By the way, iOS and Windows won’t work since they require exceptions in signatures.

[Samer]

This is an app only issue and unrelated to the hardware itself. The feedback is a misinterpretation of the error codes something that varies with browser implementation. I have put a tighter restriction on displaying vague password error’s and now working on analyzing the output of manual mode changes in regard to the mobile app.

Thanks

[Samer]

Thank you for the detail, I will be fixing this in the upcoming version and realize it is a problem for multiple users. Another user just posted a similiar problem.

The reason it won’t let you turn it off is it “sees” it as already off (since the AJAX request “failed”) which I still need to look into. I get it didn’t fail but the OS might have sent a redirect instead of a 200 and that got interpreted as an error. Again, I will look into it and get it fixed soon.

[Samer]

The entire web interface your referring to has been “discontinued” and is about 600 commits behind now. Furthermore, OSPi had a major, deviating, change which caused the old PHP based app to stop working with it. I honestly don’t plan on updating the PHP app because in the long term the install process is lengthy, requires additional hardware if using Arduino, and honestly no need for bulky PHP.

In order to help users I am working on supporting as much desktop platforms as possible. Furthermore, I export OSPi logs and worked with Ray to introduce logging on Arduino removing that feature from the mobile app. I also wrote a weather adjust plugin for OSPi that allows weather based rain delay as was in my PHP app.

Overall, this should be a better solution. This will also allow easy and mostly automatic updates. It’s as easy as one tap on most platforms to install and supports multiple devices with easy switching.

For the security concious I added support for HTTPS proxy with Basic AUTH. For OSPi users, a guide is available on the Wiki and hopefully this process can be streamlined in the future.

Hopefully by using the native apps you will be up and running again.

[Samer]

Okay so this is starting to make more sense. The web app (the PHP files hosted on the Raspberry Pi) is no longer developed. Most likely anything you do interacting with the browser will not work correctly, especially if you update the firmware.

The Samsung Note 3 is in fact showing the correct app version so that makes sense. If you use the app on the Samsung device to “export configuration” and then update your firmware you can import to restore everything except program 9-17. I still haven’t gotten this data from you so I can’t help reconstruct it however knowing what will go away might help you know what to write down to return after the upgrade.

[Samer]

Yes and furthermore based on your export you posted you will likely not be able to use the mobile app to import your data. I can fix the old JSON for you however I don’t have all of the information to reconstruct all your programs. If you want goto /vp and push view source. Give me the source code (specifically the info.) and I will help you rebuild it. Also get the source for the homepage if you don’t mind. We can do this over private message if you prefer, let me know.

In the future, the mobile app will export and import your backup which includes everything on the device. But please ensure you are using the latest version of the Sprinklers application.

[Samer]

Oh, I see now. Sorry I assumed hardware revision 2.0. Firmware prior to 2.0.4 used a regex to grab information. I will have to flash back to an older firmware and test out support. However, instead, could you just update to 2.0.7 (the latest firmware)?

Update: A closer look at your export suggests you are not running Sprinklers 1.1.6. In fact, I believe you might be running 1.0.6 or older. Also, are you sure you are not using the web app? That export method is old and has been changed a while back.

[Author]

Posts