@Nordic wrote:

Hi all! I’m having a world of trouble trying to figure out how to change my Home Assistant IP address (ideally from the terminal). I changed my ipv4 addresses over to 10.0.0.* from 192.168.1.* (long story), but HA is still getting assigned to 192.168.1.20! I’ve tried reserving a 10.0.0.* address for it in my router with no luck. I can’t access the front end, but I can get to it from a terminal because it’s running in a virtual machine on a Linux server. Any help is greatly appreciated!

Posts: 1

Participants: 1

Read full topic

@jadelapena wrote:

Hello,

I have added a Sonoff RF Bridge to my Home Assistant via the ESPHome integration. I have not modified or flashed any custom FW such as Tasmota in the device.

It is shown as “Remote” with an icon and the “sonoff 10049b901” identifier.

I want to create an automation to toggle my Sonoff Basic Switch when my RF Device Door Sensor opens or changes state. In my eWelink account, my door sensor is named as “Door”. After reading some tutorials, I can determine the changing state of my Sonoff Remote when I close/open my Door sensor as shown below. It shows the state ‘on’ when I do so.

door705×96 6.56 KB

Using the Home Assistant Automation UI Editor, I created a simple automation. Afterwards, a few lines of codes were generated in my /config/automations.yaml file as shown below:

- id: '1590193583928'
  alias: New Automation
  description: ''
  trigger:
  - entity_id: remote.sonoff_100049b901
    from: 'on'
    platform: state
    to: 'on'
  condition: []
  action:
  - data: {}
    service: script.1590193360982

However, it did not perform the automation. Everytime I play with the door sensor, the script that is incorporated to my automation does not execute.

Furthermore, I tried to create another automation using the File Editor. I have created the following code but still, no luck. The automation does not work.

- alias: Door Detect
  trigger:
    entity_id: remote.sonoff_100049b901
    platform: event
    from: []
    event_type: sonoff.remote
    event_data:
      name: Door
  action:
  - data: {}
    service: switch.toggle
    entity_id: switch.sonoff_1000bb0a56

I watched a good tutorial video in YouTube with this link. At the 10:02 time mark, it started to show the Sonoff RF Bridge, same as my situation. I followed the code he discussed later on in the automations.yaml but it did not work on my side.

Can someone please help me with this issue? This seems pretty simple but I really had a hard time solving it. Thanks in advance!

-Jade

Posts: 1

Participants: 1

Read full topic

@taargusspargel wrote:

Hey everyone,

I am using the Remote UI (Nabu Casa) to access Home Assistant when I’m away from home and it works great and I’m very happy with it.

My problem, my automations won’t work. When I click on ‘execute’ in the frontend, my automations work as expected, the Remote UI connects and disconnects. I can’t make the automations actually work though, when I leave my house, life 360 correctly shows me as “Away” and when I’m home it shows me as “Home”, but Remote UI does not connect or disconnect.

- alias: Cloud Connect
  trigger:
    platform: state
    entity_id: device_tracker.life360_e
    from: "Home"
    to: "Away"
  action:
    service: cloud.remote_connect


- alias: Cloud Disconnect
  trigger:
    platform: state
    entity_id: device_tracker.life360_e
    from: "Away"
    to: "Home"
  action:
    service: cloud.remote_disconnect

Can someone please tell me what I’m doing wrong?? I would greatly appreciate it.

Posts: 1

Participants: 1

Read full topic

@mychickensonfire wrote:

I updated from 0.109.6 to 0.110.1 and the opengarage integration failed on restart (log below). The garage door still functions via the opengarage.io android app.

Anyone else having a similar issue?

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/opengarage/cover.py", line 73, in setup_platform
    async_get_clientsession(hass),
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 47, in async_get_clientsession
    hass.data[key] = async_create_clientsession(hass, verify_ssl)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 68, in async_create_clientsession
    connector = _async_get_connector(hass, verify_ssl)
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 207, in _async_get_connector
    connector = aiohttp.TCPConnector(enable_cleanup_closed=True, ssl=ssl_context)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 731, in __init__
    loop=loop)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 229, in __init__
    loop = get_running_loop(loop)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/helpers.py", line 268, in get_running_loop
    loop = asyncio.get_event_loop()
  File "/usr/local/lib/python3.7/asyncio/events.py", line 644, in get_event_loop
    % threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'SyncWorker_10'.

Posts: 1

Participants: 1

Read full topic

@invinciberry wrote:

So I am playing around with the new zwave2mqtt integration. I successfully added my Kwikset doorlock with control working in Home Assistant. But for the life of me I just can’t figure out why I can’t get my WADWAZ-1 from Nortek to work correctly.

From what I can tell, the device will add successfully and will report it’s initial state to Home Assistant but that’s it. It will stay in the sleeping state forever even when I close and open the door. From what I can tell, there is no MQTT message fired when the door opens and closes, So I think it’s a ZWAVE problem?

In the debug console I can see this following:

OpenZWave Detail, Node013, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0d, 0x03, 0x20, 0x01, 0x00, 0xdd
OpenZWave Detail,
OpenZWave Info, Node013, Received Basic set from node 13: level=0. Treating it as a Basic report.
OpenZWave Detail, Node013, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0d, 0x0a, 0x71, 0x05, 0x07, 0x00, 0x00, 0xff, 0x07, 0x02, 0x00, 0x00, 0x65
OpenZWave Detail,
OpenZWave Warning, NotificationCCTypes::GetAlarmNotificationTypes - Unknown Alarm Type 7
OpenZWave Warning, NotificationCCTypes::GetEventForAlarmType - Unknown AlarmType/Event 7/d
OpenZWave Warning, NotificationCCTypes::GetAlarmType - Unknown AlarmType 7
OpenZWave Info, Node013, Received Notification report (>v1): Type: Unknown (7) Event: Unknown (2) Status: true, Param Length: 0
OpenZWave Warning, Node013, Couldn't Find a ValueList for Notification Type 7 (1)
OpenZWave Info, Node013, Automatically Clearing Alarm in 5000ms
OpenZWave Info, Timer: adding event in 5000 ms
OpenZWave Detail, Timer: waiting with timeout 5000 ms

And here is what’s under Hass Device JSON:

{
  "type": "binary_sensor",
  "object_id": "contact",
  "discovery_payload": {
    "payload_on": true,
    "payload_off": false,
    "value_template": "{{ value_json.value }}",
    "device_class": "door",
    "state_topic": "homeassistant/nodeID_13/48/1/0",
    "json_attributes_topic": "homeassistant/nodeID_13/48/1/0",
    "device": {
      "identifiers": [
        "zwave2mqtt_0xdebbaeb6_node13"
      ],
      "manufacturer": "Linear (Nortek Security Control LLC)",
      "model": "WADWAZ-1 Door/Window Sensor (0x0102)",
      "name": "nodeID_13",
      "sw_version": "4.84"
    },
    "name": "nodeID_13_contact",
    "unique_id": "zwave2mqtt_0xdebbaeb6_13-48-1-0"
  },
  "discoveryTopic": "binary_sensor/nodeID_13/contact/config",
  "values": [
    "48-1-0"
  ],
  "persistent": false,
  "id": "binary_sensor_contact"
}

Please Help, I don’t know where to start.

Posts: 2

Participants: 2

Read full topic

@ob2s wrote:

I have a web server running on my pi that runs HA, and I can create an iFrame with that web server in it and it displays on my PC web browser, because that same web browser prompts me for login to that page and caches creds, but on ios HA app, I can’t seem to give it the login credentials. It just says unauthorized, no matter what I try.

So I was wondering, is it possible to use the embedded www page server in HA /local/www to also serve up a cgi-like fork of a python script ?

/local/www/cgi-bin/foo.py?str=x 

Or must I use ios’ safari and pull up HA in that browser, so that I may authenticate to the pi webserver in safari and thus see the panel properly ?
Thanks

Posts: 1

Participants: 1

Read full topic

@jas_kidd32 wrote:

I have setup Home Assistant running on a docker container on Raspberry Pi 4. My goal is to integrate my TP Link HS100 Smart Plug with my Logitech Harmony Hub. I’ve configured an Emulated Hue but I cannot detect it via the Harmony Android app or MyHarmony on PC.

I’ve included --net=host when I started the Home Assistant container.

