I’m losing my mind over this and can’t seem to find a definitive answer.

I have created an image for each person and saved in the www folder. I have managed to also change entity_picture for each person in customisation to target the image in www.

I know this has been done correctly because the images are showing in buttons in the default overview.

What I need to figure out is how to create an entity card and change the default hass:account icon to show the person’s image instead.

Can someone please help?

1 post - 1 participant

Read full topic

Is there a way to get them to go back to the old behavior that I was seeing in v0.9.6 (I think) where they only appeared in the dashboard when there were active - i.e. not in the idle state.

2 posts - 2 participants

Read full topic

Hello everyone,
I now have an automation that checks every hour two parameters: humidity and temperature.
If the temperature is <25°C and humidity>60% a fan connected to a smart switch starts, else not.
What I would like to do is add another condition so that every hour it checks, if temp<25 & hum>60 OR if hum>75 it starts.
How could i do it?

This is my actual setup:

#Controllo Umidità ogni 60 minuti
- id: Controllo_Umidita
  alias: Controllo Ventola Ogni 60 Minuti
  description: 'Condizioni: umidità>60% && Temp<25'
  trigger:
  - hours: '/1'
    platform: time_pattern
  condition:
  - above: '60'
    condition: numeric_state
    entity_id: sensor.umidita_balconcino
    #value_template: "{{states('sensor.umidita_balconcino')}}"
  - below: '25'
    condition: numeric_state
    entity_id: sensor.temperatura_balconcino
    #value_template: "{{states('sensor.temperatura_balconcino')}}"
  action:
  - service: notify.christian
    data_template:
      title: '*Balconcino*'
      message: Ventola attivata, temperatura {{states('sensor.temperatura_balconcino')}}°C,
        umidità {{states('sensor.umidita_balconcino')}}%
  - device_id: f4fbd3f3debf4c9f9c36db094121d525
    domain: switch
    entity_id: switch.06673331bcddc294d6ec
    type: turn_on
  - delay: '0:10:00'
  - device_id: f4fbd3f3debf4c9f9c36db094121d525
    domain: switch
    entity_id: switch.06673331bcddc294d6ec
    type: turn_off
  mode: single
  

2 posts - 2 participants

Read full topic

Hi Guys, hopefully someone can help me with a problem.
I want to trigger a notification that the alarm system is arming. At the beginning of the transition from “disarmed” to “armed_home”.

I think I can do it based on the trigger_to state. I know the alarm entity changes its “to” state on trigger, the actual entity state does not change until the arming_time has expired.

But attempts so far have failed.

Here is my current attempt,

 - alias: Notify alarm is arming 
    trigger: 
      - platform: state
        entity_id: alarm_control_panel.alarm
    condition:
      - condition: template
        value_template: >
          {{ trigger.to_state.state == 'armed_home' }}
    action:
      - service: script.sonos_say
        data:
          sonos_entity: media_player.living_room_sonos 
          volume: 0.2
          message: 'Attention, the alarm is arming you have 30 seconds to leave'
          delay: '00:00:05'

1 post - 1 participant

Read full topic

lock.set_usercode is no longer working for me. This used to work but I didnt touch it for a while. Went back to it and even attempting to use the built in dev service call it makes the call but when I look in the ozw log file I never see the zwave call to the node being made so its not even making it to the zwave stack.

Anyone else run into this? All my other zwave devices are working.

1 post - 1 participant

Read full topic

Hi,
I’ve tried a couple of times to get MQTT switches (Tasmota) to properly utilize the RETAIN flag and have correct status upon HA reboot. But no matter what it seems I must wait the 300 seconds for Tasmota to send the tele update. I have properly set the PowerRetain 1 option from the console, and if I subscribe using eg mosquitto_sub to tasmota/stat/POWER i get the ON status immediately so the RETAIN does seem to work and is set on the broker (mosquitto, not the HA integrated)

But when I look at the mqtt config for the device in HA, it doesn’t appear to be actually subscribing to the tasmota/stat/POWER topic, only the tasmota/tele topic?

Is there some update or config change needed to get the proper stat subscription to HA?

1 post - 1 participant

Read full topic

Hello people, a question is this:

€ 18,10 52％ Off | Tuya Zigbee 3.0 Smart Radiator Actuator Thermostaat Programmeerbare Radiator Valve Temperatuur Controller Voice Control Alexa Google

Is this product connection with HA with the intergrations?
I will buy this product for my home!

Thanks for helping me!

1 post - 1 participant

