Meeting rooms not available in Nextcloud calendar

[Conoship]

Steps to reproduce

1. Create event in Nextcloud Calendar web interface
2. Add attendee and open more details
3. Not all configured meeting rooms are shown as "Suggested" but are visible in "Show rooms" even though they are available at the selected times
4. After deleting one off the rooms that are not shown and recreating it under a different name the new room appears but another one disappears

Expected behaviour

All meeting rooms should be shown under suggested when available at the selected times

Actual behaviour

Not all configured meeting rooms are shown as "Suggested" but are visible in "Show rooms" even though they are available at the selected times

Server configuration

Web server: Apache

Database: PostgreSQL

PHP version: 8.5/8.4/8.3

Nextcloud version: (see Nextcloud admin page)
34.0.4

List of activated apps

Enabled: - activity: 7.0.0 - admin_audit: 1.24.0 - announcementcenter: 7.5.0 - app_api: 34.0.0 - approval: 3.3.1 - appstore: 1.0.0 - assistant: 3.5.0 - attendance: 1.52.0 - bruteforcesettings: 7.0.0 - calendar: 6.5.4 - calendar_resource_management: 0.12.2 - call_summary_bot: 3.5.0 - circles: 34.0.0 - cloud_federation_api: 1.18.0 - collectives: 4.6.1 - comments: 1.24.0 - contacts: 8.8.1 - contactsinteraction: 1.15.0 - context_chat: 5.4.0 - dashboard: 7.14.0 - dav: 1.40.0 - deck: 1.18.4 - doom_nextcloud: 2.0.0 - federatedfilesharing: 1.24.0 - federation: 1.24.0 - files: 2.6.0 - files_3dmodelviewer: 0.0.18 - files_accesscontrol: 5.0.0 - files_antivirus: 6.4.1 - files_automatedtagging: 5.0.0 - files_confidential: 5.1.0 - files_downloadlimit: 5.2.0 - files_lock: 34.0.1 - files_pdfviewer: 7.0.0 - files_reminders: 1.7.0 - files_retention: 5.0.0 - files_sharing: 1.26.0 - files_trashbin: 1.24.0 - files_versions: 1.27.0 - firstrunwizard: 7.0.0-dev.0 - forms: 5.3.6 - groupfolders: 22.0.6 - integration_windmill: 1.1.0 - intravox: 2.7.1 - logreader: 7.0.0 - lookup_server_connector: 1.22.0 - mail: 5.11.5 - nextcloud_announcements: 6.0.0 - notes: 6.0.2 - notifications: 7.0.0-dev.1 - notify_push: 1.4.0 - oauth2: 1.22.0 - office: 1.0.0 - password_policy: 6.0.0-dev.0 - photos: 7.0.0 - previewgenerator: 5.14.0 - privacy: 6.0.0-dev.1 - profile: 1.3.0 - provisioning_api: 1.24.0 - quota_warning: 1.24.0 - recommendations: 7.0.0 - related_resources: 5.0.0-dev.0 - richdocuments: 11.1.1 - richdocumentscode: 26.4.303 - roomvox: 1.5.0 - serverinfo: 6.0.0 - settings: 1.17.0 - sharebymail: 1.24.0 - side_menu: 6.0.1 - spreed: 24.0.5 - support: 6.0.0 - survey_client: 6.0.0-dev.0 - systemtags: 1.24.0 - tables: 2.3.0 - tasks: 0.18.1 - text: 8.0.0 - theming: 2.9.0 - twofactor_backupcodes: 1.23.0 - twofactor_nextcloud_notification: 8.0.0 - twofactor_totp: 16.0.0 - updatenotification: 1.24.0 - user_ldap: 1.25.0 - user_saml: 8.3.1 - user_status: 1.14.0 - viewer: 7.0.0-dev.0 - weather_status: 1.14.0 - webhook_listeners: 1.6.0 - whiteboard: 1.5.9 - workflowengine: 2.16.0 Disabled: - encryption: 2.22.0 - eurooffice: 11.0.4 (installed 11.0.4) - files_external: 1.26.0 - ncc_backend_4mc: 1.3.0 (installed 1.3.0) - sip_trip_phone: 1.2.0 (installed 1.2.0) - suspicious_login: 12.0.0-dev.0 (installed 11.0.0) - testing: 1.23.0

