You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When someone cancels a reservation on reservecalifornia, the site does not become immediately available and instead becomes locked. I believe sites unlock at 8am the following day as this is all i have observed, but it may be possible there are other times that they unlock. Regardless, Camply does not account for this and will instead show sites as unavailable instead of becoming available at 8am. The unlock time is included in the json returned by the API and Camply could account for this to let users know sites will become available at the unlock time.
Expected behavior
Camply should identify site 33 (see json) as becoming available at 8am on 3/15/2024.
Console Output (with --debug)
[2024-03-14 16:33:37] CAMPLY camply, the campsite finder ⛺️
[2024-03-14 16:33:37] DEBUG Setting up camply debugging
[2024-03-14 16:33:37] DEBUG Camply Version: 0.32.2
[2024-03-14 16:33:37] DEBUG Python Version: 3.12.2
[2024-03-14 16:33:37] DEBUG Platform: darwin
[2024-03-14 16:33:37] INFO Using Camply Provider: "ReserveCalifornia"
[2024-03-14 16:33:37] INFO 2 booking nights selected for search, ranging from 2024-09-06 to 2024-09-07
[2024-03-14 16:33:37] INFO Searching for availabilities with 2 consecutive night stays.
[2024-03-14 16:33:38] INFO Searching across 1 campgrounds
[2024-03-14 16:33:38] INFO ⛰ Crystal Cove SP Beach Cottages (#634) - � Beach Cottages (#757)
[2024-03-14 16:33:38] INFO Searching Beach Cottages, Crystal Cove SP Beach Cottages (757) for availability: September, 2024
[2024-03-14 16:33:38] DEBUG Starting new HTTPS connection (1): calirdr.usedirect.com:443
[2024-03-14 16:33:38] DEBUG https://calirdr.usedirect.com:443 "POST /rdr/rdr/search/grid HTTP/1.1" 200 None
[2024-03-14 16:33:38] INFO ❌ 0 total sites found in month of September
[2024-03-14 16:33:38] INFO ❌ ❌ ❌ ❌ 0 Reservable Campsites Matching Search Preferences
[2024-03-14 16:33:38] CAMPLY Exiting camply �
Using curl I was able to send a similar POST request as Camply and view the JSON output from the API. Below is a snippet showing the site and the lock parameter for when a site will become available. On 9/6 and 9/7 the site shows that it is not free, but the lock parameter has a date/time identifying when it will become reservable. On 9/8 the lock parameter is null which indicates that it is reserved. Full json output attached.
Describe the bug
When someone cancels a reservation on reservecalifornia, the site does not become immediately available and instead becomes locked. I believe sites unlock at 8am the following day as this is all i have observed, but it may be possible there are other times that they unlock. Regardless, Camply does not account for this and will instead show sites as unavailable instead of becoming available at 8am. The unlock time is included in the json returned by the API and Camply could account for this to let users know sites will become available at the unlock time.
Original Camply Command (with
--debug
)camply campsites --campground 757 --start-date 2024-09-06 --end-date 2024-09-08 --nights 2 --provider reservecalifornia --debug
Expected behavior
Camply should identify site 33 (see json) as becoming available at 8am on 3/15/2024.
Console Output (with
--debug
)Using curl I was able to send a similar POST request as Camply and view the JSON output from the API. Below is a snippet showing the site and the lock parameter for when a site will become available. On 9/6 and 9/7 the site shows that it is not free, but the lock parameter has a date/time identifying when it will become reservable. On 9/8 the lock parameter is null which indicates that it is reserved. Full json output attached.
** curl**
curl -d '{"FacilityID":"757", "StartDate":"09-06-2024", "EndDate":"09-08-2024"}' -H "Content-Type: application/json" -X POST https://calirdr.usedirect.com/rdr/rdr/search/grid
json output snippet showing site 33 as locked
Full json: output.json
The text was updated successfully, but these errors were encountered: