hyperion.ng: Home Assistant Integration is unable to control certain components
- I confirm that this is an issue rather than a question.
Bug report
Home Assistant Hyperion integration is unable to control several components with the effect being the HA switch shows changed but Hyperion has not or, HA does not receive acknowledgement of the request actually changing and the HA switch then resets to off.
Steps to reproduce
Upgrade Hyperion to latest 2.0.15 and HA Integration to latest version.
What is expected?
For the damn integration to be able to control all components of Hyperion!
What is actually happening?
- HA cannot toggle the state of Component Forwarder or Component LED Device as Hyperion does not see the request and does not acknowledge a change.
- Component Platform Capture toggles in HA and stays put but no change is observed in Hyperion.
- These work: Component Blackbar Detection, Component Boblight Server, Component Smoothing, Component Capture USB-Input and Component All
System
Hyperion Server:
- Build: ()
- Build time: Feb 19 2023 16:07:19
- Git Remote:
- Version: 2.0.15
- UI Lang: en (BrowserLang: en-US)
- UI Access: default
- Avail Screen Cap.: framebuffer,x11,xcb,qt
- Avail Video Cap.: v4l2
- Avail Audio Cap.: audio
- Avail Services: boblight,cec,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
- Config path: /home/hyperion/.hyperion
- Database: read/write
Hyperion Server OS:
- Distribution: Debian GNU/Linux 10 (buster)
- Architecture: x86_64
- CPU Model: Intel(R) Core(TM) i3-3227U CPU @ 1.90GHz
- CPU Type: 58
- Kernel: linux (4.19.0-24-amd64 (WS: 64))
- Root/Admin: false
- Qt Version: 5.11.3
- Python Version: 3.7.3
- Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 23 (7 by maintainers)
@Lord-Grey I won’t be able to provide additional logs until I am back home tomorrow evening.
@dermotduffy
The tan in the response is the one send with the request, that you can correlate request and response. As you do not sent a tan, the returned tan is zero.
Send to server (192.168.1.102:19444): b'{"command": "componentstate", "componentstate": {"component": "LEDDEVICE", "state": true}}\n'
If you provide a tan with the request, the same is returned with the response. Please see below, where I send a request with tan=23.