!secret not working in packages

July 31, 2021, 6:15 pm

≫ Next: Blueprint wanted- when multi sensor triggered, send push notification in a window of time?

≪ Previous: Trouble Converting Temperature from MiniSplit

$

0

0

Hello,
I see a strange behavior when using !secret within a package.
It’s not working.

This is my package:

# Sensor
sensor:
  - platform: miflora
    mac: secret! miflora_fioriera_mac
    name: fioriera
    force_update: false
    median: 3
    #go_unavailable_timeout: 43200
    monitored_conditions:
      - moisture
      - light
      - temperature
      - conductivity
      - battery

# Integration
plant:
    Fioriera:
      sensors:
        moisture: sensor.fioriera_moisture
        battery: sensor.fioriera_battery
        temperature: sensor.fioriera_temperature
        conductivity: sensor.fioriera_conductivity
        brightness: sensor.fioriera_light_intensity
      # Customize the minimum battery percentage level
      min_battery: 20
      # Customize the following values based on the plant type: Succulente
      min_moisture: 7
      max_moisture: 50
      min_conductivity: 300
      max_conductivity: 1000
      min_temperature: 8
      max_temperature: 35
      min_brightness: 3000 #https://www.home-assistant.io/integrations/plant/#min_brightness
      max_brightness: 130000
      check_days: 3 #https://www.home-assistant.io/integrations/plant/#check_days

Which shows values only if I replace

mac: secret! miflora_fioriera_mac

with the actual address

mac: 'xx:xx:xx:xx:xx'

And yes, I have the string miflora_fioriera_mac in secrets.yaml but it seems it’s not being retrieved.

Can anyone comment and let me know what I’m doing wrong or if this is confirmed to be a bug?

Thanks!

1 post - 1 participant

Read full topic

---

Blueprint wanted- when multi sensor triggered, send push notification in a window of time?

July 31, 2021, 8:29 pm

≫ Next: What ports does Hass use to communicate over Homekit Controller

≪ Previous: !secret not working in packages

$

0

0

Anyone have anything working like this? I’m pretty new to HA, but I’m learning.
Thanks!

1 post - 1 participant

Read full topic

What ports does Hass use to communicate over Homekit Controller

July 31, 2021, 8:56 pm

≫ Next: HAProxy proxy server issue

≪ Previous: Blueprint wanted- when multi sensor triggered, send push notification in a window of time?

$

0

0

I’m trying to put a device on a VLAN for security. This device is talking to Hass using Homekit Controller. What ports do I need to open between the Server and device to allow the integration to work?

1 post - 1 participant

Read full topic

HAProxy proxy server issue

July 31, 2021, 9:33 pm

≫ Next: Cloudflare - 400 Bad Request error

≪ Previous: What ports does Hass use to communicate over Homekit Controller

$

0

0

Greetings!

I am new to Home Assistant and I came over from openHAB. Been up and running with Home Assistant for a couple days now and learning it has been a blast. Much better than the latter. Anyways, I seem to be having an issue accessing Home Assistant through my proxy server. I have HAProxy setup with my pfsense box and I’m running a few websites without any issues. I was able to set up a reverse proxy to my Home Assistant server which I can access from anywhere now. Frontend is HTTPS and backend is HTTP. I’m noticing that after I connect in, I get quick random disconnects/reconnects, every 20 to 30 seconds. Sometimes longer. If I connect locally using the direct IP and port, no issues. Been trying to figure out the issue all day with no luck. It’s very annoying because it basically refreshes the page and I can’t work on anything for long periods of time. Hopefully that all makes sense. Any help would be greatly appreciate! Thank you.

1 post - 1 participant

Read full topic

Cloudflare - 400 Bad Request error

July 31, 2021, 10:38 pm

≫ Next: Rebooting home assistant throws a strange error

≪ Previous: HAProxy proxy server issue

$

0

0

There have been recent changes to the HTTP component which is causing my (typical?) Cloudflare configuration to break.

I didn’t see another thread dealing with this issue, so here’s the problem/solution:

• The recommended Cloudflare configuration uses ‘Proxied’ requests to your HA instance.
• This is treated as a ‘reverse proxy’ by HA which (currently) blocks these requests, so you get a 400 Bad Request error.
• Switching to DNS-only is an option, but this breaks the 10Y SSL certificate Cloudflare issues that several guides suggest as an alternative to LetsEncrypt etc.

You need to follow the guide for HTTP Reverse Proxies and add all the IP Ranges Cloudflare may use - you can copy and paste these in including the /XY subnet.

This should resolve the issue (until Cloudflare adds/deletes ranges).

1 post - 1 participant

Read full topic

Rebooting home assistant throws a strange error

July 31, 2021, 11:09 pm

≫ Next: Message malformed: extra keys not allowed @ data['traces']

≪ Previous: Cloudflare - 400 Bad Request error

$

0

0

Logger: homeassistant.setup
Source: setup.py:172
First occurred: 4:01:13 PM (1 occurrences)
Last logged: 4:01:13 PM

Setup failed for select: Integration not found.

Nothing seems to be broken as far as I can tell and I don’t know what integration would possibly be called select… any ideas?

1 post - 1 participant

Read full topic

Message malformed: extra keys not allowed @ data['traces']

August 1, 2021, 1:08 am

≫ Next: Reset entity energy power every mounth

≪ Previous: Rebooting home assistant throws a strange error

$

0

0

Why can’t I do this?

alias: 1e badkamer ventilator aan en uit
description: ''
trigger:
  - platform: state
    entity_id: binary_sensor.1e_badkamer_warm_water
    id: warm_water
  - device_id: 9c05bef1cd794483a2fd923ad772d2aa
    domain: deconz
    platform: device
    type: remote_button_long_press
    subtype: turn_off
    id: button_press
condition: []
action:
  - type: turn_on
    device_id: b3e8ea8642f0619b4bc2073a52b4107c
    entity_id: switch.1e_badkamer_ventilator
    domain: switch
  - choose:
      - conditions:
          - condition: state
            entity_id: binary_sensor.1e_badkamer_warm_water
            state: 'on'
        sequence:
          - service: timer.start
            data:
              duration: '00:05:00'
            target:
              entity_id: timer.badkamer_ventilator_timer
          - wait_for_trigger:
              - platform: state
                entity_id: timer.badkamer_ventilator_timer
                to: idle
          - type: turn_off
            device_id: b3e8ea8642f0619b4bc2073a52b4107c
            entity_id: switch.1e_badkamer_ventilator
            domain: switch
    default: []
mode: restart
traces:
  stored_traces: 10

4 posts - 3 participants

Read full topic

Reset entity energy power every mounth

August 1, 2021, 1:51 am

≫ Next: Entity_picture not working

≪ Previous: Message malformed: extra keys not allowed @ data['traces']

$

0

0

Hi, I create a template sensor in this way to monitor energy in KWH:

sensor:
  - platform: integration
    source: sensor.power_in
    name: Energy_in
    round: 2

now every mounth I want to reset to 0 this value, so I use a pyscript like this:

  - service: python_script.set_state
    data:
      entity_id: sensor.energy_in
      state: 0

and it works, but as soon as the energy is updated by template/integration it returns to old value.
Should I restart HA as soon as I reset ? Is there a trick? thanks!

2 posts - 2 participants

Read full topic

---

Entity_picture not working

August 1, 2021, 2:32 am

≫ Next: Inegrate Tellstick DUO

≪ Previous: Reset entity energy power every mounth

$

0

0

Hi All,

Suddenly this is not working.
The icons of the entities are gone and not show. The files are still there…

HA 2021.7.2

device_tracker.1717fe36_3c70_4599_963c_b70b6ee95eba:
  friendly_name: "Peter Locative"
  templates:
    entity_picture: if (state === 'home') return '/local/images/person/peter-home.png'; return '/local/images/person/peter-away.png';

device_tracker.peter_iphone_geofency:
  friendly_name: "Peter Geofency"
  templates:
    entity_picture: if (state === 'home' ) return '/local/images/person/peter-home.png'; return '/local/images/person/peter-away.png';

7 posts - 4 participants

Read full topic

Inegrate Tellstick DUO

August 1, 2021, 2:45 am

≫ Next: Someone available to train/teach me?

≪ Previous: Entity_picture not working

$

0

0

Hello!

Can somebody help me how i integrate my Tellstick DUO to my system?
I have install the addon but i dont know how i set my units. Please, if you want to help me explain so i understand. im new on this.
I have a house with many (about 70 units) lights, sensors and switches. I only use Nexa system on my devices.

Hope somebody can help me.

1 post - 1 participant

Read full topic

Someone available to train/teach me?

August 1, 2021, 2:57 am

≫ Next: Tasmota Integration not detecting devices

≪ Previous: Inegrate Tellstick DUO

$

0

0

I am helping a friend in Orange County, CA whose husband passed away last month. He was quite the tinkerer and their home has quite a few automations, some with no manual way to override the automations. I’m hopping there’s another HASS enthusiast in the area who would be willing to walk me through the important stuff. I’m able to read man pages and search forums, and eventually I’ll get there. But, right now, I don’t know what I don’t know and I’m just trying to get things stabilized and working before I have to leave in a week. After that, we’ll be looking at whether this will be something I could maintain for her remotely, or we just need to decommission HASS and simplify. We’re willing to pay for this person’s time. Thanks in advance.

1 post - 1 participant

Read full topic

Tasmota Integration not detecting devices

August 1, 2021, 3:51 am

≫ Next: Call service from switch - WOL turn TV on/off

≪ Previous: Someone available to train/teach me?

$

0

0

Hello,

I have followed Home Assistant - Tasmota page and set up the Tasmota integration in my HA (2021.7.4).

• My Mosquitto is correctly configured and working.
• I have a bunch of Tasmota devices working already using the “MQTT discovery”.
• I am trying to migrate one of the devices to “SetOption19 0”. But the new Tasmota integration is just now detecting this device.
• On the Tasmota device, the following is the console log soon after reboot.

00:00:00.001 HDW: ESP8285
00:00:00.050 CFG: Loaded from flash at F9, Count 43
00:00:00.056 QPC: Count 1
00:00:00.060 SER: Set to 8N1 9600 bit/s
00:00:00.110 Project tasmota sonoff-living-fan-2 Version 9.5.0(tasmota)-2_7_4_9(2021-06-17T08:26:35)
00:00:00.549 WIF: Connecting to AP1 Channel 11 BSSId 1C:3B:F3:DC:82:AC in mode 11n as sonoff-living-fan-2-5108...
00:00:03.757 WIF: Connected
00:00:04.009 HTP: Web server active on sonoff-living-fan-2-5108 with IP address 192.168.2.206
11:33:53.021 MQT: Attempting connection...
11:33:53.035 MQT: Connected
11:33:53.038 MQT: tele/sonoff-living-fan-2/LWT = Online (retained)
11:33:53.040 MQT: cmnd/sonoff-living-fan-2/POWER = 
11:33:53.050 MQT: tele/sonoff-living-fan-2/INFO1 = {"Info1":{"Module":"Sonoff iFan03","Version":"9.5.0(tasmota)","FallbackTopic":"cmnd/DVES_D573F4_fb/","GroupTopic":"cmnd/tasmotas/"}}
11:33:53.054 MQT: tele/sonoff-living-fan-2/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"sonoff-living-fan-2-5108","IPAddress":"192.168.2.206"}}
11:33:53.057 MQT: tele/sonoff-living-fan-2/INFO3 = {"Info3":{"RestartReason":"Software/System restart"}}
11:33:53.059 MQT: stat/sonoff-living-fan-2/RESULT = {"POWER1":"OFF"}
11:33:53.062 MQT: stat/sonoff-living-fan-2/POWER1 = OFF
11:33:54.483 QPC: Reset
11:33:57.417 MQT: tele/sonoff-living-fan-2/STATE = {"Time":"2021-08-01T11:33:57","Uptime":"0T00:00:11","UptimeSec":11,"Heap":29,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","FanSpeed":0,"Wifi":{"AP":1,"SSId":"Anjan & Shruthi Home","BSSId":"1C:3B:F3:DC:82:AC","Channel":11,"Mode":"11n","RSSI":80,"Signal":-60,"LinkCount":1,"Downtime":"0T00:00:05"}}

• I have searched around endlessly to figure out why this new native Tasmota integration is not working. But it seems to “just work” for everyone else.

Screenshot 2021-08-01 at 16.17.102846×1883 490 KB

• Am I right in assuming that the Tasmota device is supposed to send a message on “tasmota/discovery/…” topic to notify HA about itself? (The prefix mentioned above)
• In the Tasmota Console logs and in MQTT Explorer (separate app), I don’t see any messages on such a topic. Screenshot below.

Screenshot 2021-08-01 at 16.14.122272×1664 315 KB

Does this mean that Tasmota is not doing something it is supposed to do?

I have restarted HA many times, but still the same result. Could someone help me please?

Screenshot 2021-08-01 at 16.18.232812×1876 439 KB

Thanks!

1 post - 1 participant

Read full topic

Call service from switch - WOL turn TV on/off

August 1, 2021, 4:05 am

≫ Next: Rename MQTT State Shelly

≪ Previous: Tasmota Integration not detecting devices

$

0

0

HI there,

HA newbie here!

I’m trying to control my philips tv on/off setting with HA. I have now managed to create an “on” switch with a WOL config. Now, I am trying to configure the “turn_off” part of the switch.
My TV has an option for turning off from HA, by using a service call.

This works fine as automation, but when I add this to the switches.yaml like so:

- platform: wake_on_lan
  name: "TV"
  mac: "xx-xx-xx-xx-xx-xx"
  host: 192.168.x.x
  turn_off:
  service: media_player.turn_off
  target:
  entity_id: media_player.55pus6804_12

My config is deemed incorrect:

Invalid config for [switch.wake_on_lan]: [service] is an invalid option for [switch.wake_on_lan]. Check: switch.wake_on_lan->service. (See ?, line ?)

I’ve tried moving the turn off commands into a script and calling the script, but as you’re also calling a service to call a script, this also fails.

Any ideas how to do this?

Kind Regards,

Eduard

1 post - 1 participant

Read full topic

Rename MQTT State Shelly

August 1, 2021, 4:33 am

≫ Next: MODBUS Changes/Development

≪ Previous: Call service from switch - WOL turn TV on/off

$

0

0

Hi guys,

i want to rename the state from MQTT for one of my Shelly devices in the frontend.

my Configuration is:

  - platform: mqtt
    name: "Shelly DW2 Status"
    state_topic: "shellies/shellydw2-x/sensor/state"

Its “closed” or “open”.
Want to rename it to my German Language.
Thanks

How can i rename the status in the ui , with Template sensor or directly in the MQTT Section?

dw222761×91 16.1 KB

1 post - 1 participant

Read full topic

MODBUS Changes/Development

August 1, 2021, 4:50 am

≫ Next: Remove old entities Buienradar

≪ Previous: Rename MQTT State Shelly

$

0

0

Anyone else getting annoyed with all these modbus changes being made? Is there actually a thread that can moderate what is being changed/developed or proposed

According to Modbus - Home Assistant there are 508 active MODBUS deployments but am sure there are more that do not have component reporting turned on

RANT
So far the following has broken my running config

• Sensors moved under individule HUB
• Multiple HUB / sensors not working

Now its “structure” being removed

Just stop and ask the community what they are using, and why
RANT over

2 posts - 2 participants

Read full topic

---

Remove old entities Buienradar

August 1, 2021, 5:21 am

≫ Next: How to create card that only shows sensors with a specfic state

≪ Previous: MODBUS Changes/Development

$

0

0

Remove old entities, no longer available, is a pain when it comes to this integration.
I have tried all sorts of solutions.

• stop Home Assistant and remove the entities out of the hidden folder.
• remove integration, stop Home Assistant and try to remove the entities from the hidden folder.

Every time I rebooted Home Assistant all of the old entities came back. (108 in total) So they are somewhere in another location?

For now I ignore them, but I hope to learn how to remove them properly. In the forum threads I could not find any recent solutions for this issue.

2 posts - 2 participants

Read full topic

How to create card that only shows sensors with a specfic state

August 1, 2021, 5:23 am

≫ Next: Hue Motions Sensor dissapear / go missing

≪ Previous: Remove old entities Buienradar

$

0

0

I am using the Omnilink bridge to monitor and control all of the Omnilink sensors/switches. How do I create a card in the Lovelace UI that only shows the sensors/switches that are on or open?

2 posts - 2 participants

Read full topic

Hue Motions Sensor dissapear / go missing

August 1, 2021, 5:31 am

≫ Next: Homeseer sensor integration

≪ Previous: How to create card that only shows sensors with a specfic state

$

0

0

Motion sensors were fine, and today they’re gone, dissapeared faster than my salary.

Rebooted Hue bridge & HA. Tried cursing a bit too.

Alexa and Hue apps can see the motion sensors. HA not at all.

Any ideas? What’s the standard operating proecdure for this kind of thing? Re-install HA Hue Integration?

HA connected to Hue Bridge using standard Hue integration.

2 posts - 2 participants

Read full topic

Homeseer sensor integration

July 31, 2021, 12:35 pm

≫ Next: [SOLVED] OTP Integration Token

≪ Previous: Hue Motions Sensor dissapear / go missing

$

0

0

Still new to Z wave but I have one device working already, integration was painless. Now looking at the HomeSeer HSM200 mulitsensor - does it work directly with the Z-wave JS integration?

I’d assume it would, but I also see a "Homeseer: integration so I’m wondering if there’s something unique about Homeseer. Or is the Homseer integration just for the hub?

2 posts - 2 participants

Read full topic

[SOLVED] OTP Integration Token

August 1, 2021, 6:46 am

≫ Next: Action chose wont execute trigger when holding state logic is added

≪ Previous: Homeseer sensor integration

$

0

0

Hi,
I am trying to make kind of an access controll System using the OTP Integration, but i am on a RPI 4 b+ Running the Hassio Image, so i cant do the Commands given in the Description of the Integration.
Can you please help me, i am a HA noob and habe switched from openHAB 3 a few weeks ago.
(The idea is that i put a card in my main dashboard with my location on it, but only Show it if the correct code (from my otp App) is entered in a text field)
Thanks

3 posts - 2 participants

Read full topic