Forum Replies Created
-
Posts
-
Glad that worked! This might be the same thing here btw: https://github.com/Dan-in-CA/OSPi/tree/firmware_based
Could you please give some more information? What app are you using and on what device? What exactly is the error? Which OpenSprinkler are you using? Which firmware?
Thanks
I have started coding this and basing it on the rain based delay in my older PHP webapp. I should have a working plugin soon and it will be compatible with my native app once completed.
No he does merges in a different way that doesn’t allow this. This happened with every OSPi release before but I constantly updated. In OSPi 2, I added a plugin to get JSON data instead of parsing html. It works a lot better but porting that code to PHP takes time.
Oh sorry that’s the one feature loss however I plan on incorporating this as a separate OSPi plugin down the road that will work with the mobile app. The only hold up is time but I should have more available soon.
Thanks
Update: Honestly it was a mistake to add features that require 24/7 monitoring into a mobile app. Since the native app lost it, it’s been the most requested missing feature next to logging. I finally added the logging thanks to Ray and Dan’s support. The automatic rain delay can come to OSPi with ease as a plugin.
That’s correct. All the assets are bundled within the app. Furthermore, the native app can automatically detect an OpenSprinkler on your local network so no IP is needed (guided on first launch). The only thing you lose is the desktop interface with the native app.
The web app is no longer being actively developed. The native apps are the only thing being worked on moving forward. This is because the web app has only one advantage, it works on desktop. However, OSPi recently got a new UI for desktop and the native apps offer everything else. As a result, I see no reason to develop both versions.
Your welcome to add 2.0 support to the web app and I will merge the pull request, if you want.
If there are any other reasons your using the web app please let me know.
Thanks!
You know what I was wrong I am sorry. I am so used to using my app to import each time I forgot they clear out.
With that said, the app works well at backing up and importing all settings back in.
Sorry for the misinformation.
Yes, furthermore, the settings should remain through upgrades. At least they do for me (I upgrade manually using avrdude).
You could use a basic wireless thermometer to monitor the air temp of the enclosure.
For the CPU temp I am not sure nor am I sure it is important.
The interval duration needs to be greater than 0 for the program to run. Please ensure this is in fact the case and let me know.
Thanks
It’s most likely your SSL certificate. Being invalid is causing an error and preventing the connection. You can get by for free by using a startssl.com certificate.
Most of the HTTP commands are documented here: http://rayshobby.net/wordpress/wp-content/uploads/2011/10/Firmware1.8HTTPGETcommands.pdf
This document was written for firmware 1.8.3 so anything new since then isn’t documented (not too many things really).
Ray, I think the avahi daemon will add support for auto discovery of the web service (and port) and not just the hostname/domain. I think this could be a useful addition as well.
The symptoms you describe are likely a password issue. Check/fix the password on the Manage Sites page.
Let me know if that helps.
I found this bug and just pushed a fix. I apologize it took so long to get to this one.
Should see the update within the week on the various app stores.
Thanks!
The preview display is rendered using a third party library. I will check if any improvements have been made regarding Windows Phone. However, I am not sure there is much I can do except using a different rendering method.
If the password is the issue, the home screen would load and the password error would show when any changes were attempted.
The issue is a networking issue. As the previous user realized, the ISP can block port 80 so try another port such as 8080. You can use port triggering for this so the inside port remains 80 and only the outside port becomes 8080 (if you want).
Thank you for the post!
I am pushing a fix for the station name length right now, thanks!
The logging feature is new in the native app and still being massaged in however the point you bring up is a good one and I will be adding this in the settings soon. I think only OSPi supports turning this feature on/off. I will check with Ray to see if the Arduino version will have that feature.
There are no known issues. It’s likely a network issue however if you can provide specifics I can help troubleshoot.
Some ISP’s may block port 80/443 and other ports such as 445. Check another port and see if it works.
Yes port forwarding works well with the mobile app.
When using port 80 you don’t need to define it. See if that helps (just the IP).
Are you sure your port forwarding port 80 to the correct device?
@fsped09 wrote:
So I recently got my OSPi up and running. But the app that I downloaded from Google Play doesn’t look like the screenshots I see on this post, ie I don’t see the weather on the main screen. Did I not install something correctly? Sorry if this has already been answered, bit of a noob here. Any help would be appreciated, thanks!
The issue here is you need to have a location specified in the device options. Let me know if you have done this and still not seeing the weather on the homepage.
Thanks!
Jonas, I agree the automatic rain delay is a nice feature however the mobile app performing this feature never made sense to me. I think this is a feature that should be included into the firmware. I know OSPi supports plugins now and am sure the automatic rain delay code I used in my PHP web app can be adapted to a Python plugin for OSPi.
If anyone is interested I can probably do this however I can’t give any projected completion dates.