The TP Link Smart Plug appears on the on the Home Assistant UI but the Emulated Hue doesn’t. Is this normal?

configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

tplink:
  switch:
    - host: 10.10.10.7

emulated_hue:
  host_ip: 192.168.1.20
  entities:
    switch.subwoofer:
      name: "Subwoofer"
      hidden: false

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

homeassistant:
  customize: !include customize.yaml

customize.yaml

switch.subwoofer:
  emulated_hue: true

http://192.168.1.20:8300/description.xml

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.20:8300/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>Home Assistant Bridge (192.168.1.20)</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.philips.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>001788FFFE23BFC2</serialNumber>
<UDN>uuid:2f402f80-da50-11e1-9b23-001788255acc</UDN>
</device>
</root>

http://192.168.1.20:8300/api/pi/lights

{"1": {"manufacturername": "Home Assistant", "modelid": "HASS123", "name": "Subwoofer", "state": {"bri": 254, "mode": "homeautomation", "on": false, "reachable": true}, "swversion": "123", "type": "Dimmable light", "uniqueid": "00:f4:2d:c8:af:d7:36:9e-c3"}}

Posts: 1

Participants: 1

Read full topic

@prankousky wrote:

Hi everybody,

I have multiple cameras that I mainly include in notifications (if front gate opens, send telegram message with snapshot from camera x). I want to create an automation to trigger camera.record, then send that recording (instead of a picture). Is there a way to determine when the file has actually been written?

In other words: let’s say I want to record 120 seconds, then send this recording. How can I make sure that this file is sent, not a previous recording? I thought of delay: "00:02:00", but there must be a better way.

My incomplete package looks like this:

binary_sensor:
  - platform: tod
    name: Nachtmodus
    after: "20:45"
    before: 07:45"

automation:
  trigger: 
    - platform: state
      entity_id: binary_sensor.draussen_gartentor_contact
      to: "on"
  condition:
    condition: state
    entity_id: binary_sensor.nachtmodus
    state: "on"
  action:
    - service: camera.record
      entity_id: camera.cam_einfahrt
      filename: /config/downloads/cams/einfahrt.mp4

What do I need to add so that I will always get the most recent recording (instead of a previous recording, or an incomplete file)? At first I thought I could use something like filename: '/tmp/{{ entity_id }}_{{ now().strftime("%Y%m%d-%H%M%S") }}.mp4', but the strftime value will be different for the file to what I could use in my service: notify.all part of the code, as those wouldn’t be executed at the very same second.

I thought of creating a second automation to observe when camera.cam_einfahrt's status changes from recording to idle; however, for some reason, even when I call the service to record a file (via developer tools), the camera will be set to idle, which is weird. I checked after the set period of time: the file will be recorded, so syntax etc. was correct, but the camera entity did not report that it was actually recording.

Thank you for your ideas

Posts: 1

Participants: 1

Read full topic

@lujmoarf wrote:

Hi all

I’m new to the community and to Home Assistant but I have been playing with it for several weeks and loves it !

I have integrated plex media player. it is working great but I’m trying to have plex playing something coming from the Text To Speech

from the multimedia player card, when I try to enter a text, I get the following error

any idea if it is possible to send some text to speech to plex ?

thank you

Luj

Posts: 1

Participants: 1

Read full topic

@stban1983 wrote:

Hi!
i want to sync volume between two different media_player.
Volume is an attribute for both entity.

When i change the volume on media player A i want that media_player B change too.

Is it possible to create an automation ?

Posts: 2

Participants: 2

Read full topic

@Konrad162 wrote:

Hi,
I’m new into Home assistant - automation. I dig through many materials, but it seems I still can’t find the answer to a simple question…

How to put variable instead of a static number in automation conditions.

Przechwytywanie1152×524 48.1 KB

This gives me an error:
Message malformed: expected float for dictionary value @ data['below']

Do you have any good and up to date tutorials about automation scripts in Home assistant?

Posts: 1

Participants: 1

Read full topic

@PianSom wrote:

First off, thanks for updating this so it works again

I have an LG TV which is connected both to an antenna and a satellite. I am writing a script to change channel using media_player.play_media and cannot find a method of distinguishing between the two connections. Both of these seem to be classified as “Live TV” as a Source.

For example, when using antenna channel 101 is “BBC ONE HD”. When using satellite channel 972 is “BBC One HD”.

• If I use a media_content_id of any of “BBC ONE HD”, “BBC One HD” or 972 then I get the satellite channel 972.

• If I use 101 then I get satellite channel 101.

What I want to get is antenna channel 101. How can I achieve this, please?

(Tagging @jjlawren who is listed in the release notes - apologies if inappropriate)

Posts: 1

Participants: 1

Read full topic

@mpaneth wrote:

I have just upgraded from 109.2 to 110.1 and my Lovelave Alarm Control Panel now has an error “Entity not available: alarm_control_panel.home_alarm”

My automation.yaml is

alarm_control_panel:
  - platform: manual
    name: home_alarm
    code: !secret alarm_password
    pending_time: 30
    arming_time: 10
    delay_time: 20
    trigger_time: 4
    disarmed:
      trigger_time: 0
    armed_home:
      arming_time: 0
      delay_time: 0

My Lovelace alarm panel configuration is

entity: alarm_control_panel.home_alarm
name: Alarm Panel
states:
  - arm_home
  - arm_away
type: alarm-panel

Help please
Mike Paneth
Melbourne, Australia

Posts: 3

Participants: 2

Read full topic

@hioctane61 wrote:

Using Remote Control for nabu casa. The url is https but it’s appearing as “not fully secure”, according to chrome (same in firefox). Any advice, my url is generated by nabu casa.

Posts: 3

Participants: 3

Read full topic

@chemelli wrote:

Hi,

I would like my automation to wait 2 minutes for a state change before processing.
This is the extract of the relevant code:

  trigger:
    platform: event
    event_type: state_changed
  condition:
    condition: and
    conditions:
      - condition: state
        entity_id: {{ trigger.event.data.entity_id }}
        for:
          minutes: 2

I tried several syntax for the entity_id , but unfortunately none works.
Any suggestion ?

Thank you,

Simone

Posts: 1

Participants: 1

Read full topic

@Polarlys wrote:

Hi,
I have installed HA and Mosquitto as Dockers on a Synology and it works fine. But there is a permanent Disk usage roundabout 10-20 Percent, i think because of the database-usage from HA and/or Mosquitto.
My Synology is in the living room and the noise of the HDDs is a little bit to loud for me - and maybe this is also not good for the life of the HDDs.
So I had the idea to use an external small SSD on an USB3-Port of the Synology an to move the /config-Folder of the HA-Docker to this external storage. The Mosquitto-Server could move to a raspberrypi, which is also soundless.
Had someone tested this before and would that work? Do I have just to move the /config-Folder to his new location and point in the docker-container the mount-path to this new location or is something more to do?
Thanks!

Posts: 1

Participants: 1

Read full topic

@SparkySharpie wrote:

Hello! I’m new here and just getting into home automation using rpi, arduino, and esp8266.

Can I simultaneously use my Raspberry Pi running rasbian and use home assistant, or does home assistant require a dedicated device just for home automation? This question might already have been answered, but I couldn’t find it.
Thanks!

Posts: 3

Participants: 3

Read full topic

@ivanbliminse wrote:

Hello!

I’m using Ubuntu 18.04 in a virtual machine and running Home assistant (HA) and AppDaemon (AD) using docker-compose. I’m a new user and have been playing with this for about a week.
This is the docker-compose.yml I’m using:

version: "3"
services:
  homeassistant:
    container_name: home-assistant
    image: homeassistant/home-assistant:0.110.1
    volumes:
      - /home/$USER/hass/docker_files/homeassistant/config:/config
    environment:
      - TZ=America/New_York
    restart: always
    network_mode: host
  appdaemon:
    depends_on:
      - homeassistant
    container_name: appdaemon
    image: acockburn/appdaemon:4.0.3
    volumes:
      - /home/$USER/hass/docker_files/appdaemon:/conf
    ports:
      - 5050:5050
    restart: always

This is the appdaemon.yaml

appdaemon:
  time_zone: "America/New_York"
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: !secret elevation
  title: Test
  status_update: none

  plugins:
    HASS:
      type: hass
      ha_url: "http://localhost:8123"
      token: !secret token
hadashboard:
  dashboard_dir: ./dashboards
http:
  url: http://127.0.0.1:5050
  password: !secret ad_password
api:
admin:

The issue I’m having is that when I try to run both HA and AD using docker compose I keep getting connection errors.

appdaemon        | 2020-05-23 08:03:55.389055 INFO AppDaemon: AppDaemon Version 4.0.3 starting
appdaemon        | 2020-05-23 08:03:55.389186 INFO AppDaemon: Python version is 3.8.2
appdaemon        | 2020-05-23 08:03:55.389255 INFO AppDaemon: Configuration read from: /conf/appdaemon.yaml
appdaemon        | 2020-05-23 08:03:55.389317 INFO AppDaemon: Added log: AppDaemon
appdaemon        | 2020-05-23 08:03:55.389415 INFO AppDaemon: Added log: Error
appdaemon        | 2020-05-23 08:03:55.389502 INFO AppDaemon: Added log: Access
appdaemon        | 2020-05-23 08:03:55.389602 INFO AppDaemon: Added log: Diag
appdaemon        | 2020-05-23 08:03:55.400465 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
appdaemon        | 2020-05-23 08:03:55.406492 INFO HASS: HASS Plugin Initializing
appdaemon        | 2020-05-23 08:03:55.406638 INFO HASS: HASS Plugin initialization complete
appdaemon        | 2020-05-23 08:03:55.406979 INFO AppDaemon: Initializing HTTP
appdaemon        | 2020-05-23 08:03:55.407238 INFO AppDaemon: Using 'ws' for event stream
appdaemon        | 2020-05-23 08:03:55.414304 INFO AppDaemon: Starting API
appdaemon        | 2020-05-23 08:03:55.416407 INFO AppDaemon: Starting Admin Interface
appdaemon        | 2020-05-23 08:03:55.416636 INFO AppDaemon: Starting Dashboards
appdaemon        | 2020-05-23 08:03:55.419098 WARNING HASS: Disconnected from Home Assistant, retrying in 5 seconds
appdaemon        | 2020-05-23 08:03:55.423195 INFO AppDaemon: App 'hello_world' added
appdaemon        | 2020-05-23 08:03:55.423767 INFO AppDaemon: Found 1 total apps
appdaemon        | 2020-05-23 08:03:55.424042 INFO AppDaemon: Starting Apps with 1 workers and 1 pins
appdaemon        | 2020-05-23 08:03:55.424696 INFO AppDaemon: Running on port 5050

appdaemon        | 2020-05-23 08:04:40.001883 WARNING HASS: Disconnected from Home Assistant, retrying in 5 seconds
appdaemon        | 2020-05-23 08:04:45.004781 WARNING HASS: Disconnected from Home Assistant, retrying in 5 seconds

But if I run AD from the comand line using the same configuration file, it works correctly:

$ appdaemon -c /home/$USER/hass/docker_files/appdaemon

2020-05-23 07:05:42.027019 INFO AppDaemon: AppDaemon Version 4.0.3 starting
2020-05-23 07:05:42.027135 INFO AppDaemon: Python version is 3.7.7
2020-05-23 07:05:42.027219 INFO AppDaemon: Configuration read from: /home/user/hass/docker_files/appdaemon/appdaemon.yaml
2020-05-23 07:05:42.027303 INFO AppDaemon: Added log: AppDaemon
2020-05-23 07:05:42.027395 INFO AppDaemon: Added log: Error
2020-05-23 07:05:42.027478 INFO AppDaemon: Added log: Access
2020-05-23 07:05:42.027560 INFO AppDaemon: Added log: Diag
2020-05-23 07:05:42.034421 WARNING AppDaemon: config_dir: /home exists, but is not writeable, owner: root
2020-05-23 07:05:42.035766 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2020-05-23 07:05:42.041046 INFO HASS: HASS Plugin Initializing
2020-05-23 07:05:42.041191 INFO HASS: HASS Plugin initialization complete
2020-05-23 07:05:42.041403 INFO AppDaemon: Initializing HTTP
2020-05-23 07:05:42.041576 INFO AppDaemon: Using 'ws' for event stream
2020-05-23 07:05:42.047168 INFO AppDaemon: Starting API
2020-05-23 07:05:42.049315 INFO AppDaemon: Starting Admin Interface
2020-05-23 07:05:42.049485 INFO AppDaemon: Starting Dashboards
2020-05-23 07:05:42.050009 WARNING AppDaemon: css: /home exists, but is not writeable, owner: root
2020-05-23 07:05:42.050586 WARNING AppDaemon: javascript: /home exists, but is not writeable, owner: root
2020-05-23 07:05:42.056007 INFO HASS: Connected to Home Assistant 0.110.1
2020-05-23 07:05:42.069887 INFO AppDaemon: App 'hello_world' added
2020-05-23 07:05:42.070366 INFO AppDaemon: Found 1 total apps
2020-05-23 07:05:42.070586 INFO AppDaemon: Starting Apps with 1 workers and 1 pins
2020-05-23 07:05:42.081352 INFO AppDaemon: Running on port 5050
2020-05-23 07:05:42.088983 INFO HASS: Evaluating startup conditions
2020-05-23 07:05:42.093506 INFO AppDaemon: Got initial state from namespace default
2020-05-23 07:05:44.084011 INFO AppDaemon: Scheduler running in realtime
2020-05-23 07:05:44.085467 INFO AppDaemon: Adding /home/user/hass/docker_files/appdaemon/apps to module import path
2020-05-23 07:05:44.086507 INFO AppDaemon: Loading App Module: /home/user/hass/docker_files/appdaemon/apps/hello.py
2020-05-23 07:05:44.088251 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello
2020-05-23 07:05:44.114133 INFO hello_world: Hello from AppDaemon
2020-05-23 07:05:44.114580 INFO hello_world: You are now ready to run Apps!

I was wondering if anyone can help me find what I’m missing or what I’m doing wrong.

Posts: 1

Participants: 1

Read full topic

@jimford wrote:

I have 2 LED lamps branded ‘HeKee’, which can be controlled by the ‘MagicHome’ app.

The page https://www.home-assistant.io/integrations/flux_led say that there is a good chance that the lamps can be used with Home Assistant.

I’ve put in my configuration.yaml file:

light:

• platform: flux_led
  devices:
  192.168.1.8:
  name: flux_lamp
  mode: “w”

But whilst an icon for the lamp appears in the Overview, it’s greyed out and doesn’t work. I also get the message that it’s “Unavailable” and “This entity does not have a unique ID, therefore its settings cannot be managed from the UI.”.

Obviously the problem is either that my particular bulbs simply don’t work with H.A. or that the configuration is incorrect.

I’d be grateful for any help, please.

Jim

Posts: 1

Participants: 1

Read full topic

@tannaroo wrote:

Hi all,
I have a HDCVT 4x4 HDMI Matrix which I am trying to control through HA. I have all of the hex commands but right now I just want to turn it on/off.

Below is an extract of the Hex commands from my user manual:
Power on/off command package length is 13byte:

[0xa5+0x5b+0x08+0x0B+ Power onoff(0x0f:ON; 0xf0:OFF) +0x00+0x00+0x00+0x00+0x00+0x00+0x00+ checksum ]

Power on/off query package is 13byte:

This is a query command which mean you must send query package and then receive an answer.

For example:

Send package: A5 5B 08 0C 00 00 00 00 00 00 00 00 checksum

Receive package: A5 5B 08 0C F0 00 00 00 00 00 00 00 checksum

The blue F0 mean Power off, if 0F mean Power on.

I have tried to following in my yaml file (which has no errors and put in the real IP address) but when in my overview when I select it - nothing happs to my HDMI matrix. Can someone kindly help?

switch:
  - platform: command_line
    switches:
      hdmi_matrix:
        command_on: ech -e "\A5\5B\08\0C\0F\00\00\00\00\00\00\00\DE" | nc 192.168.1.xxx
        command_off: ech -e "\A5\5B\08\0C\F0\00\00\00\00\00\00\00\FD" | nc 192.168.1.xxx
        friendly_name: HDMI Matrix

Posts: 1

Participants: 1

Read full topic