@borjamartinez wrote:

Hi,
You can now send WhatsApp messages using a free API:
https://www.callmebot.com/blog/whatsapp-text-messages-from-homeassistant/

The service is still in beta version but it is working well with a small delay (10 seconds aprox.)

It is super easy to use.

Posts: 1

Participants: 1

Read full topic

@killabee.nl wrote:

Hello,

I am trying to get my solar generated data from apsystems ema to homeassistant. Now i am doing this with a script that does a curl on the apsystems api and sends the data to pvoutput. In homeassistant I have the pvoutput configured and reads the data from there. But that are a couple of steps and I want to make this proces shorter.

When I do a cURL command in the commandline:

curl -H “Content-Type: application/x-www-form-urlencoded” http://api.apsystemsema.com:8073/apsema/v1/ecu/getPowerInfo -d ecuId=XXXXXXXXXXX -d filter=power -d date=20200406

Then I get the following JSON output:

{"data":{"time":"[\"05:36:25\",\"05:41:25\",\"05:46:25\",\"05:51:25\",\"05:56:25\",\"06:01:25\",\"06:06:25\",\"06:11:25\",\"06:16:25\",\"06:21:25\",\"06:26:25\",\"06:31:25\",\"06:36:25\",\"06:41:25\",\"06:46:25\",\"06:51:25\",\"06:56:25\",\"07:01:25\",\"07:06:25\",\"07:11:25\",\"07:16:25\",\"07:21:25\",\"07:26:25\",\"07:31:25\",\"07:36:25\",\"07:41:25\",\"07:46:25\",\"07:51:25\",\"07:56:25\",\"08:01:25\",\"08:06:25\",\"08:11:25\",\"08:16:25\",\"08:21:25\",\"08:26:25\",\"08:31:25\",\"08:36:25\",\"08:41:25\",\"08:46:25\",\"08:51:25\",\"08:56:25\",\"09:01:25\",\"09:06:25\",\"09:11:25\",\"09:16:25\",\"09:21:25\",\"09:26:25\",\"09:31:25\",\"09:36:25\",\"09:41:25\",\"09:46:25\",\"09:51:25\",\"09:56:25\",\"10:01:25\",\"10:06:25\",\"10:11:25\",\"10:16:25\",\"10:21:25\",\"10:26:25\",\"10:31:25\",\"10:36:25\",\"10:41:25\",\"10:46:25\",\"10:51:25\"]","power":"[\"6\",\"7\",\"14\",\"14\",\"15\",\"24\",\"31\",\"39\",\"46\",\"56\",\"70\",\"75\",\"83\",\"102\",\"115\",\"138\",\"395\",\"694\",\"789\",\"846\",\"892\",\"932\",\"968\",\"1012\",\"1044\",\"1078\",\"1111\",\"1137\",\"1169\",\"1195\",\"1217\",\"1235\",\"1253\",\"1279\",\"1298\",\"1317\",\"1328\",\"1210\",\"1335\",\"1371\",\"1382\",\"1393\",\"1400\",\"1407\",\"1416\",\"1429\",\"1452\",\"1470\",\"1493\",\"1519\",\"1538\",\"1561\",\"1593\",\"1617\",\"1648\",\"1674\",\"1706\",\"1732\",\"1763\",\"1788\",\"1817\",\"1849\",\"1872\",\"1893\"]"},"code":"1"}

Is it possible to use cURL or the restful sensor within Homeassistant in import these JSON data?

Maybe someone can push me in the right direction to fix this.

Posts: 3

Participants: 3

Read full topic

@chriselera wrote:

I’ve configured Z-wave as the built-in Z-wave integration in Home Assistant. When I was configuring it, I didn’t explicitly set a network key as it said that leaving it blank will auto-generate one for me. Now everything is working, including the lone secured device that I have (Schlage Conect Deadbolt).

Question is: how can I get the exact network key that was auto-generated for me?

Posts: 2

Participants: 2

Read full topic

@haakonstorm wrote:

I’m getting this error:

020-04-06 15:21:49 ERROR (MainThread) [custom_components.custom_icons.parser] file 'custom_icons/abc.svg' unsupported
2020-04-06 15:21:59 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]:  (See /config/configuration.yaml, line 47). 
2020-04-06 15:21:59 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]:  (See /config/configuration.yaml, line 47). 

Line 47 is my !include.
automation: !include_dir_merge_list automations

How can I locate the error when I have bunches of automations?

Posts: 6

Participants: 5

Read full topic

@Cobi wrote:

Hello,

Is anyone using broadlink to control an infrared kitchen hood. I’m looking for the codes of siemens LZ75956 remote control. It looks like this remote is share by other brands like Faber/Mepamsa, AEG, Franke, Smeg, Airlux…

700×434 23.8 KB

Thank you in advance for your help.

Posts: 3

Participants: 2

Read full topic

@Jokerigno wrote:

Hi all,

I tried without success to setup MariaDB as my db for HA.

This is what I’ve done (using this link):

Create a DB in MARIADB using console:

mysql -u root -p
CREATE DATABASE home_assistant;
CREATE USER ‘hass_user’ IDENTIFIED BY ‘xxxxxxxxxxxx’;
GRANT ALL PRIVILEGES ON home_assistant. TO ‘hass_user’@‘localhost’ IDENTIFIED BY ‘xxxxxxxxxxxxxx’;*
FLUSH PRIVILEGES;
exit

then added this in config:

recorder:
  purge_interval: 1
  db_url: !secret recorder_db_url
  purge_keep_days: 7
  include:
    domains:
    - sensor
    - climate
    - binary_sensor
    - light
    - timer
    # entities:
      # - sensor.consumo
  exclude:
    domains:
    - automation
    - script

where recorder_db_url is this:

recorder_db_url: ‘mysql://hass_user:xxxxxxxxxxx@192.168.2.100:3306/home_assistant?charset=utf8’

I checked for validation and reboot.

Record and other components (history, logbook) are no longer working.

This is the error in log:

Error during connection setup: (MySQLdb._exceptions.OperationalError) (1044, “Access denied for user ‘hass_user’@’%’ to database ‘home_assistant’”) (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)

Can someone please help me?

Thank you in advance!

Posts: 9

Participants: 2

Read full topic

@GoedGeluk wrote:

Hi,

In my configuration I created several Input_Boolean variables that I can turn on or off. Up till release 105 I could use them as conditions in my automations like:

- id: '0020200325004'
  alias: Mi 2 Motion
  trigger:
  - entity_id: binary_sensor.motion_sensor_158d0001e44955
    platform: state
    to: 'on'
  condition:
    condition: state
    entity_id: input_boolean.sendmimot2
    state: 'on'
  action:
  - data: {}
    entity_id: script.mi2_motion_delay
    service: script.turn_off
  - data:
      message: Motion Detected by Mi somewhere
      title: '*Motion Warning*'
    service: notify.tg_sendwarning
  - data: {}
    entity_id: script.mi2_motion_delay
    service: script.turn_on
  initial_state: true

Since I upgraded to release 107 the Actions in this automation are triggered always regardless of the state of the input_boolean used in the Condition.

Did I miss some breaking changes in the Release notes?

Any help would be appreciated.

Regards,

Marcel

Posts: 5

Participants: 3

Read full topic

@andyh6278 wrote:

Please help.

For some reason I am unable to access the UI on any machine. All I am getting come up is net::er_empty_response. I accidentally did a reboot(fat thumb syndrome) instead of hitting hardware from my phone whilst trying to add some devices now I have no access. Is there a way to force access please.

Thanks

Posts: 7

Participants: 3

Read full topic

@phsdv wrote:

I have some data that I want to get into HA. The input is quite long, so with the RESTfull integration I am over the 256 char limit. When using grep period I get all the data I am looking for see below:
(for the curious people, this is the output of a windturbine in Wh).

$ curl --silent https://zep-api.windcentrale.nl/production/2 | grep period

        <subset interval="HOUR" period="DAY" tstart="2020-04-06 00:00:00" tend="2020-04-06 23:59:00" sum="14632.255">
        <subset interval="DAY" period="MONTH" tstart="2020-04-01 00:00:00" tend="2020-04-30 00:00:00" sum="88488.797">
        <subset interval="DAY" period="WEEK" tstart="2020-03-31 00:00:00" tend="2020-04-06 00:00:00" sum="91294.59000000001">
        <subset interval="MONTH" period="YEAR" tstart="2020-01-01 00:00:00" tend="2020-12-31 00:00:00" sum="2189460.426">
        <subset interval="YEAR" period="LIFETIME" tstart="2013-01-01 00:00:00" tend="2020-12-31 00:00:00" sum="3.4027436681E7">

What I want to see in HA is for each different period the value of the sum. Thus I would like to get this:

somename.DAY= 14632.255
somename.MONTH=88488.797
...
somename.YEAR=3.4027436681E7

