It used to be pretty easy to quickly browse HACs repos by bringing up search results, then clicking on a repo, then X-ing out of it, then clicking on the next repo, etc. Just like any other app store, really.

Now each repo loads up in a new page, and clicking “Back” or the back arrow in the upper left no longer return me to my search results. And when I reopen the search window it’s back to the default sorting, and back at the top of the list (although it does retain any search terms I might have entered).

This makes it difficult to browse and randomly discover repos, which was part of the fun of HACs before this change was made. I’ve opened a ticket about it, but in case the developers aren’t interested in reverting to this functionality, can you recommend any alternative methods for browsing available integrations, frontend resources, and themes?

1 post - 1 participant

Read full topic

I have a Glowmarkt MQTT sensor. This works well, except that on occasion the raw data from the sensor shows a sudden jump (up or down) which can cause problems for my stats.

I integrate the sensor as follows, trying to catch the outliers - and if one is found, then just use the last recorded value.

platform: mqtt
    name: "Home Electricity Meter"
    state_topic: "SMART/LAB/5410ECA1BC1F"
    unit_of_measurement: 'kWh'
    device_class: energy
    state_class: total_increasing
    value_template: >
      {% if (value_json['elecMtr']['0702']['00']['00']|int(base=16) * value_json['elecMtr']['0702']['03']['01']|int(base=16) / value_json['elecMtr']['0702']['03']['02']|int(base=16))|int > 50000 %}
          {{ states('sensor.home_electricity_meter') }}
      {% else %}
          {{ value_json['elecMtr']['0702']['00']['00']|int(base=16) * value_json['elecMtr']['0702']['03']['01']|int(base=16) / value_json['elecMtr']['0702']['03']['02']|int(base=16) }} 
      {% endif %}

The “magic number” of 50000 is chosen to filter out any high outliers - since the expected value is only ~15000

However, it would be more future proofed if I could avoid this “magic number”.

I have tried replacing:

50000
with
(states(‘sensor.home_electricity_meter’)*2)|int

But that gives no output at all. Any ideas?

1 post - 1 participant

Read full topic

I’ve an automated mosquito net connected via KNX (cover with device class: shade) to my home assistant system.

How can I hide the tilt up/down control, as this control has no function?

3 posts - 2 participants

Read full topic

Hello. I have a Shelly 2.5.

I want to use one of the switches in detached mode for automations (single click, double click).

However, I have latching switches instead of momentary ones.

Also, the switch I want to use is a 2-way switch.

The problem I am having is that shelly.click is tracking the latching switch state, meaning that if one of the two way switches gets pushed once, then the Shelly registers it as a long press. The next single press of either of the two physical switches does nothing (as expected, the shelly thinks that the long press is over since the voltage drops to 0). Also, double clicking the switch in this state does not register as a single press only.

This is weird, but what I am looking for is a “detached edge” switch mode, which changes the state on every hit instead of reading the voltage.

Is there such an option or workaround anywhere?

2 posts - 2 participants

Read full topic

(topic deleted by author)

1 post - 1 participant

Read full topic

This just started after i updated to the latest beta, the error is super vague i dont know where to start. line 286 is just where i include my a automations.yaml