Read full topic

Hope some one can help me with my little issue. I have an automation that triggers at certain time which then sends me a notification with the COVID numbers. Recently I notice that it fires twice, not sure but I think it’s after I updated to 0.114. Last night I updated to 0.114.4 but issue persists.

- id: '1583446607782'
  alias: Check for COVID-19
  description: ''
  trigger:
  - at: '20:00:00'
    platform: time
  condition: []
  action:
  - data_template:
      message: Today numbers...
      title: Daily COVID-19 update
    service: notify.mobile_app_oneplus_a6013
  initial_state: 'on'
  mode: single

3 posts - 2 participants

Read full topic

Hello Everyone. I was wondering if someone could help me finish this code. Im a little stuck. I need to write a value to a modbus register on my home battery system I have built. Postive number tell it to charge and negative numers to discharge. Problem is I cannot write negative numbers easily. Positive number are fine no issue. I have to write my values via the 2 compliment method. The scale is 0-32768 are postive and 65536 - 32768 are negative numbers. For example if I wish for my battery to discharge by -100W its 65536 - 100 = 65436 = -100.

All I want my statement to say. If the houseload is between 0 and 3000W then write that value to the template output as positive numbers are not an issue. However IF the house load is between -1 to -3000W then 65536 + (-house load). If its anything else the write + 40W. This the code I have so far.

• platform: template
  sensors:
  grid_step:
  friendly_name: “Grid Setpoint to Battery”
  value_template: >-
  {% if states(‘house load’) | float > 0 and states(‘house load’) | float < 3000 %}
  {{states(’???’) | int}}
  {% elif states(‘house load’) | float > -1 and states(‘house load’) | float < -3000 %}
  {{ 65536 + states(’-???’) | int}}
  {% else %}
  40
  {% endif %}

I think im on the right track but im a novice and writing code.

Any help would be much appreciated.

Thanks

Gareth

1 post - 1 participant

Read full topic

Hi everyone,

New installation of HassOS 4.12 on Raspberry Pi 4.

I have added multiple integrations, but when I add a new UI, select an unused entitiy and ‘+’ to add a card I simply get the ‘Choose a view’ popup with the ‘x’ but no options. I would normally see all of the cards - i.e. Weather, History Graph, etc.

I have tried re-imaging, but this does not resolve the issue.

The only thing that has changed (that I am aware of) is I am now installing the recommended 32 bit image, versus a 64 bit image which would have been downloaded a few weeks ago (no version number available, unfortunately).

Thanks for your help!

Thanks,
Peter

1 post - 1 participant

Read full topic

Hey there! I am wondering if I can make a script which would send to all members a message which consists who fired that script?

My goal is to create a button (for ios app, 3d touch without even opening the app) which would send a critical message like ‘smth is wrong, call me back, {name, who triggered the script}’

I do not know if I can check who fired a script and put that name in the message. Would love to here your suggestions

1 post - 1 participant

Read full topic

I am fairly new to HA, been using it for about 2 months. I have several integrations installed and some HACS integrations. Every video I watch that explains how to do something, refers to modifying or adding code to the config.yaml. However, my config file only contains what I have manually added. Should installed integrations automatically add lines to the config.yaml file?

3 posts - 3 participants

Read full topic

I’m using several Amazon Echoes in my house and had them talking to me via automations to warn me of weather conditions, open doors and so on. This has been working for months but stopped recently. I didnt change anything to the configuration of the system. The only thing I remember is that my HassOs (RPI4 2GB 32bit) install died due to the v4.8 host update so I had to go back to a working backup a few weeks ago. Did all updates since, everything works fine.

• removed alexa integration, then
• removed alexa media player from HACS, reboots after both actions
• deleted pickle files
• reinstalled everything

The echoes all show up with their media player entities, however shuffle switches, next_reminder sensors and so on are shown as unavailable. If I put the media players in a lovelace card, I cant change i.e. the volume which always worked fine. It doesnt show media being played (like spotify). TTS doesnt work.
The logs are empty. Searching the forums I found some stuff but nothing helped. The only thing I havent tried yet is changing the region url but I remember it asking me once which server to use (I am in Germany). When I tried amazon.de I couldnt get it to install properly, the last install didnt even ask.

I’m helpless here guys. It always worked fine and the only thing I remember is restoring the system after a bad update. What can I do ?

1 post - 1 participant

Read full topic

