A vacant unit should draw almost nothing and open for almost no one. When its meter keeps turning or its door keeps opening, someone is living there, a fixture is leaking, or a key still works. Vacant Unit Watch takes the list of vacant units and their move dates from your property system, reads each unit's submeter over Modbus TCP, and reads door events from your access control platform.
When a vacant unit's use rises above the idle level you set, or its door opens outside a scheduled turn or showing, it proposes an inspection work order with the readings and events attached. If use continues after an inspection finds no cause, it proposes a shutoff work order. A person approves each one.
This is a reference listing. It documents what Fibric would read from Vacant Unit Watch and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
Which units are vacant and since when: IsUnitOccupied on Buildium rental units, availableUnitsOnly on Entrata getPropertyUnits, occupancies in AppFolio
Move-outs and coming move-ins: Buildium lease move outs, Entrata leases placed on notice with move-out and unit-available dates
Electricity or water use per unit from submeters read over Modbus TCP: kWh and kW registers on the polling schedule you set
Door events on the unit: ButterflyMX access logs with logged_at, entry_method, and unit; Brivo access events by site and access point; Salto KS lock entries
Credentials that still open a vacant unit's door: Brivo users and credentials, Salto KS keys and access groups, ButterflyMX PINs and access tools
Open work orders on the unit, such as a turn or a showing, from Buildium, Entrata getWorkOrders, or AppFolio, so expected activity is not raised
Proposed actions
Target capability: propose an inspection work order in Buildium, Entrata, or AppFolio for a vacant unit whose meter passed the idle level, readings attached
Target capability: propose a utility shutoff work order when use continues after an inspection found no cause, for a person to schedule and carry out
Target capability: propose suspending a credential or key that opened a vacant unit's door, through Brivo PUT /users/{userId}/suspended or a Salto KS key block
Target capability: propose a note on the unit recording the activity seen, the work order raised, and the outcome
Target capability: propose adding a unit to the watch list on move-out and removing it on move-in, from the lease dates in your property system
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Find the unit that was never vacated
Buildium shows the unit vacant since the move-out date. The Modbus TCP submeter still advances every evening. The operator proposes an inspection work order in Buildium with the nightly readings beside the vacant-since date.
Entrata lists the unit as available. ButterflyMX access logs show a swipe to open on that unit under a former resident's name. The operator proposes suspending the access tool and a note on the unit.
The inspection found no fixture running, yet the water submeter keeps counting. The operator proposes a shutoff work order in MaintainX with both sets of readings, for a person to schedule.
As Entrata leases go on notice and new leases start, the operator proposes adding and removing units, and the Brivo access points that serve them, so no vacant door goes unwatched.
A property management connector that reports unit occupancy and move dates: Buildium, Entrata, or AppFolio Property Manager
Unit submeters reachable over Modbus TCP, with a register map tying each meter to its unit and the idle level you accept
An access control connector with events per door or unit: Brivo Access, Salto KS, ButterflyMX, or your access control platform
A destination for work orders: the property system's own work orders, or a CMMS such as MaintainX
Authentication
The operator carries no credentials. Unit status, meter registers, and door events arrive through the property, Modbus TCP, and access control connectors you attach, and work orders and credential changes go out through those same connectors after approval.
Limits
Units without a submeter or a connected door show nothing. Coverage is exactly the meters and doors you map.
It does not switch off power or water. A shutoff is a work order a person schedules and carries out.
A unit being turned, shown, or cleaned looks active. The alert is held back only where the property system records that work.
Modbus TCP carries no authentication, so meter reads depend on network reach from the site to each meter or gateway.
Access and pricing
Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
Each work order and each credential change. The proposal names the unit, its vacant-since date, the meter readings or door events that raised it, and the work order text or the credential to suspend. Approve, change the assignee or wording, or dismiss.
What record does a watch leave?
A receipt per proposal with the readings and door events, the work order number created, who approved it, and the way to reinstate a suspended credential. Dismissals are kept with a reason, so the same unit and window are not raised twice.
Does it ever shut anything off itself?
No. It reads meters and door events and proposes. Power and water are shut off only by a person acting on an approved work order, and a credential is suspended only after approval, through the access control connector.
Ask about Vacant Unit Watch
Ask about the capabilities and requirements in this listing.
This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy