Posts by iam960

  • How to setup Hyperion with a Yeelight solution

    ping -a gives an error:

    And arp -a gives only the IP and the MAC address of the device.

  • How to setup Hyperion with a Yeelight solution

    I am trying to run again the wizard but it keep in this window:

    This previously happened sometimes, but now I have tried multiples times and it doesn't pass this window.

    Just now, I have removed the LAN permission for the bulb from the xiaomi app, and I have got this:

    It is strange because the name that is automatically assigned to the strip (the only one bulb with LAN permission just now) is 'conf_leds_layout_cl_entire'. But yesterday, in my router, it has the name 'yeelink-light-strip2_miap7fe2'.

    I will repeat the wizard later until the both bulbs were found.

    This is the ping output for the two bulbs:

    "ping"

    PING 192.168.31.115 (192.168.31.115): 56 data bytes
    64 bytes from 192.168.31.115: seq=0 ttl=255 time=400.514 ms
    64 bytes from 192.168.31.115: seq=1 ttl=255 time=7.545 ms
    64 bytes from 192.168.31.115: seq=2 ttl=255 time=4.487 ms
    ^C
    --- 192.168.31.115 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max = 4.487/137.515/400.514 ms

    $ ping 192.168.31.177
    PING 192.168.31.177 (192.168.31.177): 56 data bytes
    64 bytes from 192.168.31.177: seq=0 ttl=255 time=1.719 ms
    64 bytes from 192.168.31.177: seq=1 ttl=255 time=1.651 ms
    64 bytes from 192.168.31.177: seq=2 ttl=255 time=1.657 ms
    64 bytes from 192.168.31.177: seq=3 ttl=255 time=1.424 ms
    64 bytes from 192.168.31.177: seq=4 ttl=255 time=1.464 ms
    64 bytes from 192.168.31.177: seq=5 ttl=255 time=7.060 ms
    ^C
    --- 192.168.31.177 ping statistics ---
    6 packets transmitted, 6 packets received, 0% packet loss
    round-trip min/avg/max = 1.424/2.495/7.060 ms

  • How to setup Hyperion with a Yeelight solution

    Thanks for your support. I have activated the debug mode. When I enter in the Yeelight Wizard, this is the appearing window:

    The Identify button don't produce any effect, and both light and ambilight don't work. When I put the bulb IP in 'Network devicename', it does work without problem. Though the majority of movies are continously blinking (losing the HDMI source). Then, I change this parameter in 'Platform Capture':
    Height: 64
    Width: 64
    Capture frequency: 30

    And it work with all the movies.

    I paste the debug output:

    "debug"


    2020-11-03T13:22:43.529 hyperiond WEBSOCKET : <DEBUG> JsonAPI.cpp:1386:handleLedDeviceCommand() | message: [{"command":"leddevice","ledDeviceType":"yeelight","subcommand":"discover","tan":72
    4}]
    2020-11-03T13:22:43.530 hyperiond SSDPDISCOVER : <DEBUG> SSDPDiscover.cpp:206:discoverServices() | Search for Service [wifi_bulb], address [229.255.255.250], port [1982]
    2020-11-03T13:22:43.602 hyperiond SSDPDISCOVER : <DEBUG> SSDPDiscover.cpp:252:discoverServices() | Found target [wifi_bulb], plus record [yeelight://192.XXX.XX.XXX:55443] matches [LOCATION:yeel
    ight(.*)]
    2020-11-03T13:22:44.105 hyperiond SSDPDISCOVER : <DEBUG> SSDPDiscover.cpp:252:discoverServices() | Previous line repeats 1 times
    2020-11-03T13:22:44.105 hyperiond SSDPDISCOVER : <DEBUG> SSDPDiscover.cpp:294:discoverServices() | [1] service record(s) found
    2020-11-03T13:22:49.111 hyperiond LEDDEVICE : <DEBUG> LedDeviceYeelight.cpp:1370:discover() | devicesDiscovered: [{"devices":[{"cache-control":"max-age=3600","domain":"168.XX.XXX","hostname"
    :"192","id":"yeelight://192.XXX.XX.XXX:55443","ip":"192.XXX.XX.XXX","location":"yeelight://192.XXX.XX.XXX:55443","other":{"bright":"34","color_mode":"1","ct":"4000","date":"","ext":"","fw_ver":
    "73","hue":"115","id":"0x00000000080c10b4","model":"stripe","name":"","power":"off","rgb":"3692597","sat":"39","support":"get_prop set_default set_power toggle set_bright start_cf stop_cf set_s
    cene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust adjust_bright adjust_ct adjust_color set_music set_name"},"port":55443,"server":"POSIX UPnP/1.0 YGLC/1","st":"","usn":""}],
    "ledDeviceType":"yeelight"}]
    2020-11-03T13:22:49.111 hyperiond WEBSOCKET : <DEBUG> JsonAPI.cpp:1409:handleLedDeviceCommand() | response: [{"devices":[{"cache-control":"max-age=3600","domain":"168.XX.XXX","hostname":"192
    ","id":"yeelight://192.XXX.XX.XXX:55443","ip":"192.XXX.XX.XXX","location":"yeelight://192.XXX.XX.XXX:55443","other":{"bright":"34","color_mode":"1","ct":"4000","date":"","ext":"","fw_ver":"73",
    "hue":"115","id":"0x00000000080c10b4","model":"stripe","name":"","power":"off","rgb":"3692597","sat":"39","support":"get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene
    cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust adjust_bright adjust_ct adjust_color set_music set_name"},"port":55443,"server":"POSIX UPnP/1.0 YGLC/1","st":"","usn":""}],"ledD
    eviceType":"yeelight"}]
    2020-11-03T13:22:56.356 hyperiond WEBSOCKET : <DEBUG> JsonAPI.cpp:1386:handleLedDeviceCommand() | message: [{"command":"leddevice","ledDeviceType":"yeelight","params":{"hostname":"192","port
    ":55443},"subcommand":"identify","tan":1}]
    2020-11-03T13:22:56.357 hyperiond LEDDEVICE : <DEBUG> LedDeviceYeelight.cpp:1402:identify() | params: [{"hostname":"192","port":55443}]
    2020-11-03T13:22:56.357 hyperiond LEDDEVICE : <DEBUG> LedDeviceYeelight.cpp:1406:identify() | apiHost [192], apiPort [55443]
    2020-11-03T13:22:56.358 hyperiond LEDDEVICE : <ERROR> Yeelight device '192' signals error: 'Connection refused'

    Thanks again!

    Iam.