Forum Replies Created
-
AuthorPosts
-
sirkus7Participantxhirschx — I have a couple of things that may help if you’re still wanting an LCD display of the status of your OpenSprinkler system.
If you’d like to run ospiLCD.py, I updated the code to work with the recent OpenSprinkler firmware. You can find my update in the repository branch here: https://github.com/sirkus7/ospiLCD/tree/api-update-2.1.9
Or you can get the updated python file directly here: https://raw.githubusercontent.com/sirkus7/ospiLCD/api-update-2.1.9/ospiLCD.pyAnother option you may be interested in… I created another version of the project with a number of changes to work for what I was looking for and adapt to the new API. At it’s core, it does the same thing, it displays the status on an LCD display (remotely or on the OSPi). However, this one leverages OpenSprinkler’s MQTT notification to update the status immediately on change, rather than polling every minute. And, since the new UI doesn’t seem to support a LCD backlight setting, the script has a configurable auto-backlight setting to turn on and turn off the backlight when a status change happens. That’s a few of the differences, but if you’re interested you can check out the script and the tutorial for setup here:
https://github.com/sirkus7/ospiLCD-mqttCheers
sirkus7ParticipantHi kdcisit — Regarding your second question, the default setup for the web UI loads assets (such as javascript files) from a cloud server at ui.opensprinkler.com. You can move those to your local OSPI and serve them up from your nginx server, which would solve your mixed-source SSL/TLS warning.
For info about how to do this, check out https://openthings.freshdesk.com/support/solutions/articles/5000164006-using-a-different-server-for-ui-assets
Hope that helps. Cheers
-
AuthorPosts