@dyfcom wrote:

Hello,

I want to use a Wemos D1 mini with tasmota and a button to control other devices.

The button sends over MQTT ON or OFF.
Did I need a binary_sensor, switch or a sensor?

This is my current config for the button in my configuration.yaml:

binary_sensor:
#cap-button
  - platform: mqtt
    name: "CapButton"
    state_topic: "stat/WemosD1/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    icon: 'mdi:electric-switch'
    retain: false

In my Automation I can’t see the Button under devices. Same with all my other MQTT-Devices except Devices from zigbee2mqtt. The zigbee2mqtt devices are listed under config->devices and config->integration->MQTT:configuration.yaml

MQTT-devices864×261 14.4 KB

The binary_sensor is showing in Automation under Status, but there are only option where I can use from-to values.

This is my MQTT Integration in configuration.yaml:

#MQTT Integration
mqtt:
  broker: 192.168.0.9
  username: #
  password: #
  discovery: true
  discovery_prefix: homeassistant

How can I add my MQTT-Devices into config->devices? I read that, the devices need an unique_id, but this didn’t work also.

Greetings

Posts: 2

Participants: 1

Read full topic

@ATWindsor wrote:

I get the following error in the log:

Timed out when connecting to Tibber:

10:22 PM main.py (ERROR)

Setup of tibber is taking over 10 seconds.

10:22 PM main.py (WARNING)

I tried replacing the access token, and get the same message. I have tried accessing the info through the Tibber-app, and that works fine. Any tips? Could it be some kind of firewall-problem?

EDIT; turns out the integration actually work, I do get the info, despite of the error. But why has this error turned up now?

Posts: 1

Participants: 1

Read full topic

@coolmonkey5 wrote:

Everyone,

I am trying to embed weather information next to the date as shown in the picture below using the darksky_summary sensor which works great although I cannot to find a way to change the icon color, can anybody point me in the right direction here?

darksky_snap981×189 15.6 KB

I have googled and read all possible threads on how to use sensor templates but this does not seem to apply to this case, am I missing something?

Thanks in advance

Posts: 1

Participants: 1

Read full topic

@mikestreety wrote:

This is starting to annoy me.

I wanted a simple automation that runs a script at a set time. The script turns on some lights. I have made this automation with the following trigger:

Screenshot_20200121-2205051748×2048 309 KB

But yet nothing happens!

If I click the “execute” button, it turns on the lights as expected, but waiting for the time reveals nothing.

1. How do I know the exact time my Home Assistant thinks it currently is? I don’t know whether it might be not waiting long enough
2. Is there a way of knowing if it thinks it triggered it?
3. Should this toggle be on or off? I figured on, meaning you can set up automations but temporarily disable them
   
   Screenshot_20200121-2211262048×1658 243 KB

Any help and advice would be hugely appreciated. I’m very close to sacking this all off

Posts: 12

Participants: 4

Read full topic

@hal.lol wrote:

Hi,
I am trying to push my utility meter (Linky) daily value to Influxdb. This is fairly straightforward to do: I just installed the Linky integration, and configured Influxdb like this:

influxdb:
  host: myhost
  port: 8086
  max_retries: 3
  include:
    entities:
       - entity.sensor.linky_yesterday

This works fine… until HA is restarted. Every time HA starts, it adds the latest value to Influxdb. Because the values are added with different timestamps, they are not handled as duplicated by Influxdb.
So I can end up with something like this:

time                attribution_str         domain entity_id       friendly_name_str icon_str  time_str    username_str            value
----                ---------------         ------ ---------       ----------------- --------  --------    ------------            -----
1579465004677655040 Data provided by Enedis sensor linky_yesterday Linky yesterday   mdi:flash 18 Jan 2020 email@myprovider.com 55.298
1579466123163844096 Data provided by Enedis sensor linky_yesterday Linky yesterday   mdi:flash 18 Jan 2020 email@myprovider.com 55.298

Is there any way to avoid this, by making sure that HA will send the value to Influxdb only once per day?

Thanks.

Posts: 1

Participants: 1

Read full topic

@ptdalen wrote:

I have an automation that lets me know if one of my three locks did not lock as expected

        {% set unlocked = states | selectattr('entity_id', 'in', state_attr('group.all_locks','entity_id')) | selectattr('state','eq','unlocked') | map(attribute='name') | join(', ') %}
          The following locks failed to lock: {{ unlocked }}.  This was the second attempt.  Please lock using the app.

Any recommendations on best way to update this without creating a group.all_locks?

Posts: 3

Participants: 3

Read full topic

@Nordic wrote:

I recently switched over to ZHA from deCONZ. Zigbee devices all seem to be working great, however, I noticed my log is riddled with errors like the following:

2020-01-20 16:21:25 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 10 req id frame: 0xd0
2020-01-20 16:21:25 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 12 req id frame: 0xd0
2020-01-20 16:21:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 14 req id frame: 0xd0
2020-01-20 16:21:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 18 req id frame: 0xd0
2020-01-20 16:21:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 22 req id frame: 0xd0
2020-01-20 16:21:28 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 98 req id frame: 0xe9
2020-01-20 16:21:28 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 100 req id frame: 0xe9
2020-01-20 16:21:35 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 8 req id frame: 0xd0

Anyone seen these errors and know what they are?

Posts: 1

Participants: 1

Read full topic

@crispy wrote:

My setup requires DNSmasq, as my router does not support nat loopback. Previously it has worked well, but now it appears to no longer work (will randomly go out - worked fine this morning, now it doesn’t). I’m not getting any error messages on the add-on page or within HA’s logs. I believe since it is unresponsive, my devices now also ignore it as the preferred DNS server.

Results from nslookup using my HA instance with DNSmasq turned on. I believe this should return my local IP address, correct?

nslookup my-ha-domain.duckdns.org 192.168.xx.xxx
;; connection timed out; no servers could be reached

I can access HA fine via IP, but no longer via domain. The app doesn’t like this however, and will no longer connect from my home network. Any ideas why this is being problematic, or where to start debugging?

Posts: 1

Participants: 1

Read full topic

@mtnaut3 wrote:

homekit does not see aeotec nanomote z-wave buttons
Homekit does see my other z-wave devices.
I came across some vague notes to ensure the command_class is set such that Homekit recognizes it.
The nanomote has several command classes, some contain the word ‘switch’.
Is there an additional command_class section that needs to be manually added to the nanomote config?
My main yaml config contains only:
homekit:
i.e. no filters to confuse things.
Is the nanomote capable of being exported to Homekit?

Posts: 7

Participants: 3

Read full topic

@mynameisdaniel wrote:

Trying to interface with Home Assistant from a proprietary system and not able to get it to handle POST commands. This system doesn’t support tools such as cURL, so this content is being sent through an open TCP port raw.

My header seems fine as it authenticates and GET requests work fine. Different errors when the token is changed/missing. It’s only POST where I’m having issues with the JSON data and despite trying every variation I can think of, it’s still failing.

What I’m sending to Home Assistant:
POST /api/states/binary_sensor.test HTTP/1.1$0D$0AHost: 10.220.88.81$0D$0AAccept: application/json$0D$0AConnection: close$0D$0AContent-Type: application/json$0D$0AAuthorization: Bearer [TOKEN]$0D$0A$0D$0A{"state":"0","attributes":{"source":"HDMI"}}

What I’m receiving back from Home Assistant:
HTTP/1.1 400 Bad Request$0D$0AContent-Type: application/json$0D$0AContent-Length: 38$0D$0ADate: Wed, 22 Jan 2020 00:01:02 GMT$0D$0AServer: Python/3.7 aiohttp/3.6.1$0D$0AConnection: close$0D$0A$0D$0A{"message": "Invalid JSON specified."}

If anyone has ideas on what’s failing here, or how I can troubleshoot further, that’d be appreciated!

As far as I can see I’m formatting things in a way that should work, and match what I’m getting back.

Posts: 1

Participants: 1

Read full topic

@xion2000 wrote:

I’ve been playing around with trying to get my ESP chipset based Tuya devices setup LOCALLY with decent success. I’ve followed some good guides and read some good posts on this forum & others to get localtuya setup. I have 5 different smart plugs and a couple of bulbs working under local control which operate MUCH faster than via the apps.
I watched a Youtube video about this topick recently and the guy mentioned that even though his devices operated locally that if he disconnected his internet then after 5 minutes or so they became unresponsive!!
I decided to test this and found exactly the same issue which I could not get my head around. Anyway a few hours later it suddenly dawned on me what could be causing this. Even though I’d removed any way for the plugs & bulbs to communicate with the Tuya cloud server by unplugging my internet, my smart phone was still connected via 4G and all the devices had been initially setup using my phone. So, I switched of my phone then unplugged my routers internet connection again and waited, after 5 minutes my devices still worked BUT reaction time became VERY slow.
Can anyone explain my findings?
The way I see it, local control using the NON custom firmware method is not completely local or am I doing something wrong?

Posts: 1

Participants: 1

Read full topic

@aolley wrote:

So I’ve been using the asuswrt integration device tracker for over a year with no issues.

After upgrading from 0.102.0 to 0.104.2, it was still working. But after another restart, all my device_tracker entities have disappeared - resulting in “Entity not found” listings in lovelace - and absolutely no device_tracker entities showing up in the entity registry.

The logs show the asuswrt integration being setup, and no errors being emitted from it.

I tried adding nmap_tracker in case something had gone awry with the asuswrt integ - but still devices don’t show up.

The known_devices.yaml file gets populated still (if I delete the file outright, it recreates it and has the devices as I expect) - but entities are just not showing up in HA.

Things I’ve tried:

• removing the asuswrt integration altogether and just using the nmap_tracker integ - still no devices
• restarting HA
• deleting the known_devices.yaml file (it got recreated, so the tracker stuff must be doing something I imagine)

Any suggestions?

Posts: 2

Participants: 1

Read full topic

@go5 wrote:

Hi all,

I am completely new to Home Assistant and any type of custom automation (have several devices, but all Alexa or Homekit based).

I have been “tinkering” with home assistant, setting it up on my Mac mini (running Catalina). I followed the macOS instructions but I was unable to configure it to outrun. I did some research (other sites, you tube videos) but have not been able to successfully set it up.

Currently the only way I have home assistant running is if I launch this command through terminal and then leave terminal running." python3 -m home assistant. " I found this command when I was searching on how to get this enabled.

I am a complete amateur when it comes to scripts/codes.

Thanks for any help.

Posts: 1

Participants: 1

Read full topic

@currest2620 wrote:

Hello all,

Just a quick question about Home Assistant filters. I followed the instruction on the filter page, but it doesn’t seem to be working.

Here is the code I have in my sensor.yaml file:

- platform: filter
  name: "Filtered Bedroom Temperature"
  entity_id: sensor.bedroom_temperature
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

Here’s how it displays on the lovelace history graph card:

I am plotting sensor.filtered_bedroom_temperature against sensor.bedroom_temperature. It doesn’t display like the one depicted on the filter page, though there looks to be a single value plotted before 11:00.

I’m trying to filter out the erroneous values that are plotted every now and then.

Is there something I am missing.

Thanks in advance.

Posts: 2

Participants: 1

Read full topic

@Josep wrote:

I am playing with broadlink remote type, I wrote the code to learn IR codes with

- service: remote.learn_command

and then send the learned IR packet with

- service: remote.send_command

and all works fine. But I have a doubt… where are the learned commands stored? How can I delete the stored commands?

Posts: 1

Participants: 1

Read full topic

@myle wrote:

Just Tasmota it

with

AND it works

  - platform: mqtt
    name: "Kettle Power"
    state_topic: "stat/Kettle/POWER"
    command_topic: "cmnd/Kettle/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    optimistic: false
    qos: 0

now with MY DUM TV remote Pressing the record button

can toggle the the kettle

- id: IR remote Toggle Kettle
  alias: IR remote Toggle Kettle
  trigger:
  - entity_id: sensor.last_ir
    platform: state
    to: '190A332'
  condition: []
  action:
  - data:
      entity_id: switch.kettle_power
    service: switch.toggle

my only Question is …

how do i send the “TuyaSend4 102,0” in mqtt

my only Question is how do I send

Posts: 1

Participants: 1

Read full topic

@gotson wrote:

Hello,

since recently, i have one of my PC which cannot access Home Assistant, it get stuck on ‘loading data’ after login.
I can access HA from all my other devices (2 android devices, 1 macbook).
What is weird is that the PC gets stuck on loading with Chrome, but works well with Edge.

I tried clearing all the refresh tokens to no avail.

Checking the logs i see no obvious error, it seems the authentication works fine.

I am accessing HA externally via a reverse proxy running Caddy (this has not changed recently).

My http configuration looks like this:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.18.0.0/24

Any help is appreciated to troubleshoot this problem ! Thanks

Posts: 1

Participants: 1

Read full topic

@crboffo wrote:

Hi I am having problems with the August integration.
It stopped working and as indicated in several posts I deleted the .config file to force a new token to be generated. Now after restarting the system I get a different error: invalid password.
I checked and the password is correct…

Any advice on how to solve this issue?
Thanks in advance.

C

Posts: 1

Participants: 1

Read full topic

@currest2620 wrote:

Hi (again),

I got two filters working and thought I’d filter other sensors as well. The problem is only the first two are loading and visible in developer tools / states and the front end. I can’t see any obvious problems. I did see a similar issue in a thread a few years ago, but that was a bug that had since been resolved.

This is what I have in sensor.yaml:

- platform: filter
  name: "Filtered Kitchen Temperature"
  entity_id: sensor.kitchen_temperature
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Kitchen Humidity"
  entity_id: sensor.kitchen_relative_humidity
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Kitchen Luminance"
  entity_id: sensor.kitchen_luminance
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Bedroom Temperature"
  entity_id: sensor.bedroom_temperature
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Bedroom Humidity"
  entity_id: sensor.bedroom_relative_humidity
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Bedroom Luminance"
  entity_id: sensor.bedroom_luminance
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Garage Temperature"
  entity_id: sensor.garage_temperature
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Garage Humidity"
  entity_id: sensor.garage_relative_humidity
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

- platform: filter
  name: "Filtered Garage Luminance"
  entity_id: sensor.garage_Luminance
  filters:
    - filter: outlier
      window_size: 4
      radius: 4.0

For some reason only “Filtered Bedroom Humidity” and “Filtered Kitchen Temperature” get loaded. I’ve looked through the log but can’t see an error. The only entries that seem relevant are:

..
2020-01-22 15:32:52 INFO (SyncWorker_11) [homeassistant.loader] Loaded filter from homeassistant.components.filter
..
2020-01-22 15:32:53 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.filter
2020-01-22 15:32:53 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.filter
..

Any ideas? Thanks.

Posts: 1

Participants: 1

Read full topic

@mirekmal wrote:

Strange behavior of motion/presence sensors I noticed recently:
I have 4 IKEA motion sensors and 9 Aqara motion sensors
Phoscon shows all of them after hassio restart and all of them seems to report proper state (active, at moment of restart usually no move detected)
hassio (Developer Tools -> States) similarly shows all of them and as being off
In my Lovelace UI I have one history-graph card that shows all of them, so I can check history… and now strange things starts:

• just after restart all of these sensors are reported by history-graph card as unavailable (even if States shows off)
• if I move around to trigger them, they start to report proper state - in States status is changed to on, but history-graph shows it as Detected. It goes after a while to off/Clear, so also OK.
• from the moment the first move is detected history-graph properly shows sensor status as available and off/Clear (but part of history until then remains as unavailable)
• after 1 hour (my default history period) reported status changes to off/Clear, even if there was no move detected and sensor starts to look OK on graph.
• if I change history period from default 1 hour to 2 hours or more, it goes to previous situation, proper state until moment of restart and then sensor is shown as unavailable.
• In meantime all automations, that are based on motion sensors status change work perfectly fine, so clearly sensors are available in the ZigBee network and it is not first status change that bring them back to life.

To me it look that history graph has some issues with proper reading of initial state of sensors after hassio restart, but perhaps there is another catch that I did not yet figured out… Anyone noticed similar behavior? Any idea how to get this fixed?

Posts: 1

Participants: 1

Read full topic