I want to use TTS to summarise the events from my calendar for the day, however the calender entitity only has the “next” event listed. Is there a way to do this ?

1 post - 1 participant

Read full topic

Hi.
Using a BLE client sensor I see only the first character of the BLE service’s characteristic in decimal format .

sensor:
- platform: ble_client
    ble_client_id: ESP32_BLE_Remote
    name: "ESP32 Remote BLE-2"
    service_uuid: '1800'
    characteristic_uuid: '2a00'

The question are:

1. is it possible to show/convert this first character in ASCII ?
2. is it possible to show the entire service’s characteristic (i.e. “MyESP32”) instead of only the first character?

1 post - 1 participant

Read full topic

Just unpacking boxes first couple of days after moving into new, extensively renovated home. I am a complete newbie smart-home/HA user, but have read quite a bit, and am reasonably IT/programming competent. I envision a building gradually into fairly extensive implementation, integrating variety of protocols/devices/uses.

Starting out, I have installed several dozen switches and smart lights, and a dedicated Zigbee hub, all from vendor Terncy. There is an HA integration for this stuff available, but before integrating into HA all these devices must first be registered in the hub using the Terncy app.

I anticipate that the device names I assign in initial registration in the Terncy hub will be carried into HA, and would like to have a device naming scheme which facilitates ease of use in HA. Wondering if it is a good idea to create device names that help identify the device at a glance, reflecting perhaps such things as device type, room, wall (eg, N, E, S, W), wall location (left-to-right index numbering or similar).

Grateful for any advice from folks here if this is a good idea basically, and if so, what suggestions might people offer.

4 posts - 4 participants

Read full topic

Noob here, spent the past few hours digging through forums and documentation but seem to be hitting a roadblock hoping you guys can help me with.

Goal:
Ping a local IP address, on failure, power cycle a smart plug

Progress
D-Link smart plug setup manual integration with (through configuration yaml file), works great no issues.

I’ve also setup a binary_sensor for ping to ping the server (powered through the dlink outlet), which appears to work correctly as well.

switch:
  platform: dlink
  host: 10.0.0.50
  username: admin
  password: XXXXX

binary_sensor:
  - platform: ping
    host: 10.0.0.99
    name: "Check Server"
    scan_interval: 30

I’m having issues though figuring out how to setup a trigger to power cycle the dlink outlet, as it does not show up as an actual “device” per-say. Because of this, does that mean that my automation would need to somehow set the state from on to off then from off to on?

This is where i’m getting stuck at, i’m not sure how I would go about doing a power cycle on the dlink device when the ping fails, can anybody help me out or point me in the right direction please?

Reference
I have a very old server that needs to be updated/upgraded but I have not had the time yet to buy new parts, and the easiest solution for me to deal with it for now is to just power cycle. If I could get this automation setup and working it could buy me a little more time to get the funds and parts together to do the upgrade, without much downtime.

Thanks!!

1 post - 1 participant

Read full topic

Hello

I have had my Nest doorbell integrated into HA and that all works fine. I have now got one of the new Nest Hub Max devices which also has a camera, but it is not showing up in HA.
Does anyone know whether this needs to be setup on a new google project or can be added to my original project.

thanks

1 post - 1 participant

Read full topic

Hi folks,

trying to read data from my Wallbox (Vestel EVC04, firmware 2.65.0) via the TCP modbus.

Unfortunately, I am getting an error when trying to connect via modbus platform: “Connection to (192.xxx.xxx.xxx, 502) failed: [Errno 111] Connection refused”

Has someone managed by chance to connect to the Vestel wallbox or has some further ideas how to get it working.

My config.yaml entry looks as follows:

# vestel charging station
modbus:
  - name: Ladestation
    close_comm_on_error: true
    delay: 5
    timeout: 5
    type: tcp
    host: 192.xxx.xxx.xxx
    port: 502

The modbus TCP manifest from vestel wallbox states the following:
Vestel EVC04 charging station acts as a slave device in the Modbus TCP/IP communication. Charging station should be in the same network with the master device or a proper routing should be applied to provide communication between slave and the master devices in different sub networks. Each charging station should have different IP address. Modbus TCP communication port number is 502 and Modbus Unit ID is 255 for Vestel EVC04 charging stations. There can be only one active Modbus master connection at any time.

Appreciate any thought on this.

Cheers!

1 post - 1 participant

Read full topic

