@FreeSoftwareServers wrote:

I’m trying to hack setting my Roku Volume. I now “how” i can do it by setting volume down multiple times (perhaps 100) and then up to set-point, but I don’t want to make 100 “volume down” service calls. There has to be a way to script the volume up/down portion so it’s mutiple steps/service calls in one configuration. Any ideas?

Posts: 1

Participants: 1

Read full topic

@jjross wrote:

Is there a recommended way to move from the YAML configured HomeKit bridge to the configuration through the integrations page?

I would like to be able to manage my included domains and entities via the GUI (much like I do for the Alex and Google integrations) but I’m currently configured via YAML. When I click the “options” link in the integrations page I was getting a pop up indicating that the component is configured via YAML.

To try and get around this I removed the configuration from YAML and restarted and I had the same message so I followed the instructions in the docs to reset the component and I deleted the integration and then added it again.

After deleting and adding again I can select the included domains but I can’t get the GUI to filter down to the entity / domain level even though the pop up says this:

“You will be able to select which entities to exclude from this list on the next screen.”

I would like to start over with the integration. Is there a way to do this? I tried rebooting HA and the integration just kept showing up again.

I also have an issue with the entities showing as unavailable in HomeKit but I think that’s because things are in a bad state at the moment.

Posts: 1

Participants: 1

Read full topic

@HellfireZA wrote:

Hi guys, I’m really struggling here with trying to increase and decrease my brightness with an automation.
I’ve tried all of the below with now luck.

Brightness 4 will change the brightness to 100 on the Dimmer in console.

Brightness 2 will just set the brightness_pct value to the initial 50

 - alias: 'Brightness3'
    trigger:
      platform: state
      entity_id: binary_sensor.dimtest
    action:
      - service: light.turn_on
        entity_id: light.lamp4
        data_template:
          brightness: >-       
            {{  states.light.lamp4.attributes.brightness | int + 10 }}

  - alias: 'Brightness4'
    trigger:
      platform: state
      entity_id: binary_sensor.dimtest
    action:
      - service: light.turn_on
        entity_id: light.lamp4
        data_template:
          brightness: '{{states.light.lamp4.attributes.brightness + 10}}'

  - alias: 'Brightness'
    trigger:
      platform: state
      entity_id: binary_sensor.dimtest
    action:
      - service: light.turn_on
        entity_id: light.lamp4
        data_template:
          brightness: >
             {% set suggested = states.light.lamp4.attributes.brightness |int + 10 %}
             {% if suggested < 200 %}
             {{ suggested }}
             {% else %}
             200
             {% endif %}
             
  - alias: 'Brightness2'
    trigger:
      platform: event
      event_type: click
      event_data:
        entity_id: binary_sensor.button_id
        click_type: single
    action:
      - service: light.turn_on
        entity_id: light.lamp4
        data_template:
          brightness_pct: >
            {% set step_size = 50 %}
            {% set cb = (state_attr('light.lamp4', 'brightness') | float / 255.0) * 100.0 %}
            {% set new_brightness = cb | int + step_size %}
            {% if 91 <= new_brightness < (90 + step_size) %}
              100
            {% else %}
              {{ new_brightness if new_brightness < 100 else 0 }}
            {% endif %}

Posts: 1

Participants: 1

Read full topic

@mmiller7 wrote:

I’ve read a number of people’s solutions for monitoring when a sensor stops updating to alert me and I wasn’t quite satisfied with any of them. Many used an automation template to compare the ‘time’ or ‘date_time’ to the desired sensor ‘last_updated’, however this seems like it would require a large number of automation to keep track of so I can be notified WHICH sensor to check.

I think I’ve come up with an elegant way to do this which gives me lots of flexibility. If I set MQTT to force_update I could even graph it on Lovelace and have an overview of any outlier sensors that may have signal issues since the interval should be regular. Mine are temp-humidity, I want to catch a change to either (clearly if ANY update arrives it’s still updating) so I used an IF condition to grab whichever updated most recently.

The solution I came up with was using template sensors (since I’m already making sensors for each MQTT item) that track the seconds since the last update as so:

sensor:

  - platform: template
    sensors:
      outside_front_sensor_age:
        friendly_name: "Outside Front Sensor Age"
        entity_id: sensor.time
        value_template: >-
          {% if states.sensor.outside_front_temperature.last_changed > states.sensor.outside_front_humidity.last_changed %}
            {{ (states.sensor.time.last_changed - states.sensor.outside_front_temperature.last_changed).total_seconds() | round(0) }}
          {% else %}
            {{ (states.sensor.time.last_changed - states.sensor.outside_front_humidity.last_changed).total_seconds() | round(0) }}
          {% endif %}
        unit_of_measurement: "Seconds"

  - platform: template
    sensors:
      outside_rear_sensor_age:
        friendly_name: "Outside Rear Sensor Age"
        entity_id: sensor.time
        value_template: >-
          {% if states.sensor.outside_rear_temperature.last_changed > states.sensor.outside_rear_humidity.last_changed %}
            {{ (states.sensor.time.last_changed - states.sensor.outside_rear_temperature.last_changed).total_seconds() | round(0) }}
          {% else %}
            {{ (states.sensor.time.last_changed - states.sensor.outside_rear_humidity.last_changed).total_seconds() | round(0) }}
          {% endif %}
        unit_of_measurement: "Seconds"

  - platform: template
    sensors:
      shed_driveway_sensor_age:
        friendly_name: "Shed Driveway Sensor Age"
        entity_id: sensor.time
        value_template: >-
          {% if states.sensor.shed_driveway_temperature.last_changed > states.sensor.shed_driveway_humidity.last_changed %}
            {{ (states.sensor.time.last_changed - states.sensor.shed_driveway_temperature.last_changed).total_seconds() | round(0) }}
          {% else %}
            {{ (states.sensor.time.last_changed - states.sensor.shed_driveway_humidity.last_changed).total_seconds() | round(0) }}
          {% endif %}
        unit_of_measurement: "Seconds"

Now, I can use a single automation to easily message me for all the problems of interest to me, and based on the friendly_name I can be alerted if it’s the battery low, sensor age, or something else:

#System Status Alerts

  - alias: 'Telegram Check Sensor Alert'
    trigger:
      # Low Battery Alerts
      # Binary Sensor Alerts (on = alarm)
      - entity_id: 
          # Acurite Temp & Humidity Sensors
          - binary_sensor.outside_front_sensor_battery_low
          - binary_sensor.outside_rear_sensor_battery_low
          - binary_sensor.shed_driveway_sensor_battery_low
          - binary_sensor.shed_backyard_sensor_battery_low
          - binary_sensor.attic_sensor_battery_low
        platform: state
        from: 'off'
        to: 'on'
        # Reduce flapping
        for:
          minutes: 15
      # Low Battery Alerts
      - platform: numeric_state
        entity_id:
          # Zigbee
          - sensor.washer_vibration_battery_level
          - sensor.dryer_vibration_battery_level
          # Z-Wave
          - sensor.dining_room_gate_sensor_battery_level
        below: 33
        # Reduce flapping
        for:
          minutes: 15
      # Monitor sensor age - not reporting in
      - platform: numeric_state
        entity_id:
          # Acurite Temp & Humidity Sensors Age Expired
          - sensor.outside_front_sensor_age
          - sensor.outside_rear_sensor_age
          - sensor.shed_driveway_sensor_age
          - sensor.shed_backyard_sensor_age
          - sensor.attic_sensor_age
        # Seconds for timeout
        above: 1800
    action:
      service: notify.telegram_my_user
      data_template:
        message: |
          Warning - Check Sensor:
          {{ trigger.to_state.attributes.friendly_name }}

The messages from this single automation then end up looking like this - clean and concise easily letting me know what to check:

To me, as a software engineer, this seems much easier and more modular for maintenance than having to keep track of a mess of automation…I can just make the sensors as I make the MQTT sensors and then add 1 line to my notification alerts. If I decide I need to be alerted via another method, I only have to change 1 automation and I can have it (for example) blink a light or send an email instead of Telegram messages. If I decide to change the interval, I can change it in 1 place on the alert automation. If I add a sensor, I don’t have to worry about copying the correct alert logic, I can just add the new sensor to the existing list. If I want to add more actions, I can simply reference the known working age calculations.