I have installed HACS and found an integration for a trakt media card that would let me know upcoming shows. I’ve copied the trakt folder from github into my custom components folder. i’ve setup the api at https://trakt.tv/oauth/applications. if i enter just my https:/// and try to authorise it takes me to my home assistant log on screen. i login and then search for trakt in the integrations. It asks for the id and secret but then displays ‘oath error’ ‘the requested redirect uri doesnt match client redirect uri’
if in the trakt api setup i enter https:///auth/external/callback then as soon is I try to authorise i get the following error. Missing code or state parameter in https:///auth/external/callback?code=75e3bfxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxecaf7

1 post - 1 participant

Read full topic

I used to be able to have my alexa devices seen as media players and could have them make announcements if certain things happened such as phone battery dropped below 20%. this recently stoppped working. i decided to do a full reinstall of hassio due to other errors that were occuring.
I tried to follow this https://peyanski.com/alexa-and-home-assistant/ asit seemed like a good method to integrate the alexa devices but the alexa devices still dont appear in hassio.
Is this something that has been stopped by Amazon and if so how else could I have things announced.

1 post - 1 participant

Read full topic

This is going to be complicated and a challenge.
I want to build a nice interface for this nodered flow: github.com/dvbit/ICL
So let me describe what I would ideally to do.

Square button.

• Icon representing a bulb at the center: colored with the current brightness
• smaller icons on top left and right: left the running man of movement sensors, right the switch icon. Icon animated if the corresponding automation is running . Greyed out if the corresponding animation is overridden. Not displayed if the corresponding automation is not enabled
• below across the button a dynamic progress bar displaying the current status of the active countdown (either movement sensor automation or manual switch automation can be on at any given time) .
  a second bar with threshold illuminance and current illuminance

here a little sketch
I am currently fighting custom button card

1 post - 1 participant

Read full topic

Tried to configure a Sonoff Mini with Tasmota-lite with the following config:

switch:
  - platform: mqtt
     name: "LuzLucas"
     state_topic: "stat/LuzLucas/POWER"
     command_topic: "cmnd/LuzLucas/POWER"
     availability_topic: "tele/LuzLucas/LWT"
     qos: 1
     payload_on: "ON"
     payload_off: "OFF" 
     retain: true

I can listen and publish to the topic in the MQTT settings but the Switch I’m trying to add does not work, no matter what I do

image603×895 27.9 KB

Any suggestions?

2 posts - 2 participants

Read full topic

My RPi4 with a Supervised Install just got very sluggish so I looked in Portainer and saw that CPU Usage of the InfluxDB Container was North of 150%.

I updated to the latest add-on version but it didn’t change a thing.
From what I can see with htop there are still multiple influxdb processes running that eat up way more CPU% than they should.

These are the log entries if somebody understands what they mean and can give me any direction how I can fix this - other than just turning the add-on off permanently:

[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] 00-banner.sh: executing... ,
,
-----------------------------------------------------------,
 Add-on: InfluxDB,
 Scalable datastore for metrics, events, and real-time analytics,
-----------------------------------------------------------,
 Add-on version: 3.7.5,
 You are running the latest version of this add-on.,
 System: Raspbian GNU/Linux 10 (buster)  (armv7 / raspberrypi4),
 Home Assistant Core: 0.114.4,
 Home Assistant Supervisor: 235,
-----------------------------------------------------------,
 Please, share the above information when looking for help,
 or support in, e.g., GitHub, forums or the Discord chat.,
