labgrid.driver.power package
Submodules
labgrid.driver.power.apc module
labgrid.driver.power.digipower module
labgrid.driver.power.digitalloggers_http module
Driver for Digital Loggers PDU that use the legacy HTTP API. Tested with Web Power Switch 7.
labgrid.driver.power.digitalloggers_restapi module
Driver for Digital Loggers PDU that use the REST API. Tested with Ethernet Power Controller 7.
Based on https://www.digital-loggers.com/restapi.pdf
By default, only an authenticated user is allowed by REST API.
- NetworkPowerPort:
model: ‘digitalloggers_restapi’ host: ‘http://admin:1234@192.168.0.100’ index: 0
labgrid.driver.power.eaton module
labgrid.driver.power.eg_pms2_network module
- labgrid.driver.power.eg_pms2_network.login(base_url: str) None[source]
Use the default password 1, because labgrid doesn’t support password encryption, modifying the password doesn’t secure the device as the password would be stored as plain-text.
labgrid.driver.power.eth008 module
This driver implements a power port for the robot electronics 8 relay outputs board.
Driver has been tested with: * ETH008 - 8 relay outputs
labgrid.driver.power.gude module
labgrid.driver.power.gude24 module
This driver implements a power port for Gude Power Switches with up to 24 ports. These switches differ in their API to the previous 8-port switches for set- and get-commands.
Driver has been tested with: * Gude Expert Power Control 8080
labgrid.driver.power.gude8031 module
labgrid.driver.power.gude8225 module
labgrid.driver.power.gude8316 module
labgrid.driver.power.mfi_mpower module
Controls the Ubiquity mFi mPower Power Strip with Ethernet and Wi-Fi connectivity via HTTP. Reference: https://dl.ubnt.com/guides/mfi/mFi_mPower_PRO_US_QSG.pdf
Example configuration to use port #3 on a device with URL ‘http://172.17.180.53/’ with the default credentials (‘ubnt’ for both username and password):
- NetworkPowerPort:
model: mfi_mpower host: ‘http://172.17.180.53/’ index: 3
Custom credentials can be provided in the URL itself:
- NetworkPowerPort:
model: mfi_mpower host: ‘http://username:password@172.17.180.53/’ index: 3
labgrid.driver.power.netio module
labgrid.driver.power.netio_kshell module
tested with NETIO 4C, should be compatible with all NETIO 4-models
labgrid.driver.power.poe_mib module
tested with Cisco CBS350, should be compatible with switches implementing the PoE administration MiB
labgrid.driver.power.raritan module
Driver for the Raritan PDUs
Documentation sources: * https://www.circitor.fr/Mibs/Html/P/PDU2-MIB.php * http://support.raritan.com/px3/version-3.0.3/user-guides/PX3-0B-v3.0-E.pdf * https://cdn1.raritan.com/download/pdu-g2/4.0.20/MIB_Usage_4.0.20_49038.pdf
labgrid.driver.power.rest module
Rest interface for controlling power port, using PUT / GET on a URL.
- NetworkPowerPort:
model: rest host: ‘http://192.168.0.42/relay/{index}/value’ index: 3
Will do a GET request to http://192.168.0.42/relay/3/value to get current relay state, expecting a response of either ‘0’ (relay off) or ‘1’ (relay on), and a PUT request to http://192.168.0.42/relay/3/value with request data of ‘0’ or ‘1’ to change relay state.
labgrid.driver.power.sentry module
This driver was tested on those models: CW-24VDD and 4805-XLS-16 but should be working on all devices implementing Sentry3-MIB
labgrid.driver.power.shelly_gen1 module
Interface for controlling relays of Shelly devices using the Gen 1 API
- NetworkPowerPort:
model: shelly_gen1 host: ‘http://192.168.0.42’ index: 0
Will do a GET request to http://192.168.0.42/relay/0 to get the current relay state, and a POST request to http://192.168.0.42/relay/0 with request data of ‘turn=off’ or ‘turn=on’ to change the relay state.
Also, see the official Gen 1 Device API documentation: https://shelly-api-docs.shelly.cloud/gen1/
labgrid.driver.power.shelly_gen2 module
Interface for controlling relays of Shelly devices using the Gen 2+ API
- NetworkPowerPort:
model: shelly_gen2 host: ‘http://192.168.0.42’ index: 0
Will do a POST request to http://192.168.0.42/rpc to get the current relay state or change the state.
Also, see the official Gen 2+ Device API documentation: https://shelly-api-docs.shelly.cloud/gen2/General/RPCProtocol
labgrid.driver.power.siglent module
tested with Siglent SPD3303X-E, and should be compatible with all SPD3000X series modules
labgrid.driver.power.simplerest module
- Simple rest interface for Power Port. Used for ex. misc Raspberry Pi configs
Author: Kjeld Flarup <kfa@deif.com>
The URL given in hosts in exporter.yaml must replace {value} with ‘0’ or ‘1’ It is optional whether to use {index} or not.
- NetworkPowerPort:
model: simplerest host: ‘http://172.17.180.53:9999/relay/{index}/{value}’ index: 0
labgrid.driver.power.tinycontrol module
A driver to control the Tinycontrol IP Power Socket 6G10A v2 Reference: https://tinycontrol.pl/media/documents/manual_IP_Power_Socket__6G10A_v2_LANLIS-010-015_En-1.pdf
Example configuration to use port #3 on a device with URL ‘http://172.17.180.53:9999/’
- NetworkPowerPort:
model: tinycontrol host: ‘http://172.17.180.53:9999/’ index: 3
labgrid.driver.power.tinycontrol_tcpdu module
A driver to control the Tinycontrol tcPDU Reference: https://docs.tinycontrol.pl/en/tcpdu/api/commands
Example configuration to use port #3 on a device with URL ‘http://172.17.180.53/’
- NetworkPowerPort:
model: tinycontrol_tcpdu host: ‘http://172.17.180.53’ index: 3
labgrid.driver.power.tplink module
Tested with TP Link KP303, and should be compatible with any strip supported by kasa
labgrid.driver.power.ubus module
UBUS jsonrpc interface for PoE management on OpenWrt devices. This comes in handy if devices are connected to a PoE switch running OpenWrt.
The URL given in hosts in exporter.yaml must accept unauthenticated UBUS calls for the two poe calls info and manage.
Further information is availbe at https://openwrt.org/docs/techref/ubus#acls
- NetworkPowerPort:
model: ubus host: ‘http://192.168.1.1/ubus’ index: 1