I also plan to make a watchdog automation to detect if ALL the sensors drop out and automatically try restarting RTL433, sometimes if the USB cable is bumped it seems to get stuck. This should be a lot easier now that I have sensors with numeric to compare instead of having to do a bunch of complex templates with conditions duplicating the same code as my alert…now I can simply reference the age-sensor values.

For my particular scenario (Accurite sensors) I have made a bash-script to generate my MQTT temp/humidity/battery sensors and filter/last_updated sensors given a numeric sensor-ID and location-name string. I’ve posted it on GitHub if someone wants to use it as a basis for making other bulk sensors.

I wish this was an easily referenced attribute I could use built into hassio, but in the meantime I guess this is nearly as convenient.

Posts: 1

Participants: 1

Read full topic

@indigo78 wrote:

Please help. After more than a bit of trial and error I was able to get NanoMote Quad connected. Now that it’s connected to the as a node in the Z-Wave network, I’m at a loss of how to get it to do anything. I really want to set up some scenes for others in my house so they don’t have to grab phones or talk to Siri. Nothing fancy but I can’t seem to find it when creating Automations. Here’s what I get in the logs.

2020-05-20 15:13:22.357 Info, Node003, Received Central Scene set from node 3: scene id=2 in 7680 seconds. Sending event notification.
2020-05-20 15:13:22.357 Detail, Node003, Initial read of value
2020-05-20 15:13:22.357 Detail, Node003, Notification: ValueChanged
2020-05-20 15:13:22.637 Detail, Node003, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x03, 0x05, 0x5b, 0x03, 0x16, 0x80, 0x03, 0x3b

Any help is much appreciated.

Posts: 1

Participants: 1

Read full topic

@jriker1 wrote:

I am trying to enable OpenZWave integration that came with 0.110:

1. So I setup a separate docker instance on the computer for Misquitto MQTT
2. Went into configuration.yaml and added in:

mqtt:
  broker: 192.168.0.50
  username: hass
  password: <pass>
  port: 1883

3. Restarted HA
4. Added custom repo: https://github.com/marcelveldt/hassio-addons-repo/tree/master/ozwdaemon
5. Install Open Z-Wave Daemon
6. Did Click on Configuration > Integrations > + > OpenZWave (beta)
7. Clicked SUBMIT and FINISH

So nothing else from my interpretation of the documentation but it does say on the OpenZWave (beta) “After completing the configuration flow, the OpenZWave integration will be available.”.

Is all I did above the “configuration flow” or was it supposed to ask me questions. Also is it not working or am I missing something?

Posts: 1

Participants: 1

Read full topic

@darkarchives wrote:

New user, so apologies if this is a basic question.

My Z Wave Network isn’t restarting and I’m not sure what the problem is, a nudge in the direction of how to fix this would be appreciated: Here are the log entires:

2020-05-20 18:32:05 WARNING (Dummy-52) [openzwave] Z-Wave Notification DriverFailed : {'notificationType': 'DriverFailed', 'homeId': 0, 'nodeId': 0}
2020-05-20 18:36:53 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2020-05-20 18:36:53 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  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/zwave/__init__.py", line 888, in _finalize_start
    network.set_poll_interval(polling_interval, False)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 894, in set_poll_interval
    self.manager.setPollInterval(milliseconds, bIntervalBetweenPolls)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 564, in manager
    raise ZWaveException(u"Manager not initialised")
openzwave.object.ZWaveException: 'Zwave Generic Exception : Manager not initialised'
2020-05-20 18:37:17 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2020-05-20 18:37:17 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  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/zwave/__init__.py", line 888, in _finalize_start
    network.set_poll_interval(polling_interval, False)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 894, in set_poll_interval
    self.manager.setPollInterval(milliseconds, bIntervalBetweenPolls)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 564, in manager
    raise ZWaveException(u"Manager not initialised")
openzwave.object.ZWaveException: 'Zwave Generic Exception : Manager not initialised'
2020-05-20 19:05:38 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2020-05-20 19:05:38 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  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/zwave/__init__.py", line 888, in _finalize_start
    network.set_poll_interval(polling_interval, False)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 894, in set_poll_interval
    self.manager.setPollInterval(milliseconds, bIntervalBetweenPolls)
  File "/usr/local/lib/python3.7/site-packages/openzwave/network.py", line 564, in manager
    raise ZWaveException(u"Manager not initialised")
openzwave.object.ZWaveException: 'Zwave Generic Exception : Manager not initialised'

Posts: 1

Participants: 1

Read full topic

@guice wrote:

How do I use cards to display an attribute of an entity?

I don’t see any examples: https://www.home-assistant.io/lovelace/

The only thing I can see are direct entity state values, or custom cards to do custom things. How can I display an entity’s attribute instead of it’s state value?

e.g.
An entity has an attribute ip_address and I want to show that using Entity:

  - entities:
      - entity: sensor.iot_devices_status
        name: IoT IP Address
        // ?? show sendsor.iot_devices_status[ip_address] ??
    type: entities

Posts: 1

Participants: 1

Read full topic

@yonny24 wrote:

I’m testing out different platofrms - hassio first which I liked but erased it as it was a VM on windows using too much RAM.
Now formatted windows and just got ubuntu works out nicely.

BUT I used home assistant core this time from:

So where on earth do I config everything??
Is there no yaml? Is there no add-on store? How can I add HACS for example?

Have I missed a lot?
Seems extremely limited. Can’t do anything with it.

Posts: 1

Participants: 1

Read full topic

@Cheesenwine wrote:

Hi all,

I have a mental block on how to deal with this logic… I have a single MQTT topic on which I’d like 2 controls. I’d like to have

1. a On/Off switch with no rules
2. a switch with automation which will turn it off again in 1 hour.

So here’s what I put together, but is of course not working since both switches work off the same MQTT topic. Toggling one switch will always also toggle the other and as a result the automation always runs, turning it off 1 hour later.

Any idea how I could get around this?

Switch definition:

switch Generator:
  name: "Generator"
  platform: mqtt
  qos: 2
#  retain: true
  state_topic: "energy/generator/stat/POWER"
  command_topic: "energy/generator/cmnd/POWER"
  
switch Generator1Hour:
  name: "Generator 1Hr"
  platform: mqtt
  qos: 2
#  retain: true
  state_topic: "energy/generator/stat/POWER"
  command_topic: "energy/generator/cmnd/POWER"

Automation definition

- alias: 'Rule - Generator for 1 Hour'
  trigger:
    platform: state
    entity_id: switch.generator_1hr
    to: 'on'
    for:
      hours: 1
  action:
    service: switch.turn_off
    entity_id: switch.generator_1hr

Posts: 1

Participants: 1

Read full topic

@Steveo wrote:

I have HA 0.110 and use ZHA with a Nortek stick.

I get regular updates for the current consumption and on/off status, but not the total consumption value
I saw a workaround of pulling the value directly from the DB, but it is not set there.

Screenshot 2020-05-21 at 11.20.331258×722 35.5 KB

sorry for multiple posts, I could only show one image per post.

Posts: 4

Participants: 1

Read full topic

@lawsuitup wrote:

So I use the Rest platform to pull weather information from the open weather map one call api - which means I dont use a weather.xxx entity but instead a bunch of sensors. As of now I use an entities card with the custom multiple entity row to give me each days data.

Here it is:

entities:
  - entities:
      - entity: sensor.openweather_temp_current
        name: Current
      - entity: sensor.openweather_feels_like
        name: Feels Like
      - entity: sensor.openweather_temp_max_today
        name: High
      - entity: sensor.openweather_temp_min_today
        name: Low
    entity: sensor.openweather_temp_current
    name: Today
    show_state: false
    type: 'custom:multiple-entity-row'
  - entities:
      - entity: sensor.openweather_temp_max_tomorrow
        name: High
      - entity: sensor.openweather_temp_min_tomorrow
        name: Low
    entity: sensor.openweather_temp_current
    name: Tomorrow
    show_state: false
    type: 'custom:multiple-entity-row'
  - entities:
      - entity: sensor.openweather_temp_max_3
        name: High
      - entity: sensor.openweather_temp_min_3
        name: Low
    entity: sensor.openweather_temp_current
    name: The Day After Tomorrow
    show_state: false
    type: 'custom:multiple-entity-row'
  - entities:
      - entity: sensor.openweather_temp_max_4
        name: High
      - entity: sensor.openweather_temp_min_4
        name: Low
    entity: sensor.openweather_temp_current
    name: The Day After That
    show_state: false
    type: 'custom:multiple-entity-row'
  - entities:
      - entity: sensor.openweather_temp_max_5
        name: High
      - entity: sensor.openweather_temp_min_5
        name: Low
    entity: sensor.openweather_temp_current
    name: The Day After That
    show_state: false
    type: 'custom:multiple-entity-row'
title: Weather Forecast
type: entities

My problem is that the sensors for each days sensor do not correspond to days but correspond to days relative to today meaning- there is a sensor that will show the the high temperature for today, tomorrow, three days from today and so on.

Is it possible to template the name: portion of the entity row to reflect the correct day dynamically? As in it knows that today is thursday, therefore the tomorrow sensor knows to label itself friday, and the one after that saturday - and then change based on what today is- something like X+2 days =Saturday.

Or would it possible in a banner card of some kind, if I could template that into a banner or something similar I could just use stack-in cards and glance cards to get what I want.

I would be amenable to creating some senors that pop out the correct day and using that sensor as the main entity in the multiple entity row.

Any suggestions?

Posts: 1

Participants: 1

Read full topic

@mbaran5 wrote:

So, looking at using Automation Triggers and decided to use sun.sun and elevation vs. a static offset for Sunset.

My understanding of this is that it should trigger once when used as a trigger, but essentially I see this execute all night long every time the sun’s elevation changes.

image830×192 24.7 KB

If I decide to turn that device off early (say to go to bed) this seems to trigger again and turn it back on. Is there a better way to trigger this (code below)

Thanks!

- id: '1589757784702'
  alias: Turn on Porch at Sunset
  description: ''
  trigger:
  - below: '-4.2'
    entity_id: sun.sun
    platform: numeric_state
    value_template: '{{ state_attr(''sun.sun'', ''elevation'') }}'
  condition: []
  action:
  - device_id: 6bfbcd45081a45038ce87b14dc7569c4
    domain: light
    entity_id: light.porch
    type: turn_on

Posts: 1

Participants: 1

Read full topic

@Liese wrote:

Hi, just as information for other beginners.
Did I miss an instruction in the release info?
In 0.110 the pending_time has to be changed to arming_time otherwise the alarm panel entity is broken:

alarm_control_panel:
  - platform: manual
    name: Home Alarm
    code: xxxx
    arming_time: 20
    delay_time: 20
    trigger_time: 4
    disarmed:
      trigger_time: 0
    armed_home:
      arming_time: 0
      delay_time: 0

Posts: 1

Participants: 1

Read full topic

@DavidFW1960 wrote:

I currently use the custom config-template card to produce this:

Now there are a few custom cards that will produce columns and I can probably even use those with attributes. But I have not seen anything that will let me also have an icon. In the config template I have a calculation based on the RSSI to graphically show the signal strength.

What is annoying me about this card is I have to randomly work out the right number of spaces between elements and because of the proportional font used, the numbers in the rows don’t line up 100% properly.

Can anyone think of a way I can make these line up?

Posts: 5

Participants: 3

Read full topic

@peternest wrote:

Hi All,
I just upgraded a small instance of HA with very little on it to .110.

