bradsjm / hassio-addons Goto Github PK

HassOS 5.3 on RPi 4

The installation worked fine and GUI is available under the port 8090 but I cannot connect to it with any external grabber.
Even with Flatbuffers Server on port 19400 and Protocol Buffers Server on port 19445 enabled I cannot send any information to the Hyperion.

Is there any way to debug the issue of why those ports behave differently than 8090? Any suggestions will be greatly appreciated.

hi i am using hyperion as an addon(vm on vmware esx). but I can't see the live video on hyperion ...

root@dba1ceb5-hyperion:/# v4l2-ctl --all
Driver Info:
Driver name : uvcvideo
Card type : USB Video: USB Video
Bus info : usb-0000:03:00.0-2.1
Driver version : 5.4.83
Capabilities : 0x84a00001
Video Capture
Metadata Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
Width/Height : 1920/1080
Pixel Format : 'MJPG' (Motion-JPEG)
Field : None
Bytes per Line : 0
Size Image : 4147200
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Full Range)
Flags :
Crop Capability Video Capture:
Bounds : Left 0, Top 0, Width 1920, Height 1080
Default : Left 0, Top 0, Width 1920, Height 1080
Pixel Aspect: 1/1
Selection: crop_default, Left 0, Top 0, Width 1920, Height 1080, Flags:
Selection: crop_bounds, Left 0, Top 0, Width 1920, Height 1080, Flags:
Streaming Parameters Video Capture:
Capabilities : timeperframe
Frames per second: 30.000 (30/1)
Read buffers : 0
brightness 0x00980900 (int) : min=-128 max=127 step=1 default=-11 value=-11
contrast 0x00980901 (int) : min=0 max=255 step=1 default=148 value=148
saturation 0x00980902 (int) : min=0 max=255 step=1 default=180 value=180
hue 0x00980903 (int) : min=-128 max=127 step=1 default=0 value=0

This problem with only HomeAssistant addons. With I start hyperion-ng in debian its OK.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.

• failed to open vchiq instance
  [cmd] /run.sh exited 255
  [cont-finish.d] executing container finish scripts...
  [cont-finish.d] done.
  [s6-finish] waiting for services.
  [s6-finish] sending all processes the TERM signal.

On Raspberry Pi 3+ the LED WS281x isn’t working with PWM. Tried it with GPIO 18. It works with the standalone Hyperion OS, but with the same settings on the Hassio Add on, it does not work. The Log:

Can’t open device file
: Operation not permitted
2021-01-12T13:45:23.769 hyperiond LEDDEVICE : Device disabled, device ‘ws281x’ signals error: ‘Failed to open. Error message: Failed to create mailbox device’
Can’t open device file
: Operation not permitted

At the Remote Control page, the LED device button on the right side is also always off. When i push it on, directly the message

Can’t open device file
: Operation not permitted

appears in the log.

The Hassio System is installed with 32 bit image directly with the hassio OS standalone on the SD Card.

I also tried deactivating Audio in the config file and hdmi forcing. Both did not work.

When starting the addon with version 2.0.13 the log shows:

s6-overlay-suexec: fatal: can only run as pid 1

Reverting back to 2.0.12 and the addon starts with no errors.

Bug report

When pressing the HA light toggle for Hyperion-NG (2.0.12) the LED array switches off as intended without changing any of the other states (eg. the used capture methods in this case)

However when you click on the light toggle again, it will toggle the LED array back on but will disable the opposite capture mode of the one active.

Eg. When Screen Capture is enabled and the LED array is switched on from HA it toggles off the USB Capture and vice versa.

Steps to reproduce

