class PlaceOS::Driver::Interface::Lockers::PlaceLocker
Overview
inherit this to extend with additional locker information
Included Modules
- JSON::Serializable
Extended Modules
- JSON::Schema
Defined in:
placeos-driver/interface/lockers.crConstructors
Instance Method Summary
-
#allocated=(allocated : Bool | Nil)
is the current locker allocated
-
#allocated? : Bool | Nil
is the current locker allocated
-
#bank_id : String | Int64
the locker system ids
-
#bank_id=(bank_id : String | Int64)
the locker system ids
-
#building : String | Nil
metadata for locating the locker (if known) - placeos zone ids
-
#building=(building : String | Nil)
metadata for locating the locker (if known) - placeos zone ids
-
#expires_at : Time | Nil
when the locker is released if known / enabled in the locker system
-
#expires_at=(expires_at : Time | Nil)
when the locker is released if known / enabled in the locker system
- #level : String | Nil
- #level=(level : String | Nil)
-
#location : Symbol
identifier for location services
- #locker_id : String | Int64
- #locker_id=(locker_id : String | Int64)
-
#locker_name : String
the text on the outside of the locker
-
#locker_name=(locker_name : String)
the text on the outside of the locker
-
#mac : String | Nil
a single field that can be used to uniquely identify a locker should not clash with other systems and ideally be usable to identify the user who is allocated to the locker (via a lookup function)
-
#mac=(mac : String | Nil)
a single field that can be used to uniquely identify a locker should not clash with other systems and ideally be usable to identify the user who is allocated to the locker (via a lookup function)
Constructor Detail
Instance Method Detail
metadata for locating the locker (if known) - placeos zone ids
when the locker is released if known / enabled in the locker system
a single field that can be used to uniquely identify a locker should not clash with other systems and ideally be usable to identify the user who is allocated to the locker (via a lookup function)
a single field that can be used to uniquely identify a locker should not clash with other systems and ideally be usable to identify the user who is allocated to the locker (via a lookup function)