It has Garbage Collection (from bruxy70 - legend) and it still appears to be functional however the garbage bin icons have disappeared. Have upgreaded HACs , Garbage Collection and GC Card (which is practicaly the only thing on the box.

Has anyone esle come across this.

Cheers

Posts: 6

Participants: 3

Read full topic

@DSGMM1 wrote:

Just upgraded to 0.110.0 (without fully reading the release notes -my bad) and my whole zigbee integration went belly up. Gone are my Silicon Labs EZSP coordinator and all of my zigbee devices (all of my zigbee devices are light bulbs). I have done a little digging and discovered two things:

a) The zha integration has been demoted out of configuration.yaml; now it has to be brought in through GUI (nice for novices and first timers moving forward) but not so nice for users who have it setup and v 0.110 upgrade brings a breaking change to ZHA.

b) v 0.110 now supports python 3.8 and I’m suspecting this has to do with some of the errors I see in the home-assistant.log file:

2020-05-20 19:04:22 ERROR (MainThread) [zigpy.application] Couldn't start application
2020-05-20 19:04:22 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry /dev/ttyAMA0 for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 217, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 100, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 141, in async_initialize
    app_config, auto_form=True, start_radio=True
  File "/usr/local/lib/python3.7/site-packages/zigpy/application.py", line 65, in new
    await app.startup(auto_form)
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 138, in startup
    await self.initialize()
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 88, in initialize
    await self._cfg(t.EzspConfigId[config], value)
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 230, in _cfg
    assert v[0] == t.EmberStatus.SUCCESS  # TODO: Better check
AssertionError
2020-05-20 19:04:22 DEBUG (bellows.thread_0) [bellows.uart] Closed serial connection

Any clues, anybody?

Thank you!

PS I had wipe and restore back to v 0.109.6; first time I had to do that, an odyssey but got everything back as it was.

Posts: 1

Participants: 1

Read full topic

@tomasi wrote:

Hello, I have some issues related to Rflink integration. I have no idea what I am doing wrong. First I did not download any files, components, etc. I just put this code into my configuration.yaml:

rflink:
  port: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
  wait_for_ack: false
  reconnect_interval: 20
sensor:
  - platform: rflink
    automatic_add: true
    devices:
      'auriolv3_1701_temp':
        sensor_type: temperature
        unit_of_measurement: "°C"
        name: "Temperature 1"
      'auriolv3_1701_hum':
        sensor_type: humidity
        name: "Humidity 1"
      'auriolv3_c103_temp':
        sensor_type: temperature
        unit_of_measurement: "°C"
        name: "Temperature 2"
      'auriolv3_c103_hum':
        sensor_type: humidity
        name: "Humidity 2"
logger:
  default: info
  logs:
    rflink: debug
    homeassistant.components.rflink: debug

Additionally this is what I can find in my logs:

2020-05-21 09:40:31 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_1701_hum', 'sensor': 'humidity', 'value': 50, 'unit': '%'}
2020-05-21 09:40:31 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_1701_hum', 'sensor': 'humidity', 'value': 50, 'unit': '%'}
2020-05-21 09:40:31 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_1701_update_time', 'sensor': 'update_time', 'value': 1590046832, 'unit': 's'}
2020-05-21 09:40:31 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_1701_update_time', 'sensor': 'update_time', 'value': 1590046832, 'unit': 's'}
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] received data: 20;FD;Auriol V3;ID=C103;TEMP=00a
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] received data: f;HUM=44;
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] got packet: 20;FD;Auriol V3;ID=C103;TEMP=00af;HUM=44;
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'auriol v3', 'id': 'c103', 'temperature': 17.5, 'temperature_unit': '°C', 'humidity': 44, 'humidity_unit': '%'}
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_c103_temp', 'sensor': 'temperature', 'value': 17.5, 'unit': '°C'}
2020-05-21 09:41:19 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_c103_temp', 'sensor': 'temperature', 'value': 17.5, 'unit': '°C'}
2020-05-21 09:41:19 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: []
2020-05-21 09:41:19 DEBUG (MainThread) [homeassistant.components.rflink] device_id not known and automatic add disabled
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_c103_hum', 'sensor': 'humidity', 'value': 44, 'unit': '%'}
2020-05-21 09:41:19 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_c103_hum', 'sensor': 'humidity', 'value': 44, 'unit': '%'}
2020-05-21 09:41:19 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_c103_update_time', 'sensor': 'update_time', 'value': 1590046879, 'unit': 's'}
2020-05-21 09:41:19 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_c103_update_time', 'sensor': 'update_time', 'value': 1590046879, 'unit': 's'}
2020-05-21 09:41:40 DEBUG (MainThread) [rflink.protocol] received data: 20;FE;Auriol V3;ID=1701;TEMP=00a
2020-05-21 09:41:40 DEBUG (MainThread) [rflink.protocol] received data: a;HUM=50;
2020-05-21 09:41:40 DEBUG (MainThread) [rflink.protocol] got packet: 20;FE;Auriol V3;ID=1701;TEMP=00aa;HUM=50;
2020-05-21 09:41:40 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'auriol v3', 'id': '1701', 'temperature': 17.0, 'temperature_unit': '°C', 'humidity': 50, 'humidity_unit': '%'}
2020-05-21 09:41:40 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'auriolv3_1701_temp', 'sensor': 'temperature', 'value': 17.0, 'unit': '°C'}
2020-05-21 09:41:40 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'auriolv3_1701_temp', 'sensor': 'temperature', 'value': 17.0, 'unit': '°C'}
2020-05-21 09:41:40 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: []
2020-05-21 09:41:40 DEBUG (MainThread) [homeassistant.components.rflink] device_id not known and automatic add disabled