• Put Hyperion in default state for my setup (ie. Smoothing, Black bar detection, Screen capture, USB capture and LED output in ON state
• Press Hyperion button on light card off and on again

What is expected?

Both capture methods should remain unchanged regardless of the LED output state

What is actually happening?

The non-active capture method will be toggled into the OFF state

System

Home Assistant Server

• Virtual machine (Synology VMM)
• Home Assistant OS 6.6
• Home Assistant Supervisor: 2021.10.8
• Home Assistant Core: 2021.11.5

Hyperion Server:

• Build: (HEAD detached at df149583) (GitHub-dc6aa4dd/df149583-1637501177)
• Build time: Nov 21 2021 16:50:38
• Git Remote: https://github.com/hyperion-project/hyperion.ng
• Version: 2.0.12
• UI Lang: en (BrowserLang: en-US)
• UI Access: expert
• Avail Capt: v4l2,qt,dx
• Config path: C:/Users/forkless/.hyperion
• Database: read/write

Hyperion Server OS:

• Distribution: Windows 10 Version 2009
• Architecture: x86_64
• Kernel: winnt (10.0.19044 (WS: 64))
• Root/Admin: true
• Qt Version: 5.15.0
• Python Version: 3.10.0
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36

Alpha 10 just released.
https://hyperion-project.org/forum/index.php?thread/11973-alpha-10-is-out/

I would like to try you addon on this version.

Thanks

Can't work it out.
I'm getting "Operation not permitted" when trying to turn on adalight usb device.
Looks like addon or hyperion itself doesn't have enough permissions.

I'm also tried "full_access", but no luck
Do you have an idea how to make access hyperion in docker to usb?

Hey, it seems the slug format is not valid for hassio.addon_start to use. Currently it's: dba1ceb5_hyperion.ng and it is not accepting it when I test it out in developer tools. Could you remove the ".ng" which is what I believe is causing the issue. Thx. Awesome job btw!

Improvement proposal:
Would it be possible to upgrade container image for the latest hyperion.ng build?

Added
WLED: Support storing/restoring state, fixes #1101

I've tested it and it's working as expected so I would like to move my hyperion.ng rpi setup to my hassio vm installation.

I've recently moved from a Pi4 to a NUC and would love to use your docker on amd64.

I've added the repository and the log file acknowledged the new git as expected:

21-12-12 18:56:47 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/bradsjm/hassio-addons repository

But the Hyperion add-on does not show up for selection at the bottom of the Add-on Store as expected.

Hi,
Could you please update to Alpha 10.1?
https://hyperion-project.org/forum/index.php?thread/12265-alpha-10-1-is-out/
Thanks.

Hello,

today i have installed the core update 2021.2.3. After the update my leds turn off, on, off, on and so on.

My brother has the same bug after the update. My brother and i have an rpi4

Does anyone have the same problem?

Hey, I noticed something when I was randomly looking at my logs. It seems that "auto_uart" and "devices" in config are deprecated. Everything is working fine though.

I am using a RPI400 for my HA OS install. I have added Hyperion NG as an add-on, but for some reason when I try to choose the capture card I have plugged into it, it says "No Capture Device Discovered". I've tried rebooting, I've tried using other usb ports, nothing.
Logs:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023-08-14T11:15:56.004 |__| MAIN              : <INFO> Starting Hyperion [non-GUI mode] - 2.0.15, (HEAD detached at 2.0.15) (GitHub-70e1043/24a00e3-1676809483), built: Feb 19 2023:15:46:14
2023-08-14T11:15:56.010 |__| MAIN              : <INFO> Set user data path to '/config/hyperion'
2023-08-14T11:15:56.540 |__| DAEMON            : <INFO> CEC handler created
2023-08-14T11:15:56.609 |__| EFFECTFILES       : <INFO> 40 effects loaded from directory :/effects/
2023-08-14T11:15:56.624 |__| EFFECTFILES       : <INFO> 22 effect schemas loaded from directory :/effects/schema/
2023-08-14T11:15:56.629 |__| EFFECTFILES       : <INFO> 0 effects loaded from directory /config/hyperion/custom-effects/
2023-08-14T11:15:56.780 |__| FLATBUFSERVER     : <INFO> Started on port 19400
2023-08-14T11:15:56.781 |__| PROTOSERVER       : <INFO> Started on port 19445
2023-08-14T11:15:56.810 |I0| EFFECTENGINE      : <INFO> Run effect "Rainbow swirl fast" on channel 1
2023-08-14T11:15:56.811 |I0| LEDDEVICE         : <INFO> Start LedDevice 'philipshue'.
2023-08-14T11:15:56.831 |__| DAEMON            : <ERROR> Suspend/resume handler - System bus is not connected
2023-08-14T11:15:56.832 |__| DAEMON            : <ERROR> Lock/unlock handler- Session bus is not connected
2023-08-14T11:15:56.865 |I0| HYPERION          : <INFO> Initial foreground effect 'Rainbow swirl fast' started
2023-08-14T11:15:56.868 |__| HYPERION-INSTMGR  : <INFO> Hyperion instance 'First LED Hardware instance' has been started
2023-08-14T11:15:56.870 |__| JSONSERVER        : <INFO> Started on port 19444
2023-08-14T11:15:56.988 |__| WEBSERVER         : <INFO> 'Hyperion http-Webserver' started on port 8090
2023-08-14T11:15:57.035 |__| WEBSERVER         : <INFO> 'Hyperion https-Webserver' started on port 8092
2023-08-14T11:15:59.865 |I0| LEDDEVICE         : <ERROR> Cannot resolve mDNS hostname for given service [DIYHue._hue._tcp.local]!
2023-08-14T11:16:00.008 |I0| EFFECTENGINE      : <INFO> Effect [Rainbow swirl fast] finished

Thank you for including v4l-utils package as now I can modify the values for the default video device. I'm using a camera as my grabber which is working fine but I need to modify some values to make it respond faster. What I'm using now are those values:
v4l2-ctl -c auto_exposure=1 -c white_balance_auto_preset=3 -c iso_sensitivity_auto=0 -c exposure_metering_mode=2
but to call this I need to log into docker container and call it from there. Ideally, I would like to have a parameter in HA plugin config page to do it. If you could add it, it would be great.