Skip to content

Rachio Binding development branch 26 – Thing type migration support

Pre-release
Pre-release

Choose a tag to compare

@kovacsi2899 kovacsi2899 released this 22 May 21:01
· 7 commits to rachio-on-oh5.1 since this release

Rachio Binding – Development Branch 26

This release adds openHAB Thing type migration support for the Rachio binding after the recent channel type / QuantityType updates.

Added

  • Added OH-INF/update/update.xml with Thing type migration instructions.
  • Added thingTypeVersion=1 to the updated Thing type XML definitions.
  • Added migration support for the affected Rachio Thing types:
    • device
    • zone
    • schedule
    • flexschedule
    • valve
    • valveprogram

Changed

  • Updated the README upgrade documentation.
  • Clarified that existing UI-managed Things should be migrated automatically by openHAB.
  • Documented that existing Items may still need manual adjustment when channel types changed from plain Number to Quantity-aware types such as:
    • Number:Time
    • Number:Length
    • Number:Dimensionless
    • and other matching QuantityType-based Item types.

Tested

Smoke tested on openHAB 5.1.1 with an existing Rachio Generation 3 irrigation controller.

Verified:

  • Bridge startup
  • Cloud connection
  • Automatic discovery
  • Existing controller Thing initialization
  • Existing zone Thing initialization
  • Schedule Thing initialization
  • Flex schedule Thing initialization
  • Webhook registration
  • Current schedule refresh
  • Forecast refresh
  • Recent event history refresh
  • Multi-zone start using the controller runZones / runTime / run channels
  • Controller stop command
  • Single-zone start and stop commands

No runtime ERROR, WARN, Exception, COMMUNICATION_ERROR, or API throttling issue was observed during the smoke test.

Notes

This release focuses on openHAB migration compatibility for already existing managed Things. It does not introduce new Rachio API functionality.

Users upgrading from earlier development builds should verify their existing Items and adjust Item types manually where required, because openHAB migrates managed Thing/channel definitions but does not automatically rewrite user-created Item definitions.