It looks like entity is not being created. What am I doing wrong?

Posts: 1

Participants: 1

Read full topic

@leotantantan wrote:

Hi, I’m new in HA, I just setup everthing via DrZz’s guide on youtube.
I’ve flash sonoff sv to latest tasmota firmware 8.3.1, then set GPIO14 to switch2(10)，GPIO 4 to Relay2 (22) and put following commands in tamota console:

• Switchretain 1
• Powerretain 1
• switchtopic2 garagestate
• switchmode1 0
• switchmode2 2
  
  Screen Shot 2020-05-21 at 18.11.32750×1012 69.5 KB

I can see the status changes of reed switch in console

18:12:11 MQT: cmnd/garagestate/POWER2 = ON (retained)
18:12:13 MQT: cmnd/garagestate/POWER2 = OFF (retained)

But the two arrows do not turn to grey when I test the reed switch, they are always black
I do not know where I’m wrong, could anyone help me? please.

Screen Shot 2020-05-21 at 18.07.521018×180 8.74 KB

It works when I click any arrows, just can not see the status
My configuaration in HA

cover:
  - platform: mqtt
    name: garage
    state_topic: cmnd/garagestate/POWER2
    command_topic: cmnd/sonoff/POWER
    payload_open: ON
    payload_close: ON
    payload_stop: ON
    state_open: ON
    state_closed: OFF
    optimistic: false

Posts: 1

Participants: 1

Read full topic

@tescophil wrote:

OK, going a bit mad here…, updated to 0.110.0 which breaks the icon_color capability provided by custom_ui. There is however a fix for this here : https://github.com/home-assistant/frontend/issues/5892 which involves just changing one line in one file : state-card-custom-ui.html

So, on my HASSIO install, this file is located in /root/config/www/custom_ui

I change the file, reboot the system, and no matter what I do, I still get the original unmodified file returned to me by HA. So if I manually navigate to :

https://myhainstall:8123/local/custom_ui/state-card-custom-ui.html

Then view the source for this page, I see the old unmodified version of the file.

If I then change the name of the file to orig-state-card-custom-ui.html then I get a 404: Not Found error when I refresh the URL as expected…

Now the interesting bit…, If I then create a new state-card-custom-ui.html file just containing some plain text like Hi Phil then when I refresh the URL I get the OLD state-card-custom-ui.html back again. Where the hell is this coming from…, it does not exist anywhere on the system.

I’ve cleared the cache on my browser, cleared the cache then restarted my machine, I’ve restarted the HA server, then completely shut down and restarted the host machine… and I still get the original unmodified state-card-custom-ui.html back to my browser, even though the file on the server just contains the text Hello Phil

Can someone please point out where I’m going wrong here…, all the posts on this simply say to modify the file and it will fix the icon color problem…

Posts: 2

Participants: 1

Read full topic