enigma2 for Homey
Control and monitor compatible Enigma2 receivers from Homey over your local network using OpenWebif.
Production version:
enigma2 for Homey
Test version:
enigma2 for Homey – Test 
Source code:
About the app
The enigma2 app connects Homey to compatible Linux-based DVB receivers through the OpenWebif API.
Depending on the receiver and its OpenWebif implementation, Homey can:
- Turn the receiver on or place it in standby
- Monitor whether it is online or unavailable
- Check whether it is in standby
- Control volume and mute
- Change channels
- Control play, pause, next and previous
- Show the current channel and programme title
- Show programme duration and progress
- Display the channel picon as album artwork
- Send remote-control command IDs
- Display messages on the television
- Restart the Enigma2 software
- Reboot the receiver
- Put the receiver into deep standby
- Use these functions in standard and Advanced Flows
Current versions
At the time of this update, recent development includes:
- Availability and unavailability Flow triggers
- Configurable polling interval
- Device-specific Flow cards for multiple receivers
- Improved receiver targeting
- Fixed standby and mute Flow behaviour
- Improved polling and playback-state recovery
- Improved pairing validation
- HTTP and HTTPS protocol selection
- Better handling of self-signed HTTPS certificates
- Safer error handling without exposing credentials or complete request URLs
- Improved message validation
- Czech and Slovak programme-title decoding
- ISO-6937 and Central European text-encoding handling
- Updated dependencies and regression testing
Requirements
To use the integration:
- The receiver must run Enigma2.
- The OpenWebif plugin must be installed and running.
- Homey must be able to reach the receiver over the local network.
- The OpenWebif port must be accessible from Homey.
- A username and password must be entered if OpenWebif authentication is enabled.
Both HTTP and HTTPS are supported. HTTPS is recommended when the receiver supports it, but it is no longer mandatory.
Typical settings are:
- HTTP: port 80
- HTTPS: port 443
- Protocol: Automatic, HTTP or HTTPS
- Polling interval: 5–60 seconds
- Username and password: optional, depending on OpenWebif configuration
In Automatic mode, the app uses HTTPS for port 443 and HTTP for other ports.
HTTPS certificates
Many Enigma2 receivers use a self-signed HTTPS certificate. For compatibility, Allow untrusted certificates is enabled by default.
Disable this option if your receiver uses a certificate that can be properly validated and you want strict certificate verification.
Allowing an untrusted certificate encrypts the connection but does not verify the identity of the receiver. Only use this on a trusted local network.
Network configuration
Homey and the receiver must be able to communicate directly.
Communication can fail when:
- Homey and the receiver are in isolated VLANs
- Client isolation is enabled
- The receiver is on an isolated guest network
- A firewall blocks the configured OpenWebif port
- The receiver’s IP address has changed
- OpenWebif listens only on another interface or port
- HTTP or HTTPS is selected incorrectly
Assigning the receiver a fixed IP address or DHCP reservation is strongly recommended.
Pairing
- Confirm that OpenWebif works from a browser on the same network.
- In Homey, select Add device and choose enigma2.
- Enter the receiver’s IP address or hostname.
- Enter the OpenWebif port.
- Select Automatic, HTTP or HTTPS.
- Enter the username and password when required.
- Decide whether self-signed certificates should be accepted.
- Test the connection.
- Add the detected receiver.
Pairing calls the OpenWebif device-information endpoint and validates that the selected receiver returns a usable Enigma2 response before the device is added.
Device information and picons
During polling, the app can display:
- Current channel or service name
- Current programme title
- Programme duration
- Programme position
- Programme progress
- Playing or paused state
- Current volume
- Mute state
- Standby state
- Receiver availability
When available, the current channel picon is loaded through OpenWebif and displayed as album artwork in Homey.
Picons must be accessible through the configured OpenWebif connection under:
/picon/
For example:
https://RECEIVER-IP:443/picon/
or:
http://RECEIVER-IP:80/picon/
The exact filename is derived automatically from the current Enigma2 service reference.
Flow support
When…
The app provides standard Homey capability triggers and dedicated receiver triggers:
- Device becomes available
- Device becomes unavailable
- Receiver turned on
- Receiver turned off
- Started playing
- Stopped playing
- Artist or channel information changed
- Track or programme title changed
- Volume changed
The availability triggers are activated when polling detects that the receiver has gone offline or has become reachable again.
And…
- Receiver is or is not in standby
- Receiver is or is not turned on
- Receiver is or is not playing
Then…
Power and receiver management
- Turn on or wake from standby
- Turn off or enter standby
- Toggle on or off
- Enter deep standby
- Reboot the receiver
- Restart the Enigma2 software
Channel and playback control
- Channel up
- Channel down
- Next
- Previous
- Play
- Pause
- Toggle play or pause
Volume control
- Set volume
- Change volume relatively
- Volume up
- Volume down
- Mute
- Unmute
- Toggle mute
Additional actions
- Send a remote-control command ID
- Display a message on the receiver
Device-specific Flow cards
Current Flow cards allow the target Enigma2 receiver to be selected explicitly. This is important when multiple receivers are installed.
Older non-device-specific Flow cards are deprecated and can no longer be added to new Flows. Existing Flows using those cards remain supported for backward compatibility.
New Flows should always use the device-specific cards.
Deep standby warning
The Deep standby mode action shuts the receiver down to its lowest power state.
After executing this action:
- OpenWebif will no longer be reachable.
- Homey cannot send additional network commands.
- The receiver will be marked unavailable.
- Normal network wake-up may not work.
Recovery depends entirely on the receiver hardware and configuration. Some receivers support Wake-on-LAN or a scheduled timer; others must be powered on manually.
Do not use deep standby in a Flow unless you have verified how your particular receiver can be started again.
Displaying messages
Messages use the following format:
Type|Timeout|Message
Do not add spaces around the | separators.
Message types
0– Yes/No question; currently displayed only, without returning the selected answer to Homey1– Information message2– Plain message3– Attention or warning message
Timeout
Enter the display time in seconds.
Use 0 to request an indefinitely displayed message, if supported by the receiver image and OpenWebif version.
Examples
Information message displayed for 10 seconds:
1|10|The garage door is still open
Attention message displayed for 30 seconds:
3|30|Alarm activated
Plain message without a timeout:
2|0|Welcome home
The message text may contain additional | characters. Only the first two separators are interpreted as the type and timeout.
Sending remote-control command IDs
Use Send command as ID to emulate individual buttons from a compatible Enigma2 remote control.
Command references:
-
Enigma2 command spreadsheet
Green means supported. An empty green field means that the command is not programmed for that device.
Command availability depends on the receiver, remote-control profile, Enigma2 image and OpenWebif implementation.
Compatible receivers
The app should work with Enigma2 receivers that expose a compatible OpenWebif API.
Potentially compatible manufacturers and platforms include:
- AB-COM
- Amiko and selected IPBOX devices
- AX Technology
- Dreambox
- Edision
- Formuler
- GigaBlue
- Octagon
- Opticum
- Protek
- Red Eagle
- Redline
- Spycat
- VU+
- Other Enigma2-compatible Linux receivers
Compatibility is determined by the Enigma2 image and OpenWebif behaviour, not only by the receiver brand.
Not every receiver, image or OpenWebif version is available for testing. Please report successful results as well as problems.
Troubleshooting
If a receiver becomes unavailable:
- Open OpenWebif from a browser on the same network.
- Verify the IP address and port.
- Check whether HTTP or HTTPS is configured correctly.
- Verify the username and password.
- If using HTTPS, check the self-signed-certificate setting.
- Confirm that Homey can reach the receiver’s network or VLAN.
- Verify that the receiver is not in deep standby.
- Restart the enigma2 Homey app.
- Reproduce the problem.
- Immediately create a Homey app diagnostic report.
When reporting a problem, include:
- Diagnostic-report ID
- Exact receiver brand and model
- Enigma2 distribution or image
- Enigma2 version
- OpenWebif version
- Homey model and firmware version
- enigma2 app version
- Production or test channel
- Configured protocol and port
- Whether authentication is enabled
- Whether a self-signed certificate is used
- Approximate time of the failure
- The exact action or Flow card that failed
Do not publish usernames, passwords, access tokens, public IP addresses or remote-access details.
For general help and configuration questions, use this Homey Community topic.
For confirmed application bugs and development-related reports, use GitHub:
Credits
Special thanks to Markus Mahr / carp3-noctem, the original author and developer of this application. 
Thanks also to:
- Martin Timmermans for the Dutch translation
- The OpenWebif and Enigma2 communities
- Contributors who test the app on different receivers and Enigma2 images
- ChatGPT for development assistance
This is an independent community integration and is not affiliated with or endorsed by Athom, OpenWebif or any receiver manufacturer.
Community development and appreciation
These Homey Community apps are developed and maintained in my spare time. They are free to use, and contributions are never required.
Did you know? In my experience maintaining community Homey apps, only a very small proportion of users choose to support their development financially—even when a new device integration or specific feature has been implemented at their request.
Contributions are entirely optional, but they are a meaningful way to recognise the time invested in development, testing, compatibility updates and ongoing user support.
Send an optional thank-you via PayPal
A contribution does not unlock additional features or affect the support you receive. It is simply a way to say thank you.
Other Homey apps I maintain
 Smart Presence Wi-Fi presence detection |
 Xiaomi Mi Home Xiaomi Mi Home devices |
 Broadlink IR, RF and smart devices |
|||
 TP-Link KASA LAN Local Kasa control |
 Yeelights LAN Local Yeelight control |
 Xiaomi Miija Temperature and humidity sensors |
|||
 Octoprint Monitor your 3D printer |
 Virtual |