-----------------------------------------------------------,
[cont-init.d] 00-banner.sh: exited 0.,
[cont-init.d] 01-log-level.sh: executing... ,
[cont-init.d] 01-log-level.sh: exited 0.,
[cont-init.d] create-users.sh: executing... ,
[cont-init.d] create-users.sh: exited 0.,
[cont-init.d] influxdb.sh: executing... ,
[cont-init.d] influxdb.sh: exited 0.,
[cont-init.d] kapacitor.sh: executing... ,
[cont-init.d] kapacitor.sh: exited 0.,
[cont-init.d] nginx.sh: executing... ,
[cont-init.d] nginx.sh: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
[18:51:56] INFO: Chronograf is waiting until InfluxDB is available...,
[18:51:56] INFO: Kapacitor is waiting until InfluxDB is available...,
[18:51:56] INFO: Starting the InfluxDB...,
[httpd] 127.0.0.1 - chronograf [28/Aug/2020:18:52:21 -0700] "GET /ping HTTP/1.1" 204 0 "-" "InfluxDBShell/1.8.2" 473cb933-e99a-11ea-8001-0242ac1e2102 254,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:21 -0700] "GET /ping HTTP/1.1" 204 0 "-" "InfluxDBShell/1.8.2" 473ebbbb-e99a-11ea-8003-0242ac1e2102 60,
[httpd] 127.0.0.1 - chronograf [28/Aug/2020:18:52:21 -0700] "POST /query?chunked=true&db=&epoch=ns&q=SHOW+DATABASES HTTP/1.1" 200 121 "-" "InfluxDBShell/1.8.2" 473cfed1-e99a-11ea-8002-0242ac1e2102 156245,
[18:52:21] INFO: Starting Chronograf...,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:21 -0700] "POST /query?chunked=true&db=&epoch=ns&q=SHOW+DATABASES HTTP/1.1" 200 121 "-" "InfluxDBShell/1.8.2" 473ee6bd-e99a-11ea-8004-0242ac1e2102 166259,
[18:52:21] INFO: Starting the Kapacitor,
,
'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::,
 ##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:,
 ##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:,
 #####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::,
 ##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::,
 ##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::,
 ##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:,
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::,
,
2020/08/28 18:52:22 Using configuration at: /etc/kapacitor/kapacitor.conf,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:22 -0700] "GET /ping HTTP/1.1" 204 0 "-" "KapacitorInfluxDBClient" 478da706-e99a-11ea-8005-0242ac1e2102 82,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:22 -0700] "POST /query?db=&q=SHOW+DATABASES HTTP/1.1" 200 121 "-" "KapacitorInfluxDBClient" 478e0f96-e99a-11ea-8006-0242ac1e2102 3912,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+_internal HTTP/1.1" 200 153 "-" "KapacitorInfluxDBClient" 478f05a1-e99a-11ea-8007-0242ac1e2102 2559,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+homeassistant HTTP/1.1" 200 149 "-" "KapacitorInfluxDBClient" 478f9d6c-e99a-11ea-8008-0242ac1e2102 2950,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:52:22 -0700] "POST /query?db=&q=SHOW+SUBSCRIPTIONS HTTP/1.1" 200 225 "-" "KapacitorInfluxDBClient" 479037d8-e99a-11ea-8009-0242ac1e2102 2178,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 48cfd7ee-e99a-11ea-800a-0242ac1e2102 202373,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 48fb5b45-e99a-11ea-800b-0242ac1e2102 17467,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 4905d252-e99a-11ea-800c-0242ac1e2102 14726,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 490e1ede-e99a-11ea-800d-0242ac1e2102 79973,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 4920820f-e99a-11ea-800e-0242ac1e2102 12535,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:24 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 49288188-e99a-11ea-800f-0242ac1e2102 16162,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:25 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 4930fc66-e99a-11ea-8010-0242ac1e2102 11626,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:27 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 4a9845f9-e99a-11ea-8011-0242ac1e2102 30654,
time="2020-08-28T18:52:40-07:00" level=info msg="Reporting usage stats" component=usage freq=24h reporting_addr="https://usage.influxdata.com" stats="os,arch,version,cluster_id,uptime",
time="2020-08-28T18:52:40-07:00" level=info msg="Serving chronograf at http://127.0.0.1:8889" component=server,
[18:52:41] INFO: Starting NGinx...,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:45 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 55a83e75-e99a-11ea-8012-0242ac1e2102 15731,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:52:58 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 5d1165f1-e99a-11ea-8013-0242ac1e2102 10715,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:02 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 5f77a1c8-e99a-11ea-8014-0242ac1e2102 8835,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:14 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 66989351-e99a-11ea-8015-0242ac1e2102 10105,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:16 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 67dbc729-e99a-11ea-8016-0242ac1e2102 13228,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:53:22 -0700] "GET /ping HTTP/1.1" 204 0 "-" "KapacitorInfluxDBClient" 6b504b75-e99a-11ea-8017-0242ac1e2102 74,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:53:22 -0700] "POST /query?db=&q=SHOW+DATABASES HTTP/1.1" 200 121 "-" "KapacitorInfluxDBClient" 6b5079bc-e99a-11ea-8018-0242ac1e2102 2760,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:53:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+_internal HTTP/1.1" 200 153 "-" "KapacitorInfluxDBClient" 6b511a5d-e99a-11ea-8019-0242ac1e2102 2388,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:53:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+homeassistant HTTP/1.1" 200 149 "-" "KapacitorInfluxDBClient" 6b51a8fa-e99a-11ea-801a-0242ac1e2102 1217,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:53:22 -0700] "POST /query?db=&q=SHOW+SUBSCRIPTIONS HTTP/1.1" 200 225 "-" "KapacitorInfluxDBClient" 6b522dd6-e99a-11ea-801b-0242ac1e2102 1342,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:28 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 6ef5cc75-e99a-11ea-801c-0242ac1e2102 30968,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:30 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 7008a3b4-e99a-11ea-801d-0242ac1e2102 7636,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:32 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 715ce12c-e99a-11ea-801e-0242ac1e2102 5578,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:34 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 729085ea-e99a-11ea-801f-0242ac1e2102 7990,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:39 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 754e8660-e99a-11ea-8020-0242ac1e2102 30511,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:41 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 76845ff4-e99a-11ea-8021-0242ac1e2102 8873,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:53:53 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 7daa6ebc-e99a-11ea-8022-0242ac1e2102 23113,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:05 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 84ceff83-e99a-11ea-8023-0242ac1e2102 119911,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:09 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 87319386-e99a-11ea-8024-0242ac1e2102 6694,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:11 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 8865ce8d-e99a-11ea-8025-0242ac1e2102 4810,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:15 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 8ac9b859-e99a-11ea-8026-0242ac1e2102 4796,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:21 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 8e527933-e99a-11ea-8027-0242ac1e2102 4258,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:54:22 -0700] "GET /ping HTTP/1.1" 204 0 "-" "KapacitorInfluxDBClient" 8f138722-e99a-11ea-8028-0242ac1e2102 489,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:54:22 -0700] "POST /query?db=&q=SHOW+DATABASES HTTP/1.1" 200 121 "-" "KapacitorInfluxDBClient" 8f13d88e-e99a-11ea-8029-0242ac1e2102 1725,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:54:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+_internal HTTP/1.1" 200 153 "-" "KapacitorInfluxDBClient" 8f14545a-e99a-11ea-802a-0242ac1e2102 1681,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:54:22 -0700] "POST /query?db=&q=SHOW+RETENTION+POLICIES+ON+homeassistant HTTP/1.1" 200 149 "-" "KapacitorInfluxDBClient" 8f14cdcd-e99a-11ea-802b-0242ac1e2102 1101,
[httpd] 127.0.0.1 - kapacitor [28/Aug/2020:18:54:22 -0700] "POST /query?db=&q=SHOW+SUBSCRIPTIONS HTTP/1.1" 200 225 "-" "KapacitorInfluxDBClient" 8f1545cd-e99a-11ea-802c-0242ac1e2102 12760,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:28 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 92a5ff8c-e99a-11ea-802d-0242ac1e2102 10691,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:39 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 99237b6b-e99a-11ea-802e-0242ac1e2102 190865,
[httpd] 172.30.32.1 - homeassistant [28/Aug/2020:18:54:45 -0700] "POST /write?db=homeassistant HTTP/1.1" 204 0 "-" "python-requests/2.24.0" 9cbb0139-e99a-11ea-802f-0242ac1e2102 4689,

1 post - 1 participant

Read full topic

Hoping for some Zigbee/ZHA guru help

I have acquired a conbeeII stick and am starting to migrate some devices to the new network from my Xiaomi & Ikea Zigbee networks.

I am using the baked in Zigbee (ZHA) integration in Homeassistant. Running Homeassistant container in docker on my NAS. Homeassistant V114.4 (had same behaviour in v113). Added zigbee devices have applied appropriate quirks and are identified in the integration.

I have added an Ikea 5 way remote (E1810) and a xiaomi lumi plug (ZNCZ02LM) to the ZHA network and now any time I press the toggle button on the remote, my plug will toggle. I do not want this behaviour and have not done anything to select it (to my knowledge).

I am assuming this is in the direct Zigbee worked using the magic of groups and/or clusters.

Any tips on how to diagnose and adjust this behavior on the native Zigbee network?

Phil

1 post - 1 participant

Read full topic

Hello there!
I have a TP-Link switch and I enabled SNMP v3 with password on it, but I have no idea how to get what’s called OID.
I’d like to get cpu, mem and bandwidth sage from it and maybe the ability to activate/deactivate ports on it (and maybe bandwidth per port?).
Or maybe I understood that wrong and it’s not possible?

Would that be possible? How I can I get the OID for those? I think the rest of the HA integration will be easy (I hope), I just have no idea how to get those freaking numbers XD
Thinks folks!

1 post - 1 participant

Read full topic