Logger: homeassistant.config
Source: config.py:455
First occurred: 14:51:22 (3 occurrences)
Last logged: 14:51:22

Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('logger', OrderedDict([('default', 'error')])), ('api', {}), ('lock', {}), ('my', {}), ('cloud', {}), ('sun', {}), ('input_datetime', {}), ('ssdp', {}), ('input_boolean', {}), ('person', {}), ('config', {}), ('history', {}), ('zeroconf', {}), ('system_health', {}), ('mobile_app', {}), ('zha_toolkit', {}), ('remote_syslog', {}), ('discovery', {}), ('media_source', {}), ('energy', {}), ('default_config', {}), ('ifttt', OrderedDict([('key', 'dz28yYgXihJf3vEvfJvDjy')])), ('folder_wa.... (See /config/configuration.yaml, line 286).

Any insight or direction would be greatly be greatly appreciated

2 posts - 2 participants

Read full topic

Using HA on RPi4 with Z-Wave JS 0.1.64. My existing 28 device Z-Wave network is functioning just fine, but I cannot add any Z-Wave device now, it just times out. This includes both brand new devices of any brand/type, and existing devices if I reset them. I have an Aeotec 5+ stick.

• Power cycling doesn’t work
• Restarting Z-Wave JS doesn’t work
• Excluding devices doesn’t work
• Bringing devices closer doesn’t work (BUT, if I bring a device literally 6 inches away, it says “The device could not be added” instead of failing to find it entirely)

I’m not sure when this started but it was probably after one of the recent updates to Z-Wave JS. It could have been a month ago for all I know.

After getting burned previously with the HAOS no-boot after update thing a few months ago, I’ve just about had it with HA unless someone has a simple solution to this total Z-Wave meltdown. Is it a better strategy to just never update anything?

Maybe the Aeotec stick has failed? I have a spare stick but AFAIK all of the devices are tied directly to the stick and not HA so if I replace the stick I have to re-create the entire network, correct?

Anyway, please help, my system is totally broken now, thanks.

1 post - 1 participant

Read full topic

Hi all,
I have HA v2022.7.7 installed on a Raspberry Pi.
My UPS is connected to the USB port of the Raspberry Pi.
I installed the add-on “Network UPS Tools” v0.11.0 to monitor the UPS (I guess nut server side).
I installed the integration Network UPS Tools (NUT) (latest, but not sure where to find version number) (I guess nut client side).

While monitoring the UPS, I noticed that the battery charge is jumping from one value to the other and was wondering about the refresh rate. Where can I find the refresh rate? Or, if it needs to be defined, what is the default value and where can I define it?

Thanks for your help.

1 post - 1 participant

Read full topic

I’m using a rest sensor to pull some electricity pricing, including datetimes to which the future pricing applies.
However, while the rest sensor returns the correct datetime string
eg tradingDateTime: 2022-08-01T11:30:00+12:00 for my timezone.
The sensors that are created by that attribute being filtered by a template sensor are not correct, eg 2022-07-31T23:30:00+00:00. I don’t do any manipulation of that value/string (that I know of).

the “+12 hours ahead” is removed - some how it is converted to UTC.

To re-phrase:
The rest payload shows the correct datetime. When the datetime attribute is filtered to a sensor, something changes the time zone!

should I not have the device class defined as “timestamp”?
From the Sensor - Device Class page I used this as my reason to define the class:

• timestamp: Datetime object or timestamp string (ISO 8601)

my yaml:

rest:
  - authentication: basic
    method: GET
    headers:
      Authorization: Bearer {{ states('sensor.token') }}
      Accept: application/json
    scan_interval: 180
    resource: 'https://etc....'
    sensor:
      - name: "forecast_price"
        json_attributes_path: "$.[0].prices[0]"
        value_template: "OK"
        json_attributes:
          - "schedule"
          - "tradingDateTime"
          - "tradingPeriod"
          - "node"
          - "price"
          - "lastRunTime"

The template sensor that filters rest attributes to sensors - for example:

template:
  - sensors:
      trading_date_time:
        value_template: "{{ state_attr('sensor.price_forecast', 'tradingDateTime') }}"
        device_class: timestamp

EDIT: just to be clear, my HA time zone is set to GMT+13

1 post - 1 participant

Read full topic

Hello all,

Could anyone help me out with the subject? Or does anyone possibly have an example of doing this with the subject device? (I have heard ADB commands can be specific to the device)

I have verified that I can send the ADB commands to the TV (using Android TV Integration) but to be honest, I have no clue if it is even possible to get it to play music consistently. I really almost don’t even care what station as long as I can get it to play one of the recent ones.

The reason, I am wanting to do it by ADB commands is because when you do it through a routine on google assistant, it sends the audio to the television through a “cast” and almost all music services only allow 30 min- 1 hour until it stops playing (free tier).

By starting the app and music directly throught the TV interface, I have learned it goes for a few hours before stopping.

1 post - 1 participant

Read full topic

Hi,
What is the best way to create a new sensor that gives me the estimated Wh available from 2 installed batteries (totalled).

So far instance, both batteries give me these as available capacities:-
9905.28 + 9832.32 = 19737.60.

Thats what the batteries capacities are.

I also know that the capacity left in both batteries is 27% (ive added both together already in a separate template).

How can I get these pieces of information outputted to a new sensor giving me an estimate of how many Wh I have remaining?

I would do 19737.60 x 0.27 = 5329.15 but I’m unsure how to translate 27% from my created template to 0.27.

Thanks for any assistance, I’m relatively new to the power of templates.

1 post - 1 participant

Read full topic

I just upgraded to 2022.7.7 and some of my automations aren’t working any longer: the zigbee dimmers get turned one (expected) but immediately turned off as the end of the automation. Simple zigbe switches remain on.

They can be be turned on manually without problems.

1 post - 1 participant

Read full topic

I have two Pi 4s running Home Assistant:

Old Assistant:
I can’t find it on the LAN anymore, not sure why. I don’t want to reboot it because I don’t know what will happen. I hooked up a monitor to it and it shows it claiming an IP address on startup, but it’s not at that address. My Insteon PLM is still plugged in to it and that system is still controlling some Insteon devices.

New Assistant:
I set this up because I was having problems with the older version. I still have a few things to finish on it, including the Insteon devices. No PLM in it at this point at all.

Insteon setup:
I have a few Insteon devices and I really do not want to remove them then add them, since one is a garage door opener that’s hard to get to (and high up!) and others need to have some light fixtures removed from walls or ceilings to get to the controller. I have the PLM plugged into a USB extender on my Pi with Home Assistant running. I also have a 2413S Powerline Modem plugged in about 4’ from the PLM. I have had trouble with the PLM, by itself, connecting to the Insteon devices, even ones that were close by. Once I added the 2413S, Home Assistant was able to communicate with my Insteon devices.

Goal:
In short, I want to pull the PLM out from the old system, plug it in the new one, add the Insteon integration, and have my current Insteon devices working with the new system. I’ve read that the Insteon devices are paired with the PLM, not with the software like Home Assistant. Since several devices are on timers, and, even with the old system not being easily found on my LAN, still being activated and controlled from the old system, I don’t want to pull the PLM out of that system until I have an upgrade path so I can be reasonably sure that I can transfer the PLM to the new system and start controlling the Insteon devices.

I understand this may not be possible and I’ll have to go through and reset my Insteon controllers by hand (since I can’t remove them from the old system when I can’t connect to it), but if I remember correctly, that the devices pair to the PLM and not the software, I would think a changeover would be possible.

1 post - 1 participant

Read full topic

Hi there, I’m searching for a way to have a grid of input_boolean helper like this:

I’ve tried to make it with Glance, Horizontal-Stack and Grid, but none of this fits my requirement. Any idea to do this?

3 posts - 3 participants

Read full topic

Hi all,

I have HASSIO installed on a Raspberry Pi 3B+ and I use Duck DNS as free DNS provider; I installed the Let’s Encrypt add-on for Home Assistant and it worked fine until about a month ago, when I changed my ISP.
My previous ISP gave me the possibility to open the public port 80, so I was able to renew my Let’s Encrypt certificate using the HTTP challenge; now my new ISP give me a range of pulic ports that doesn’t include port 80 (the port range starts with port 49152 and it is blocked).
I tried to follow instructions on https://github.com/home-assistant/addons/blob/master/letsencrypt/DOCS.md to enable the DNS challenge but without success due to some configuration option that I am unable to set correctly.

This is the configuration I put on the DNS section of the Let’s Encrypt add-on after selecting the DNS option for the challenge:

email: my_email@gmail.com
domains:
  - mydomain.duckdns.org
certfile: fullchain.pem
keyfile: privkey.pem
challenge: dns
dns:
  provider: duckdns
  duckdns_email: my_email@gmail.com
  duckdns_api_key: <duckdns token>

and this is the Let’s Encrypt add-on log after its restart:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[08:22:13] INFO: Selected DNS Provider: null
[08:22:14] INFO: Use propagation seconds: 60
usage: 
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate. 
certbot: error: unrecognized arguments: --null --null-credentials /data/dnsapikey
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I am not able to solve this problem due to my limited experience with these kind of problems; please, is it possible to obtain more detailed help about the DNS challenge configuration of the Let’s Encrypt add-on?

Thanks in advance for any hint.

Regards.

1 post - 1 participant

Read full topic

Hi,
I would like to have 3 cameras to monitor outside of my home.
I’m thinking about Hikvision cameras with Acusense technology (to recognize ‘human’/‘car’ objects).

Looking at hikvision NVRs, it seems those cameras would be in different subnet, private to NVR, and access to them would be via NVR.
My questions:

1. is it possible to have hikvision cameras in my main subnet, same as my HA, same as my laptop, same as NVR? Perhaps instead of nvr with built-in PoE switch, I should just buy seperete switch?
2. if not, if the architecture of hikvision is that nvr needs to built it’s own private subnet, I suppose I could get a camera feed in my HA dashboard via NVR… but - wouldn’t I ‘loose’ acusense features in HA ?

3 posts - 3 participants

Read full topic

I have an automation. I want to send the value of the door to telegram.

I wrote this in action but it does not working.

service: notify.telegram
data:
  title: Main Entrance
  message: Main entrance door is {{ binary_sensor.lumi_main_entrance_door_on_off }}

1 post - 1 participant

Read full topic

There is an automation which sends a message via Telegram if some conditions are met.
Assume - if some device becomes unavailable.

Devices may become unavailable “almost simultaneously”.
Means - messages should be sent at “almost” one moment of time.

In these cases I usually see messages in log like:
2022-08-01 10:54:20 WARNING (SyncWorker_15) [telegram.vendor.ptb_urllib3.urllib3.connectionpool] Connection pool is full, discarding connection: api.telegram.org
2022-08-01 10:54:20 ERROR (SyncWorker_15) [homeassistant.components.telegram_bot] Error sending message: Flood control exceeded. Retry in 5.0 seconds. Args: (-1001301432273, ‘RPi-2: ping OK (startup)’), kwargs: {‘parse_mode’: ‘HTML’, ‘disable_web_page_preview’: None, ‘disable_notification’: False, ‘reply_to_message_id’: None, ‘reply_markup’: None, ‘timeout’: None}

Guess there is a problem with an “almost simultaneous” using Telegram.
What I need is a some kind of mutex (mutual exception) here - do not allow to use Telegram unless it is becomes available.

What I have now:

1. A script “notify_send_notification” containing a “notify.xxxx” service call for telegram.
2. A blueprint “XYZ” containing calling a script “notify_send_notification” if some template is TRUE.
3. A few automations based on that “XYZ” blueprint.

Assume that the “XYZ” blueprint has a “mode: restart”.
The logic is that one automation is for one device.

I may specify a “mode” for the “notify_send_notification” script.
What mode should it be?
Queued?
Will it help me?

Update: “queued” does not help.

1 post - 1 participant

Read full topic

I currently obtain the value of daily consumption from a device. I want to create a sensor to obtain the increasing value of the daily consumption.

  - sensor:
    - name: "Venta de electricidad (total) v3"
      unit_of_measurement: 'kWh'
      device_class: energy
      state_class: total_increasing
      state: >-
        {{ states.sensor.homekit_91000hku21501076.attributes.Charts_sell }}
    - name: "Compra de electricidad (total) v3"
      unit_of_measurement: 'kWh'
      device_class: energy
      state_class: total_increasing
      state: >-
        {{ states.sensor.homekit_91000hku21501076.attributes.Charts_buy }}       

Problem is that the created sensors give exactly the same information as the original sensors. What I mean is that even when stating total_increasing the created sensors reset daily to 0. On developer tools/states both sensors are stated as total_increasing.

If anyone has any advice please tell. I don’t know where to look for the problem. Thanks.

1 post - 1 participant

Read full topic

I have some automations where the service to be called is determined by a template. In certain situations I do not want a service called. In that case I call the service homeasistant.update_entity in order to prevent the error “invalid service”. Like this:

  - service: '
    {% if state_attr("sensor.jablotron_oasis_80","zones")=="ABC" and states("alarm_control_panel.woonhuis_alarm")!="armed_away" %}
      alarm_control_panel.alarm_arm_away
    {% elif state_attr("sensor.jablotron_oasis_80","zones")=="A" and states("alarm_control_panel.woonhuis_alarm")!="armed_home" %}
      alarm_control_panel.alarm_arm_home
    {% elif state_attr("sensor.jablotron_oasis_80","zones")=="None" and states("alarm_control_panel.woonhuis_alarm")!="disarmed" %}
      alarm_control_panel.alarm_disarm
    {% else %}
      homeassistant.update_entity
    {% endif %}
    '
    target:
      entity_id: alarm_control_panel.woonhuis_alarm
    data:
      code: !secret alarm_code
    '

However this stil generates an error because the update_entity service does not allow any data.
Is there a no-op service that can be applied in all domains, accepts all kind of data and does exactly nothing?

2 posts - 2 participants

Read full topic