How to do this in HA? Any pointers is appreciated.
I have it working for DAY only with the use of curl|grep|awk|sed but it is a bit long commandline and only for 1 sum, not for all.

Posts: 3

Participants: 3

Read full topic

@RandomHassUser wrote:

I have a picture elements card with my camera and ptz arrows overlayed in the corner. Is there an option for a fullscreen button to overlay on the card as well?

If I use a picture-glance card with a live camera_view, I am able to click on the stream and then select fullscreen (but obviously I cannot use overlay buttons here)

What I want is to be able to have all my cameras as picture element cards in a view, then be able to individually fullscreen them.

I do know of panel view, but that isn’t a true fullscreen (as the header information is there). Is there an option or alternative to toggle fullscreen on a camera picture elements card?

Posts: 1

Participants: 1

Read full topic

@carsten_h wrote:

Hi!

Since two days, after running for hours without problems, when I try to get to the Home Assistant webpage I am only getting “loading data” and nothing more happens.
I am running the newest versions of HassOS and Home Assistant on a Pi 4B 4GB.

I tried it with Safari, Vivaldi, Opera and Chrome and also the iOS App and all showed the same behaviour.

I can go to the shell via ssh and reboot the Pi, because I have no knowledge what else can be done there. But that’s all.

Can someone help me here?

Posts: 11

Participants: 4

Read full topic

@FranzMaurer wrote:

Hi there, i cant handle this on my own Can someone point me to a resolution ?

Automation looks like this

- id: '1586175443173'
  alias: test
  description: ''
  trigger:
  - platform: template
    value_template: '{{ state_attr(''sensor.zielone'',''days'') == 1 }}'
  condition: []
  action:
  - data_template: >
      message: >
      {%- if {{ state_attr('sensor.zmieszane','days') == 1 }} -%}
      "Jutro wywóz śmieci {{ state_attr(''sensor.zmieszane'',''friendly_name'') }}"
      {%- elif {{ state_attr('sensor.zielone','days') == 1 }} -%}
      "Jutro wywóz śmieci {{ state_attr(''sensor.zielone'',''friendly_name'') }}"
      {%- elif {{ state_attr('sensor.segregowane','days') == 1 }} -%}
      "Jutro wywóz śmieci {{ state_attr(''sensor.segregowane'',''friendly_name'') }}"
      {%- else -%}
      "Dindu Nuffin"
      {%- endif -%}
    service: notify.smieci

And the error i get after configuration validation:

Invalid config for [automation]: expected a dictionary for dictionary value @ data['action'][0]['data_template']. Got None. (See /share/CE_CACHEDEV1_DATA/.qpkg/Home-Assistant/CONFIG_DIR/configuration.yaml, line 7).

That is completely unrelated cuz configuration.yaml, line 7 is:

group: !include groups.yaml

That was never a problem and will wanish when i delete the automation.

Posts: 8

Participants: 3

Read full topic

@mee wrote:

Hey guys!
i own a couple of those sensors and want to have an automation based on the current temperature.
But i noticed that its updating only every 5 minutes.

Do your know whether there is an option to increase that frequency?

General idea:
I like have alexa playing music when showering . Currently, I have two sensors, of which one tracks presence within the bathroom and another just for the shower. But I like to reduce it to one.
I could place it to notice presence everywhere, but than i dont know how it could distinguish between bathroom and shower.

Thanks a lot!

Posts: 1

Participants: 1

Read full topic

@Vasiliy wrote:

Hello.
Is it possible to solve this problem, using a generic thermostat?
It is necessary to control the temperature in the house, 2 floors. There is no physical thermostat, but there are controlled relays that regulate heating by floors separately.
I would like to make a separate night and day temperature, with the possibility of changing it from the hass interface.
At the moment, he sees the decision “out of the house”, turn it on at night. But the thermostat does not save the night temperature if you change it.

Posts: 1

Participants: 1

Read full topic

@Gerard_Smith wrote:

hi all I am new to aqara and recently purchased light bulbs and double wall switches and the hub the problem is I cannot connect the wall switches to the light bulbs. can anyone help

Posts: 2

Participants: 2

Read full topic

@maggggus wrote:

Hi!

I wonder how to set an attribute. I can succesfully use the attribute ‘mode’ in automation rules:

  - alias: 'EG_WohnZ Heizung Modus'
    initial_state: 'on'
    trigger:
      - platform: template
        value_template: "{{ is_state_attr('climate.eg_wohnz_hzg', 'mode', 'Auto') }}"
    action:
      - service: notify.notify
        data:
          message: 'EG_WohnZ_Hzg wurde auf Auto gestellt!'

how can I set the attribute ‘mode’ to the value ‘Manual’?

Posts: 3

Participants: 2

Read full topic

@chansearrington wrote:

Hey guys,

I’m trying to get a tuya device working with localtuya and currently running 107 in VM.

I’ve copied over the localtuya directory from @mileperhour and now have

config

custom_components

localtuya

switch.py
manifest.json
init.py
pytuya

init.py

I updated the switch.py code to have from . import pytuya

I’ve confirmed that the device ID, Local Key and IP address are all correct and working using TuyaCLI, where I’m able to successfully tun on the device.

But I’m still getting an error in the Developer Tools Logs

Log Details (ERROR)
Logger: homeassistant.components.switch
Source: custom_components/localtuya/switch.py:97
Integration: Switch (documentation, issues)
First occurred: 9:48:01 AM (1 occurrences)
Last logged: 9:48:01 AM

Error while setting up localtuya platform for switch
Traceback (most recent call last):
  File "/config/custom_components/localtuya/switch.py", line 93, in __get_status
    status = self._device.status()
  File "/config/custom_components/localtuya/pytuya/__init__.py", line 259, in status
    data = self._send_receive(payload)
  File "/config/custom_components/localtuya/pytuya/__init__.py", line 171, in _send_receive
    data = s.recv(1024)
ConnectionResetError: [Errno 104] Connection reset by peer

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 179, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/localtuya/switch.py", line 74, in setup_platform
    config.get(CONF_ID)
  File "/config/custom_components/localtuya/switch.py", line 127, in __init__
    self._status = self._device.status()
  File "/config/custom_components/localtuya/switch.py", line 111, in status
    self._cached_status = self.__get_status()
  File "/config/custom_components/localtuya/switch.py", line 97, in __get_status
    raise ConnectionError("Failed to update status.")
ConnectionError: Failed to update status.

Any ideas what this could be? How I might be able to fix it?

I have the following setup as a package for my config

###################################
# RecTec RT-700 Bull Package
###################################


###################################
# Climate
###################################


###################################
# Sensors
###################################

sensor:
 - platform: template
   sensors:
     rectec_target:
       value_template: >-
         {{ states.switch.rectec.attributes.target }}
       unit_of_measurement: 'F' 
     rectec_current:
       value_template: >-     
         {{ states.switch.rectec.attributes.current }}
       unit_of_measurement: 'F'      
     rectec_probea:
       value_template: >-
         {{ states.switch.rectec.attributes.probea }}
       unit_of_measurement: 'F'
     rectec_probeb:
       value_template: >-
         {{ states.switch.rectec.attributes.probeb }}
       unit_of_measurement: 'F'


###################################
# switch
###################################

switch:
  - platform: localtuya
    host: !secret rectec_host
    local_key: !secret rectec_local_key
    device_id: !secret rectec_device_id
    name: smoker

Posts: 1

Participants: 1

Read full topic

@jolaca wrote:

Hi, I have migrated my Hassbian installation from a Pi3 to Hass.io and then to a Pi4. I’ve been able to restore all my integrations without issues, all but Nest. I was asked to link my nest account, and authorize Nest integration, I entered the link to do so: received a Pin in my mobile, entered that pin in nest page and after giving my authorization in their page I get from the same web page: ‘Upps there’s been a problem, try again!’ Getting that error when I enter the same pin in HA, obviously it does not work.
No idea why this is happening, but I have tried several times with no success. BTW, I already had a nest developer account (and was working on Hassbian), so I guess it’s not related to that.

Any idea will be very much appreciated. It seems that the normal way to authorize this integration is not working anymore.

Posts: 1

Participants: 1

Read full topic

@mknybel wrote:

HI , appreciate crosscheck and help to beginner.
Story: measure energy consumption locally - charts. etc…
Plan: buy 3 phase consumption Energy Meter (Modbus, RS 485) + RS485 to USB and Raspberry PI

How then manage the data flow.
Home assistant with Modbus configuraiton (https://www.home-assistant.io/integrations/modbus/)
then Node Red to define data flow ?
and then InfluxDB & Grafana ?

thanks for help
Martin

Posts: 1

Participants: 1

Read full topic

@sz0wxc wrote:

How does the homekit integration differ from the non-homekit integration for ecobee.

Does the homekit only utilize local network and not require external access. Seems that am missing some sensor data with the homekit integration where when I use the other method I get weather and all the sensor data I am looking for.

Posts: 2

Participants: 2

Read full topic