Nextcloud configuration

{ "system": { "instanceid": "***REMOVED SENSITIVE VALUE***", "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "192.168.10.32", "nc2.conoship.com", "nc.conoship.com" ], "datadirectory": "***REMOVED SENSITIVE VALUE***", "skeletondirectory": "\/var\/www\/nextcloud\/core\/skeleton-conoship", "dbtype": "pgsql", "version": "34.0.4.1", "overwrite.cli.url": "https:\/\/nc2.conoship.com\/", "overwritehost": "nc2.conoship.com", "overwriteprotocol": "https", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbtableprefix": "oc_", "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "installed": true, "maintenance": false, "force_language": "en", "default_locale": "nl_NL", "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory", "memcache.local": "\\OC\\Memcache\\APCu", "memcache.locking": "\\OC\\Memcache\\Redis", "memcache.distributed": "\\OC\\Memcache\\Redis", "filelocking.enabled": true, "htaccess.RewriteBase": "\/", "redis": { "host": "***REMOVED SENSITIVE VALUE***", "port": 0, "timeout": 0 }, "enable_previews": true, "preview_max_x": 2048, "preview_max_y": 2048, "preview_max_memory": 512, "enabledPreviewProviders": [ "OC\\Preview\\PNG", "OC\\Preview\\JPEG", "OC\\Preview\\GIF", "OC\\Preview\\BMP", "OC\\Preview\\XBitmap", "OC\\Preview\\MP3", "OC\\Preview\\TXT", "OC\\Preview\\MarkDown", "OC\\Preview\\PDF", "OC\\Preview\\Movie", "OC\\Preview\\MSOffice2003", "OC\\Preview\\MSOffice2007", "OC\\Preview\\MSOfficeDoc", "OC\\Preview\\OpenDocument" ], "loglevel": 0, "mail_smtppassword": "***REMOVED SENSITIVE VALUE***", "mail_smtpname": "***REMOVED SENSITIVE VALUE***", "mail_domain": "***REMOVED SENSITIVE VALUE***", "mail_from_address": "***REMOVED SENSITIVE VALUE***", "mail_smtpmode": "smtp", "mail_smtpsecure": "ssl", "mail_smtphost": "***REMOVED SENSITIVE VALUE***", "mail_smtpauth": true, "mail_smtpport": "465", "mail_sendmailmode": "smtp", "mail_smtpstreamoptions": { "ssl": { "allow_self_signed": true, "verify_peer": false, "verify_peer_name": false } }, "app_install_overwrite": [], "theme": "", "maintenance_window_start": 1, "trusted_proxies": "***REMOVED SENSITIVE VALUE***", "updater.secret": "***REMOVED SENSITIVE VALUE***" } }

Browser

Browser name: Firefox/

Browser version: 155

Operating system: Windows

Browser log

Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...

[Rikdekker]

Thanks for the detailed report — the "delete and recreate and another one disappears" observation is what made this traceable, so that detail was worth a lot.

I've traced it, and the cause is not in RoomVox. There are two separate bugs upstream in Nextcloud, and together they produce exactly what you describe. I've reported both:

• nextcloud/calendar#8949 — the suggestions list is hard-capped at three, and unsorted
• nextcloud/server#64413 — the capacity filter compares as text, not as a number

What is happening

The suggestion list only ever shows three rooms. In ResourceList.vue:

// Take the first three available options
this.suggestedRooms = results.filter((room) => room.isAvailable).slice(0, 3)

Nothing is sorted, so the three you get are whichever rows the search returned first. That is why deleting and recreating a room shuffles the picture: the new room gets a different row position and pushes another one out of the top three. Show rooms uses a different code path with no cap, which is why everything is visible there.

On top of that, the capacity filter drops rooms that fit. The suggestions search passes the attendee count as a minimum capacity, and the server compares that against a varchar column — so it is a string comparison. With capacities like 4, 6, 8, 10, 12, 16, 20, 100 and a 2-attendee meeting:

Attendees	Rooms passing the filter
2	4, 6, 8, 20, 25, 30
3	4, 6, 8, 30
4	4, 6, 8

The rooms seating 10, 12, 16 and 100 are dropped because "10" < "2" as text. A room for a hundred people disappears from a two-person meeting, while the four-seat room stays.

One question, to tell the two apart

Could you tell me the seating capacities of the rooms that don't show up, and roughly how many attendees you had on the event?

• If the missing rooms have capacities with a different digit count than the ones that do show (say 10+ versus single digits), both bugs are in play.
• If all your rooms have similar capacities, the hard cap of three explains it on its own.

Either way nothing is wrong with your configuration.

Until upstream fixes it

There is no version to upgrade to — I checked 6.5.4 (what you run), 6.6.0-rc.2 and main; the cap is in all three, unchanged since 2021, and the capacity comparison is the same on server master.

Two things that help meanwhile:

• Use "Show rooms" rather than the suggestions. That path applies neither the cap nor the capacity filter, so it shows every room you have access to, with availability.
• If the capacity bug is the one biting you, padding capacities to equal length (004, 010, 100) makes the string comparison accidentally correct. It does leak into the interface as leading zeros, so I'd only reach for it if the suggestions are important to your workflow.

I'll keep this issue open to track the upstream reports, and update here when either moves.

[Rikdekker]

Update — I tested this against Calendar 6.6.0-rc.2, and there is better news than my previous comment suggested.

Calendar 6.6.0 ships a new room picker, and its capacity filter is correct. Behind Show rooms you now get a proper dialog: search by name, filter by floor, minimum capacity and features, with a count like "113 of 113 rooms available". That filter compares capacity as a number, client-side, so neither of the two bugs affects it — no cap at three, and no rooms dropped by the string comparison.

The "Suggested" list is unchanged. Both code paths live in the same component, so the suggestions still run their own search with the attendee count as a capacity filter and still cut off at three. Verified in the built bundle on a running 6.6.0-rc.2 instance, not just in the source.

So for your situation:

• Upgrading to 6.6.0 (once it leaves rc) gives you a Show rooms dialog that actually does what you want — filter on capacity, see every matching room.
• The Suggested row keeps showing at most three, with the same capacity bug.

My earlier advice to use "Show rooms" as a workaround still holds, and gets noticeably better in 6.6.0.

I've noted this on both upstream issues. It changes the ask on the Calendar side: the correct filtering logic now already exists in the codebase, so applying it to the suggestion list is a much smaller change than building something new.

The question from my previous comment still stands, if you have a moment — the capacities of the rooms that don't appear, and the attendee count. That tells us whether the capacity bug is biting you or just the cap of three.

[Rikdekker]

Here is what the new picker looks like, so you can see what to expect from 6.6.0 — this is the Show rooms dialog on a 6.6.0-rc.2 instance:

Note what it does with Minimum capacity: 4 — it returns rooms seating 4, 6, 7, 8, 12, 16, 20 and 50, and reports "12 of 12 rooms available". The multi-digit capacities are exactly the ones the broken server-side filter drops from the suggestions, and there is no cap at three: every matching room is listed, grouped by building, with search and filters on floor and features.

(Room and building names are painted over; the capacities are the original values, since those are the part that matters here.)

[Conoship]

Great work, thank you.
We are at 6.5.4 and hope 6.6.0 is available soon.
We had sort of a hunch that the capacity could be of influence so we set the capacity to 20 for all rooms. That did not change anything.
We tried with two and three attendees > three room suggestions are visible. With four or more attendees all suggestions are gone.