No PR, See also: ThinkerForge Forum/(#85). Issue #4949, Forum topic 111487, Branch: plex
No PR, but this branch seems to contain work on this binding Add-ons to Migrate Add-onĭepends on cul transport. If you have or use an openHAB 3 binding but it doesn’t have the same features as the openHAB 1 version please also report.
If something is missing or changed please comment or update this list. This information is compiled to have an overview of the differences and compatibility of different openHAB add-on versions. The column Feature Compatible in the last table mentions if the openHAB 3 bindings lacks some features that where part of the openHAB 1 binding. This can give an indication on the complexity of the binding.
The column Java LOC is the number of Lines of Code of the add-on. Some add-ons have no poll results because those have an openHAB 2 variant and were not in the poll. The poll results are from the (closed) poll from the openHAB forum: poll-which-oh1-x-addons-do-you-use. If not supported it still might work, but it needs to be installed manually. This means it’s included in the feature file and known to work with openHAB 2 and show up in PaperUI when legacy mode is activated. The column supported in the table means if the add-on was officially supported in openHAB 2.
In the lists the persistence add-ons are not included because separate work has been done: PR #5275. When an openHAB 1 binding from the first 2 tables has been migrated it’s moved to third table. The third table is with openHAB 1 add-ons that have a known openHAB 3 replacement. These bindings have potential very few users and therefor the chance someone will migrate it to openHAB 3 is very low. The second table is with unsupported openHAB 1 bindings that have not be voted on. The table contains the links to the work-in-progress if known. The first table contains the openHAB 1 add-ons with no (official) openHAB 3 version, but have been voted on in the poll or are being worked on. Use the comments to report new or changed entries to the list. If you want to know if a binding will be available in openHAB 3 and it’s not mentioned on the list ask on the openHAB forum. It just gives an overview of the status of migrations or known other new versions bindings. If (duration > 300 ) and (rundate > maxdate):ĭiff = datetime.today() - datetime.This issue contains an overview of all openHAB 1 add-ons and how/if there is an openHAB 3 version.ĭisclaimer: This list is not a planning or to do list. #iterate through all the entries finding the oldest one that was more than 5 minutesįor e in range (0, len(logs)):ĭuration = logs Url = ' + startDate + '&edate=' + endDate StartDate = (datetime.today() - timedelta(days=5)).strftime('%s') ĮndDate = datetime.today().strftime('%s') Rsprinklers: curl #getsprinklerLastRun.py Same options as logs, but returns logs with text descriptorsĬommand: python3 ~/.homeassistant/scripts/getSprinklerLastRun.pyĮntity_id: input_n_sprinklers_now “json/tlogs” JSONtLogs(key_value_pairs, pFile) (params : sdate(start_date), edate(end_date), g(grouping)) G : grooupin values h, d, or m (hourly, daily, monthly)
Sdate : unix epoch representing the start date of the reportĮdate : unix epoch representing the end date of the report
“json/wcheck” returns weather underground data. “json/state” returns system state values “json/settings” returns web port, and weather underground settings. “json/zones” shows for each zone: name, enabled, pump, state “json/schedules” shows basic information on all schedules “json/schedule” shows the details of a schedule
(turning on a manual zone, turns automation off) Options : sched : 0 through x will run a current schedule as a quick schedule. “bin/setQSched” Initiates a quick schedule I have documented the rest of the api’s (except the add and delete stuff) here it is: So I´ve started with this package in HASS: switch:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" valve2:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" valve3:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" valve4:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" valve5:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" valve6:Ĭommand_on: "/usr/bin/curl \" command_off: "/usr/bin/curl \" input_slider: It is possible to manually open/close the valves using the following url: It is also faster to get up and running compared to building your own solution.īut of course, you want to integrate this with HASS I chose this over opensprinkler since this setup only required a cheap relay board.