lifx-emulator-core
Core Python library for emulating LIFX devices using the LAN protocol.
This package provides the embeddable library for creating virtual LIFX devices in your own projects. It implements the binary UDP protocol from the LIFX LAN Protocol specification.
Installation
pip install lifx-emulator-core
Quick Start
import asyncio
from lifx_emulator import EmulatedLifxServer, DeviceManager
from lifx_emulator.factories import create_color_light
from lifx_emulator.repositories import DeviceRepository
async def main():
# Create devices
devices = [
create_color_light(serial="d073d5000001"),
create_color_light(serial="d073d5000002"),
]
# Create repository and manager
repository = DeviceRepository()
manager = DeviceManager(repository)
# Start the emulator server
server = EmulatedLifxServer(
devices=devices,
device_manager=manager,
bind_address="127.0.0.1",
port=56700,
)
await server.start()
print("LIFX Emulator running on 127.0.0.1:56700")
# Keep running until interrupted
try:
await asyncio.Event().wait()
finally:
await server.stop()
asyncio.run(main())
mDNS interface limitation
mDNS is opt-in (mdns_enabled=True). On Linux, zeroconf may receive and answer mDNS queries through an interface other than the selected one when another process has joined the multicast group there. Selecting an interface, including loopback, is not a receive-isolation security boundary; synthetic device records may be visible on that other network. Strict isolation requires an external network boundary such as a dedicated network namespace or firewall policy. The emulator retains the public zeroconf API and does not patch its sockets to enforce receive isolation.
Features
- Emulate color lights, multizone strips, tiles, infrared, HEV, and switch devices
- Full LIFX LAN protocol implementation
- Persistent device state storage
- Testing scenarios for simulating edge cases
- Product registry with 137+ official LIFX products
Documentation
Full documentation is available at: https://djelibeybi.github.io/lifx-emulator
Related Packages
- lifx-emulator: Standalone CLI tool and HTTP management API built on this library
License
1 maintainer
Metadata
1 maintainer
Release files for lifx-emulator-core 3.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lifx_emulator_core-3.13.0.tar.gz | 260.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lifx_emulator_core-3.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 411.6 kB
Release files / lifx_emulator_core-3.13.0.tar.gz
| Download URL | lifx_emulator_core-3.13.0.tar.gz |
|---|---|
| Size | 260.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3169ef2673198d78ab035ae4080bf3c5231507bd48293d7312cd006d2891aca7
|
|
BLAKE2b-256 checksum How to use checksums |
c59f76edb32617ae4c9851b7c4ddb9dba647022b8119e37a9f801cc1b336531a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / lifx_emulator_core-3.13.0-py3-none-any.whl
| Download URL | lifx_emulator_core-3.13.0-py3-none-any.whl |
|---|---|
| Size | 151.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2898332d5aa6dcf45b615d6ecad58b1d0f21b47de8264f143b3af6593d8f48fc
|
|
BLAKE2b-256 checksum How to use checksums |
e42b562f754914e5deec387dec9a1349abb871d4485144cd0fb9f071cda8eb1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency log