I am trying to do a home assistant integration and per the documentation Tuya - Home Assistant

1106: permission deny

• Incorrect username or password: Enter the correct account and password of the Tuya Smart or Smart Life app in the Account and Password fields (social login, which the Tuya Smart app allows, may not work, and thus should be avoided for use with the Home Assistant integration). Note that the app account depends on which app (Tuya Smart or Smart Life) you used to link devices on the Tuya IoT Platform.

I interpret this to mean that my Tuya account was likely created using a social media authentication token not with a standard username and password created and stored on the Tuya Servers… how to I change my tuna account to be “non-social” so I can get passed this error?

1 post - 1 participant

Read full topic

Using the RTL_433 add-in and also the corresponding RTL_433-to-MQTT add-in, and I can see the device definition messages in MQTT Explorer (see below) Unfortunately, no devices/entities were ever automagically created from these messages. Is there something missing from the add-in’s device syntax?

homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-UTC/config : {"device_class": "timestamp", "name": "Cotech-367959-121-UTC", "icon": "mdi:clock-in", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/time", "unique_id": "Cotech-367959-121-UTC", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-B/config : {"device_class": "battery", "name": "Cotech-367959-121-B", "unit_of_measurement": "%", "value_template": "{{ float(value|int) * 99 + 1 }}", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/battery_ok", "unique_id": "Cotech-367959-121-B", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-F/config : {"device_class": "temperature", "name": "Cotech-367959-121-F", "unit_of_measurement": "\u00b0F", "value_template": "{{ value|float }}", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/temperature_F", "unique_id": "Cotech-367959-121-F", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-H/config : {"device_class": "humidity", "name": "Cotech-367959-121-H", "unit_of_measurement": "%", "value_template": "{{ value|float }}", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/humidity", "unique_id": "Cotech-367959-121-H", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-RT/config : {"name": "Cotech-367959-121-RT", "unit_of_measurement": "mm", "value_template": "{{ value|float }}", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/rain_mm", "unique_id": "Cotech-367959-121-RT", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}
homeassistant/sensor/Cotech-367959-121/Cotech-367959-121-WD/config : {"name": "Cotech-367959-121-WD", "unit_of_measurement": "\u00b0", "value_template": "{{ value|float }}", "state_topic": "rtl_433/b854a4b8-rtl433/devices/Cotech-367959/121/wind_dir_deg", "unique_id": "Cotech-367959-121-WD", "device": {"identifiers": "Cotech-367959-121", "name": "Cotech-367959-121", "model": "Cotech-367959", "manufacturer": "rtl_433"}, "force_update": "true"}

Even after manually adding the MQTT sensor definitions in configuration.yaml and reviewing the incoming data messages using MQTT Explorer, still nothing appears in the sensor values.

1 post - 1 participant

Read full topic

I have an automation setup to fire based on the state of my “family” group changing to Away. If I delete and recreate the automation, it seems to work once but doesn’t trigger again after that point.

I’ve confirmed that the group.family entity is successfully reporting away:

YAML for the automation is below:

- id: '1641105629441'
  alias: 'Vacuum: start when away'
  description: ''
  trigger:
  - platform: state
    entity_id: group.family
    to: Away
  condition: []
  action:
  - device_id: c5b7e1cd14e602974d3967ea5eb95b2d
    domain: vacuum
    entity_id: vacuum.roborock_s7
    type: clean
  - service: notify.mobile_app_jons_iphone
    data:
      message: Vacuum triggered
      title: Vacuum triggered
  mode: single
  max: 10

I previously had conditions to only trigger the automation during certain hours but removed that hoping to solve the issue.

Thanks for your suggestions.

1 post - 1 participant

Read full topic

I have just discovered Home Assistant. I haven’t even installed it yet. I have a mix of hardware I have accumulated over the years with everything having it’s own interface. If I could manage from one app it would be awesome. I have a Homeseer Hometroller G1 witch is unsupported but operational. I have a bunch of Z-wave sensors connected to it. I have a garage door closer. I have a Topgreener IP switch. I have Sensi thermostat and 2 Nest thermostats. I have several generations of Foscam cameras. And I have a box of old x10 stuff. Can Home Assistant help me?
Thanks,
Chris

1 post - 1 participant

Read full topic

 Logger: homeassistant.components.nmap_tracker
Source: components/nmap_tracker/__init__.py:275
Integration: Nmap Tracker (documentation, issues)
First occurred: 17:31:42 (4 occurrences)
Last logged: 18:25:43
Nmap scanning failed: "nmap: Target.cc:503: void Target::stopTimeOutClock(const timeval*): Assertion `htn.toclock_running == true' failed.\n"

Any idea where to look for whats causing this error ???
latest HA-core running on a Odroid XU4 SBC, ubuntu 20.04 (32 bit octal core ARM SBC)
Thanks

1 post - 1 participant

Read full topic

so i been using TP Link Light switchs, and plugs it works well minus if the router needs a reboot or no power big deal… plus it works out of the box pair it with the phone then to the wifi and HA finds it… no need for this tuya app as the costco plugs switchs is a pain…

but i was looking at zigbee devices like Levition uses… and i wanted to stay away from costco plugs i cant desolder this stuff… and wanted to work out of the box… but what do you guys recommend

stick with Wifi? or if you got zigbee… what you guys find pros and cons? is it better to go zigbee way… i dont have a hub… and is there one better over the other…

all input is great… as i like the Easy Use of the TPLink devices i do find sometimes it looses connection and my plug will show off line… so i wanted to to try other routes too…
so i not soly stuck with TP-Link… and dont get me wrong they work great with HA

3 posts - 3 participants

Read full topic

I’m looking for a way to determine if I’m in a meeting with my microphone on, or if the webcam is on. I use Teams for work, but the integrations seem to only pull in Teams status, which isn’t that helpful because I’m in meetings most of the day, and so I’d really like a status to say if I’m actively talking (i.e. microphone mute is off) or if I’m on camera (webcam is in use).

Hass Workstation Service would be ideal for this, but I don’t have admin access to the company-owned laptop I use. What I really need is something that I don’t have to install, but can communicate microphone and webcam status over MQTT. Anyone have any ideas?

2 posts - 2 participants

Read full topic

Hi Team.

I have a Helper toggle button. How can i have Alexa set this to On or Off?

I am just looking to see how i expose this button to Alexa so that i can create a routine.

Thanks in advance

3 posts - 2 participants

Read full topic

Now that Google is going to start charging for their Google Workspace accounts, I’m taking a closer look at where my email is hosted. One of my requirements is for hosting service that is secure (privacy-focused) and has a calendar component. As of now, I have narrowed this down to Protonmail and Fastmail.

Looking through the integrations, the only calendar integration is for Google. Has anyone had any success integrating either Protonmail or Fastmail’s calendars? My use-case is on a table-based dashboard to display multiple calendars (one for each family member + shared).

2 posts - 2 participants

Read full topic

Hi,
I’m trying to get the EcoDim 0.5 to work in HA in general and MQTT specifically. My issues are:

1. After pairing the device does appear in in the Zigbee2MQTT list but not in the HA device list;
2. Pairing in Z2M results in error messages and finally that the device is not supported.

Before I paired the dimmer I:

1. Created a converter file in the Z2M directory with this code zigbee-herdsman-converters/ecodim.js at 89fd37d7fc0715e62fb6e62e83a9fc48cbb31fba · Koenkk/zigbee-herdsman-converters · GitHub. It includes the dimmer.
2. I amended the config file (added the converter and removed all the quotes

{
  external_converters: [ecodim.js],
  devices: [devices.yaml],
  groups: [groups.yaml],
  homeassistant: true,
  permit_join: true,
  mqtt:
    {
      base_topic: zigbee2mqtt,
      user: addons,
      password: wephoh3aeh1Il6da0iequ2ievu1shuT2Faethahf7aecooZiezae1ahBae3peo7c,
      server: mqtt://core-mosquitto:1883,
    },
  serial: { port: /dev/ttyACM0, adapter: deconz },
  advanced:
    {
      log_level: warn,
      pan_id: 6754,
      channel: 11,
      network_key: [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13],
      availability_blocklist: [],
      availability_passlist: [],
    },
  device_options: {},
  blocklist: [],
  passlist: [],
  queue: {},
  frontend: { port: 8099 },
  experimental: {},
}

However, after restarting Z2M, the original config is back again, without the converter and with the quotes.

What am I doing wrong?

2 posts - 2 participants

Read full topic

Are there any variables that can be used with notifications. For example, I have notifications configured in Hubitat cor when my front door opens but I leverage the %time% and %text% variable in Hubitat to place the time and what actually happened in the notification.

I want to start moving everything over to home assistant and was curious if there was anything similar with HA.

1 post - 1 participant

Read full topic

Hello HA-Friends,

I am desperately trying to create a “precipitation_probability” template sensor for my weather forecast integration “DWD”.

This is how all attributes of my entity “weather.dwd_weather_city” look like:

temperature: -0.2
humidity: 77
pressure: 1022.4
wind_bearing: 297
wind_speed: 27.8
visibility: 38.8
forecast:
  - datetime: '2022-01-20T00:00:00Z'
    condition: partlycloudy
    temperature: 1
    templow: -1
    precipitation: 0.6
    precipitation_probability: 72
  - datetime: '2022-01-21T00:00:00Z'
    condition: sunny
    temperature: 2
    templow: -4
    precipitation: 1.4
    precipitation_probability: 81
  - datetime: '2022-01-22T00:00:00Z'
    condition: rainy
    temperature: 5
    templow: 3
    precipitation: 6.1
    precipitation_probability: 80

As you can see, the “precipitation_probability” per day (today, tomorrow, day after tomorrow) is a child of the attribute “forecast” restricted by a “datetime”.
I was able to “filter” out the forecast-attribute by templating like this:

{{ (state_attr("weather.dwd_weather_city", "forecast"))}}

But the problem remains, that I can not extract the “precipitation_probability” of todays “datetime”.

Maybe some templating/jinja2-expert may help me with this problem?
Would be great, thanks in advance!

Best Regards

3 posts - 2 participants

Read full topic

Hello,
I created a garbage calender:

title: Müllabfuhr
type: vertical-stack
in_card: true
cards:
  - type: custom:button-card
    entity: sensor.abfall_bio
    layout: icon_name_state2nd
    show_label: true
    label: |
      [[[
        var days_to = entity.state.split("|")[1]
        if (days_to == 0)
        { return "Heute" }
        else if (days_to == 1)
        { return "Morgen" }
        else
        { return "in " + days_to + " Tagen" }
      ]]]
    show_name: true
    name: Abholung des Bioabfalls
    state:
      - color: red
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 0 ]]]'
      - color: orange
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 1 ]]]'
      - value: default
  - type: custom:button-card
    entity: sensor.abfall_restmuell
    layout: icon_name_state2nd
    show_label: true
    label: |
      [[[
        var days_to = entity.state.split("|")[1]
        if (days_to == 0)
        { return "Heute" }
        else if (days_to == 1)
        { return "Morgen" }
        else
        { return "in " + days_to + " Tagen" }
      ]]]
    show_name: true
    name: Abholung des Restabfalls
    state:
      - color: red
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 0 ]]]'
      - color: orange
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 1 ]]]'
      - value: default
  - type: custom:button-card
    entity: sensor.abfall_gelbersack
    layout: icon_name_state2nd
    show_label: true
    label: |
      [[[
        var days_to = entity.state.split("|")[1]
        if (days_to == 0)
        { return "Heute" }
        else if (days_to == 1)
        { return "Morgen" }
        else
        { return "in " + days_to + " Tagen" }
      ]]]
    show_name: true
    name: Abholung des Plastikabfalls
    state:
      - color: red
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 0 ]]]'
      - color: orange
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 1 ]]]'
      - value: default
  - type: custom:button-card
    entity: sensor.abfall_papier
    layout: icon_name_state2nd
    show_label: true
    label: |
      [[[
        var days_to = entity.state.split("|")[1]
        if (days_to == 0)
        { return "Heute" }
        else if (days_to == 1)
        { return "Morgen" }
        else
        { return "in " + days_to + " Tagen" }
      ]]]
    show_name: true
    name: Abholung des Papierabfalls
    state:
      - color: red
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 0 ]]]'
      - color: orange
        operator: template
        value: '[[[ return entity.state.split("|")[1] == 1 ]]]'
      - value: default

Now I want it to be sorted by days, so that the nearest is always a the top.
Is there a way to do this? In didn’t find anything usefull until now.

1 post - 1 participant

Read full topic

Hi,

I’ve installed a POPP 010101 (danfoss) z-wave radiator thermostat (I also use danfoss Ally).

I’m getting a strange issue on the air temperature reading. Occasionally it will report an extreme temperature. It’s not a major issue but it’s really messing with the feng shui of my temperature graphs.

Statistics table:

short term statistics table:

To me it looks like some weird issue parsing the number which I assume should be 18.44 C? Has anyone else seen it or something similar?

1 post - 1 participant

Read full topic