Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 109599 articles
Browse latest View live

Lutron Caseta - Transition, Flash

$
0
0

@jazzyisj wrote:

Anybody have “transition” or “flash” working with Lutron Caseta lights?

Neither of these work for me.

 - service: light.turn_on
   data:
     entity_id: light.living_room_pot_lights
     transition: 60

 - service: light.turn_on
   data:
     entity_id: light.living_room_pot_lights
     flash: short

Posts: 1

Participants: 1

Read full topic


Failed to setup smart life

$
0
0

@henry8866 wrote:

I’m using smart life app in iOS to manager a few smart plugs. Tried to setup with this guide https://www.home-assistant.io/integrations/tuya/ but got this error:
“tuyaha.tuyaapi.TuyaAPIException: Get accesstoken failed. Username or password error!”

I tested on my app, the username, password works fine. But I can’t login on tuya.com website. Anyone has similar issue? How to fix it?

Thanks.

Posts: 3

Participants: 2

Read full topic

Playing Local GH Doorbell Sound on HASS - Ubuntu running on laptop

$
0
0

@Sabellwind wrote:

I’ve been battling this issue for a few days now. Every other forum post I’ve read seems to have it working locally by pointing their config to the www folder. I had to create a www folder because it wasn’t there by default. I’m running this on a Ubuntu and not hass.io on a pi.

My automation yaml is:

- alias: 'Doorbell'
  initial_state: 'on'
  trigger:
    platform: event
    event_type: deconz_event
    event_data:
      id: smart_switch
      event: 1000
  action:
    # service: tts.google_translate_say
    service: media_player.play_media
    data: 
      entity_id: media_player.all_speakers
    #   message: 'Ding Dong, someone is at the door'
      media_content_id: http://xxx.xxx.x.xx:8123/home/angelo/.homeassistant/www/audio/doorbell.mp3
      media_content_type: 'music'

and my target sound file is here:
image

The commented out TTS works, so I believe the issue here is that HA can’t find doorbell.mp3 file. What am I doing wrong?

Posts: 5

Participants: 3

Read full topic

Hanafi --- islamic_prayer_time

$
0
0

@Gadgets wrote:

As-Salaam and good day.

I am trying to make the islamic_prayer_time sensor.py accept “school” as a parameter.

I took the original sensor.py code from GitHub, but I cant get it to work. Can anyone help. Here is my code:
`
“”“Platform to retrieve Islamic prayer times information for Home Assistant.”""
import logging
from datetime import datetime, timedelta

import voluptuous as vol

import homeassistant.helpers.config_validation as cv
import homeassistant.util.dt as dt_util
from homeassistant.components.sensor import PLATFORM_SCHEMA
from homeassistant.const import DEVICE_CLASS_TIMESTAMP
from homeassistant.helpers.entity import Entity
from homeassistant.helpers.event import async_track_point_in_time

_LOGGER = logging.getLogger(name)

PRAYER_TIMES_ICON = “mdi:calendar-clock”

SENSOR_TYPES = [“fajr”, “sunrise”, “dhuhr”, “asr”, “maghrib”, “isha”, “midnight”]

CONF_CALC_METHOD = “calculation_method”
CONF_CALC_SCHOOL = “calculation_school”
CONF_SENSORS = “sensors”

CALC_METHODS = [“karachi”, “isna”, “mwl”, “makkah”]
DEFAULT_CALC_METHOD = “isna”
CALC_SCHOOL = [“0”, “1”]
DEFAULT_CALC_SCHOOL =“0”
DEFAULT_SENSORS = [“fajr”, “dhuhr”, “asr”, “maghrib”, “isha”]

PLATFORM_SCHEMA = PLATFORM_SCHEMA.extend(
{
vol.Optional(CONF_CALC_METHOD, default=DEFAULT_CALC_METHOD): vol.In(
CALC_METHODS
),
vol.Optional(CONF_CALC_SCHOOL, default=DEFAULT_CALC_SCHOOL): vol.In(
CALC_SCHOOL
),
vol.Optional(CONF_SENSORS, default=DEFAULT_SENSORS): vol.All(
cv.ensure_list, vol.Length(min=1), [vol.In(SENSOR_TYPES)]
),
}
)

async def async_setup_platform(hass, config, async_add_entities, discovery_info=None):
“”“Set up the Islamic prayer times sensor platform.”""
latitude = hass.config.latitude
longitude = hass.config.longitude
calc_method = config.get(CONF_CALC_METHOD)
calc_school = config.get(CONF_CALC_SCHOOL)

if None in (latitude, longitude):
    _LOGGER.error("Latitude or longitude not set in Home Assistant config")
    return

prayer_times_data = IslamicPrayerTimesData(latitude, longitude, calc_method, calc_school)

prayer_times = prayer_times_data.get_new_prayer_times()

sensors = []
for sensor_type in config[CONF_SENSORS]:
    sensors.append(IslamicPrayerTimeSensor(sensor_type, prayer_times_data))

async_add_entities(sensors, True)

# schedule the next update for the sensors
await schedule_future_update(
    hass, sensors, prayer_times["Midnight"], prayer_times_data
)

async def schedule_future_update(hass, sensors, midnight_time, prayer_times_data):
“”"Schedule future update for sensors.

Midnight is a calculated time.  The specifics of the calculation
depends on the method of the prayer time calculation.  This calculated
midnight is the time at which the time to pray the Isha prayers have
expired.

Calculated Midnight: The Islamic midnight.
Traditional Midnight: 12:00AM

Update logic for prayer times:

If the Calculated Midnight is before the traditional midnight then wait
until the traditional midnight to run the update.  This way the day
will have changed over and we don't need to do any fancy calculations.

If the Calculated Midnight is after the traditional midnight, then wait
until after the calculated Midnight.  We don't want to update the prayer
times too early or else the timings might be incorrect.

Example:
calculated midnight = 11:23PM (before traditional midnight)
Update time: 12:00AM

calculated midnight = 1:35AM (after traditional midnight)
update time: 1:36AM.

"""
_LOGGER.debug("Scheduling next update for Islamic prayer times")

now = dt_util.as_local(dt_util.now())
today = now.date()

midnight_dt_str = "{}::{}".format(str(today), midnight_time)
midnight_dt = datetime.strptime(midnight_dt_str, "%Y-%m-%d::%H:%M")

if now > dt_util.as_local(midnight_dt):
    _LOGGER.debug(
        "Midnight is after day the changes so schedule update "
        "for after Midnight the next day"
    )

    next_update_at = midnight_dt + timedelta(days=1, minutes=1)
else:
    _LOGGER.debug(
        "Midnight is before the day changes so schedule update for the "
        "next start of day"
    )

    tomorrow = now + timedelta(days=1)
    next_update_at = dt_util.start_of_local_day(tomorrow)

_LOGGER.debug("Next update scheduled for: %s", str(next_update_at))

async def update_sensors(_):
    """Update sensors with new prayer times."""
    # Update prayer times
    prayer_times = prayer_times_data.get_new_prayer_times()

    _LOGGER.debug("New prayer times retrieved.  Updating sensors.")

    # Update all prayer times sensors
    for sensor in sensors:
        sensor.async_schedule_update_ha_state(True)

    # Schedule next update
    await schedule_future_update(
        hass, sensors, prayer_times["Midnight"], prayer_times_data
    )

async_track_point_in_time(hass, update_sensors, next_update_at)

class IslamicPrayerTimesData:
“”“Data object for Islamic prayer times.”""

def __init__(self, latitude, longitude, calc_method, calc_school):
    """Create object to hold data."""
    self.latitude = latitude
    self.longitude = longitude
    self.calc_method = calc_method
self.calc_school = calc_school
    self.prayer_times_info = None

def get_new_prayer_times(self):
    """Fetch prayer times for today."""
    from prayer_times_calculator import PrayerTimesCalculator

    today = datetime.today().strftime("%Y-%m-%d")

    calc = PrayerTimesCalculator(
        latitude=self.latitude,
        longitude=self.longitude,
        calculation_method=self.calc_method,
        calculation_school=self.calc_school,
        date=str(today),
    )

    self.prayer_times_info = calc.fetch_prayer_times()
    return self.prayer_times_info

class IslamicPrayerTimeSensor(Entity):
“”“Representation of an Islamic prayer time sensor.”""

ENTITY_ID_FORMAT = "sensor.islamic_prayer_time_{}"

def __init__(self, sensor_type, prayer_times_data):
    """Initialize the Islamic prayer time sensor."""
    self.sensor_type = sensor_type
    self.entity_id = self.ENTITY_ID_FORMAT.format(self.sensor_type)
    self.prayer_times_data = prayer_times_data
    self._name = self.sensor_type.capitalize()
    self._device_class = DEVICE_CLASS_TIMESTAMP
    prayer_time = self.prayer_times_data.prayer_times_info[self._name]
    pt_dt = self.get_prayer_time_as_dt(prayer_time)
    self._state = pt_dt.isoformat()

@property
def name(self):
    """Return the name of the sensor."""
    return self._name

@property
def icon(self):
    """Icon to display in the front end."""
    return PRAYER_TIMES_ICON

@property
def state(self):
    """Return the state of the sensor."""
    return self._state

@property
def should_poll(self):
    """Disable polling."""
    return False

@property
def device_class(self):
    """Return the device class."""
    return self._device_class

@staticmethod
def get_prayer_time_as_dt(prayer_time):
    """Create a datetime object for the respective prayer time."""
    today = datetime.today().strftime("%Y-%m-%d")
    date_time_str = "{} {}".format(str(today), prayer_time)
    pt_dt = dt_util.parse_datetime(date_time_str)
    return pt_dt

async def async_update(self):
    """Update the sensor."""
    prayer_time = self.prayer_times_data.prayer_times_info[self.name]
    pt_dt = self.get_prayer_time_as_dt(prayer_time)
    self._state = pt_dt.isoformat()

`

Posts: 1

Participants: 1

Read full topic

How to add BLE and get it value to Hassio?

$
0
0

@forted.exe wrote:

I try to google it but no clues, can some one point me where I should start ?
Note: my device is not in HA integrations
Example: I have an BLE device sensor, and it dont list in HA integrations, how can I make it connect with HA and receive it data ?
In my case, I has JDY 08 BLE attatched to globe sensor, I can run and get it value with terminal, but I dont know what to write in to configuration.yaml or automation/trigger
The way I get ble data to hassio is according to this https://learn.adafruit.com/reverse-engineering-a-bluetooth-low-energy-light-bulb/control-with-bluez

Posts: 3

Participants: 2

Read full topic

BLE tracker still not working

$
0
0

@smugleafdev wrote:

I have the BLE tracker set up and it’s still not detecting my phones as home. It detected my two phones at least once or they wouldn’t be in the known_devices.yaml. I have about a hundred of these lines in my log, so I know it’s at least sort of working:

2019-11-09 22:38:08 DEBUG (SyncWorker_14) [homeassistant.components.bluetooth_le_tracker.device_tracker] Adding BLE_58:CB:52:12:2C:A9 to BLE tracker
2019-11-09 22:38:08 DEBUG (SyncWorker_14) [homeassistant.components.bluetooth_le_tracker.device_tracker] Adding BLE_8C:8E:F2:D8:7D:E8 to BLE tracker
2019-11-09 22:38:08 DEBUG (SyncWorker_14) [homeassistant.components.bluetooth_le_tracker.device_tracker] Adding BLE_59:99:99:0B:5F:E3 to BLE do not track
2019-11-09 22:38:08 DEBUG (SyncWorker_14) [homeassistant.components.bluetooth_le_tracker.device_tracker] Adding BLE_F9:0E:94:4D:42:AE to BLE do not track

My config:

device_tracker:
  - platform: bluetooth_le_tracker
    interval_seconds: 60
    consider_home: 180
    track_new_devices: false

Yes I’m sure BT is on 24/7 on my devices (one Android, one iPhone). Wifi tracking is working great for the Android device; flawlessly actually. It’s awful with the iPhone which is why I’m even bothering with BTLE. What am I missing?

Posts: 3

Participants: 2

Read full topic

Samba connection

$
0
0

@Fredrik_Jacobsson wrote:

Hi,
I have problem with connection to Hassio via Samba.
I have following confoguration.

{
  "workgroup": "FREDDAGROUP",
  "username": "Fredda",
  "password": "Secret",
  "interface": "",
  "allow_hosts": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/16"
  ],
  "veto_files": [
    "._*",
    ".DS_Store",
    "Thumbs.db",
    "icon?",
    ".Trashes"
  ]
}

And this how the logfile looks like:

[08:14:46] INFO: Hostname: Fredda-Hassio
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user Fredda.
nmbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface eno1 ip=10.0.1.3 bcast=10.0.1.255 netmask=255.255.255.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
making subnet name:172.30.32.1 Broadcast address:172.30.33.255 Subnet mask:255.255.254.0
making subnet name:10.0.1.3 Broadcast address:10.0.1.255 Subnet mask:255.255.255.0
making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface eno1 ip=10.0.1.3 bcast=10.0.1.255 netmask=255.255.255.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections

But I can not connect to Hassio from my windows machine.
Do I need to specify the “interface”?
How do I know what the interface is?
I’m running Hassio in a Docker on a Ubuntu machine.

Posts: 4

Participants: 2

Read full topic

Owner locked out by allow_bypass_login

$
0
0

@Peter_M wrote:

To avoid the login procedure of home assistant I wanted to use the trusted networks athentication provider. Because I don’t want the trusted user to be the ‘owner’ I created a second ‘user’ account which I added in the configuration as shown below.

homeassistant:
  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 192.168.3.0/24
      trusted_users:
        192.168.3.0/24: my_user_id
      allow_bypass_login: true
    - type: homeassistant

This does what I want for daily use, but unfortunately this also locks out the ‘owner’ user. I’m not able to login to home assistant manually. I hoped this would be possible by logging out after the automatic login but this doesn’t seem the case.

Is there a way to achieve this by changing my configuration? Or is there an url on the home assistant server I can access to bypass the automatic login and use user/password authentication to login with my ‘owner’ account?

Posts: 3

Participants: 2

Read full topic


Nmap device tracker new ISP

$
0
0

@Fredrik13 wrote:

I have just changed isp and got new ip-addresses in my network. HA is up and running but Nmap tracker is not working. None of the devices are home. I changed the ip range to scan in the configuration and have tried to delete known_devices.yaml.
Still the same and no known_devices file is created.
How can I remove all the old devices and rescan the network for my devices?

Posts: 1

Participants: 1

Read full topic

Jewish calendar showing wrong times

$
0
0

@Shahar_Kakooli wrote:

Hi.
I’m new to this great community.
I added the jewish calendar to my configuraton file, and the time it is showing for lighting candles and all the rest is wrong.
my configuration:

default_config:
homeassistant:
  name: Gedera
  latitude: 31.81456
  longitude: 34.77998
  time_zone: Asia/Jerusalem
  unit_system: metric
  elevation: 67
  customize: !include customize.yaml

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

sensor:
  - platform: time_date
    display_options:
     - date_time
  - platform: systemmonitor
    resources:
     - type: disk_use_percent
     - type: memory_use_percent
     - type: ipv4_address
     - type: processor_use
     - type: last_boot

jewish_calendar:
  language: hebrew
  candle_lighting_minutes_before_sunset: 40

smartir:


frontend:
  themes: !include themes.yaml

it’s very important for me to use this feature.
Currently, it shows me that the time for lighting candle in shabbat is 2019-11-15 14:02:00+00:00, and havdalah time is - 2019-11-16 15:20:00+00:00
The date and time of the system is correct.
i’m using version 2.12 (stable), and recently updated the hassio system to version 0.101.3.
Thank you in advance!

Posts: 1

Participants: 1

Read full topic

Sending sensor data to ifttt

$
0
0

@chocolatejoe wrote:

Im trying to send sensor data from a power meter periodically to a google sheets spreadsheet via ifttt.

can someone please enlighten me where i am wrong, the following json gets me the numerical value of the sensor in templates but purely sends it as text in the automation.

- id: '1573218181707'
  alias: Sensor to ifttt
  description: ''
  trigger:
  - hours: ''
    minutes: '1'
    platform: time_pattern
    seconds: ''
  condition: []
  action:
  - data:
      event: event_name
      value1: "{{ states('sensor.main_board_ct1_watts')}}"
    service: ifttt.trigger

Posts: 2

Participants: 2

Read full topic

Can't login to hassbians frontend

$
0
0

@roamer57 wrote:

Hi, I have installed Hassbian on a rpi3 and I can login via Putty to Hassbian and it says it is active, but when I try to log in via my web browser at rpi3 ip address I get 404: not found, and in the addressbar is says not secure.
I had a working Home assistant earlier but the sd card broke and now I am trying to get a fresh install but no luck so far.
Any help is appreciated.
Greatings Ronny

Posts: 2

Participants: 2

Read full topic

Remove Space between entities card

$
0
0

@AdmiralRaccoon wrote:

Hi there,
This card should list me some system stats. At the End of the card, there are also some conditions, to show the status of my 3 NAS only when they´re turned on, and it looks like this:

Why is there so much space between the entry “HA Database Size” and the Diskstation-sensors and how can I reduce them to aliign correct to the other entries?

Here is the code:

cards:
  - color: 'rgb(223, 255, 255)'
    color_type: label-card
    name: system stats
    styles:
      card:
        - height: 15px
    tap_action:
      action: navigate
      navigation_path: /lovelace/7
    type: 'custom:button-card'
  - cards:
      - entities:
          - entity: sensor.speedtest_download
          - sensor.speedtest_upload
          - binary_sensor.fritzbox_connectivity
          - entity: sensor.fb7590uptime
            icon: 'mdi:clock'
            name: Fritzbox 7590
          - entity: sensor.ha_uptime
            name: Hassio
          - entity: sensor.nucuptime
            icon: 'mdi:clock'
            name: NUC
          - entity: sensor.omvuptime
            icon: 'mdi:clock'
            name: OpenMediaVault
          - entity: sensor.db_size
            icon: 'mdi:database'
            name: HA Database Size
        show_header_toggle: false
        title: null
        type: entities
    type: vertical-stack
  - cards:
      - card:
          entities:
            - entity: sensor.ds3status
              icon: 'mdi:database'
              name: Diskstation3
          type: entities
        conditions:
          - entity: switch.diskstation3
            state: 'on'
        type: conditional
      - card:
          entities:
            - entity: sensor.ds2status
              name: Diskstation2
          type: entities
        conditions:
          - entity: switch.diskstation2
            state: 'on'
        type: conditional
      - card:
          entities:
            - entity: sensor.ds1status
              name: Diskstation1
          type: entities
        conditions:
          - entity: switch.diskstation1
            state: 'on'
        type: conditional
    type: vertical-stack
type: vertical-stack

Posts: 2

Participants: 1

Read full topic

Is my CC2531 broken?

$
0
0

@JJussi wrote:

Hi!
I have CC2531 USB stick what is flashed with CC2531_DEFAULT_20190608.zip

Stick is connected to Raspberry Pi 4 where hass.io ver: 192 is running.

I have: # Zigbee2mqtt Hass.io Add-on 1.6.0

Config:
{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": true,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://a0d7b954-mqtt",
    "user": "mqtt",
    "password": "mqtt"
  },
  "serial": {
    "port": "/dev/ttyACM0"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ],
    "availability_blacklist": []
  },
  "ban": [],
  "whitelist": [],
  "queue": {},
  "socat": {
    "enabled": false,
    "master": "pty,raw,echo=0,link=/dev/ttyZ2M,mode=777",
    "slave": "tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5",
    "restartdelay": 1,
    "initialdelay": 1,
    "options": "-d -d",
    "log": false
  }
}

Log file says:

./run.sh: line 16: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
[Info] Socat is DISABLED and not started
2019-11-10T12:37:38: PM2 log: Launching in no daemon mode
2019-11-10T12:37:38: PM2 log: App [npm:0] starting in -fork mode-
2019-11-10T12:37:38: PM2 log: App [npm:0] online
> zigbee2mqtt@1.6.0 start /zigbee2mqtt-1.6.0
> node index.js
  zigbee2mqtt:info 11/10/2019, 12:37:41 PM Logging to directory: '/share/zigbee2mqtt/log/2019-11-10.12-37-41'
  zigbee2mqtt:info 11/10/2019, 12:37:42 PM Starting zigbee2mqtt version 1.6.0 (commit #unknown)
  zigbee2mqtt:info 11/10/2019, 12:37:42 PM Starting zigbee-shepherd
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM zigbee-shepherd started
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM Coordinator firmware version: '20190608'
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM Currently 0 devices are joined:
  zigbee2mqtt:warn 11/10/2019, 12:37:43 PM `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 11/10/2019, 12:37:43 PM Allowing new devices to join.
  zigbee2mqtt:warn 11/10/2019, 12:37:43 PM Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM Connecting to MQTT server at mqtt://a0d7b954-mqtt
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM zigbee-shepherd ready
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM Connected to MQTT server
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 11/10/2019, 12:37:43 PM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.6.0","commit":"unknown","coordinator":20190608,"log_level":"info","permit_join":true}'
  zigbee2mqtt:info 11/10/2019, 12:40:23 PM Successfully reenabled joining
  zigbee2mqtt:info 11/10/2019, 12:43:03 PM Successfully reenabled joining

Green led on the stick is constantly burning.

I have tried to join multiple different devices, but I cannot get any other lines to log file… No errors and no any pairing lines like:

Successfully interviewed ‘0x00158d0001dc126a’, device has successfully been paired

I have also tried to use https://github.com/Frans-Willem/AqaraHub and no success.

So… is my USB stick faulty? (from aliexpress)
Can I some way to do “debug” of the stick?

Posts: 2

Participants: 2

Read full topic

Camera.record Stream/record not ending/saving

$
0
0

@djansen1987 wrote:

Hi All,

I used to have an automation what send an photo via Telegram whenever the door opens.
This work great, only issue is that it is way to quick so i did not see who walked in as the photo was already taken.

So now i read some blogs and the advice was to use camera.record instead of camera.snapshot. Only i can’t get it to work. First issue was i did not install Stream and additional packages. But those are fixed. Now when i run my automation it doesn’t do anything (for what i can see). When i run the automation again it tells me it is already recording.

I already changed the duration time to “2” to make sure i was not to quick. But no joy.

Error log shows me:

Log Details (ERROR)
Sun Nov 10 2019 14:55:24 GMT+0100 (Central European Standard Time)
Error while executing automation automation.voordeur_notificatie. Unknown error for call_service at pos 2:
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/automation/init.py”, line 437, in action
await script_obj.async_run(variables, context)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/script.py”, line 190, in async_run
await self._handle_action(action, variables, context)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/script.py”, line 274, in _handle_action
await self._actions[_determine_action(action)](action, variables, context)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/script.py”, line 357, in _async_call_service
context=context,
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/service.py”, line 97, in async_call_from_config
domain, service_name, service_data, blocking=blocking, context=context
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py”, line 1236, in async_call
await asyncio.shield(self._execute_service(handler, service_call))
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py”, line 1261, in _execute_service
await handler.func(service_call)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py”, line 213, in handle_service
self._platforms.values(), func, call, service_name, required_features
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/service.py”, line 348, in entity_service_call
future.result() # pop exception if have
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/service.py”, line 372, in _handle_service_platform_call
await func(entity, data)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/camera/init.py”, line 712, in async_handle_record_service
DOMAIN_STREAM, SERVICE_RECORD, data, blocking=True, context=call.context
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py”, line 1236, in async_call
await asyncio.shield(self._execute_service(handler, service_call))
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py”, line 1261, in _execute_service
await handler.func(service_call)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/stream/init.py”, line 132, in async_record
await async_handle_record_service(hass, call)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/stream/init.py”, line 237, in async_handle_record_service
raise HomeAssistantError(f"Stream already recording to {recorder.video_path}!")
homeassistant.exceptions.HomeAssistantError: Stream already recording to /home/homeassistant/.homeassistant/secure/voordeur.mp4!

My automation is not so exciting but here is the config.

- id: test123
  alias: Voordeur Notificatie
  trigger:
  - entity_id: binary_sensor.door_window_sensor_158d0002e8b414
    from: 'off'
    platform: state
    to: 'on'
  action:
  - data:
      message: '{{now().strftime("%H:%M %Y-%m-%d")}}: Voor deur is open geweest.'
      title: '*Voordeur sensor is getriggerd*'
    service: notify.telegramdaniel
  - data:
      duration: 2
      entity_id: camera.gang
      filename: /home/homeassistant/.homeassistant/secure/voordeur.mp4
    service: camera.record

The path where it saves is my secure path:

homeassistant:
  # Name of the location where Home Assistant is running
  # name: Home
  # Location required to calculate the time the sun rises and sets
  # latitude: 52.028213
  # longitude: 5.046502
  # Impacts weather/sunrise data (altitude above sea level in meters)
  # elevation: 0
  # metric for Metric, imperial for Imperial
  # unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  # time_zone: Europe/Amsterdam
  # Customization file
  customize: !include customize.yaml
  whitelist_external_dirs:
    - /home/homeassistant/.homeassistant/secure
# lovelace:
#   mode: yaml

Hope anyone can see where i am going wrong.
Thanks!

Posts: 1

Participants: 1

Read full topic


Problems with google home / nest hub / stream component with router change

$
0
0

@vlaraort wrote:

Hi there!

I am using a Home Assistant instance, running in 0.100.3 version in a python virtual env.

I have changed my main router (ISP ONT+Router) to a Asus AC68U + separate ONT, currently everything is working as intended

I have the manual google assistant integration configured, exposing several lights, and they are working

My external access is configured with duckdns and letsencrypt, the asus router automatically enables nat loopback, so I am able to access to https://home.mydomain.duckdns.org:8123 from outside and inside of my network, without certificate problems.

The problem is now with the nest hub and the google home minis. When I try to use tts in any of the google devices, the “bling” sounds, but nothing is said, I have tryied from the frontend and from an automation an it does not work, a chromecast icon is displayed in the hub, the status changes to idle, but nothing sounds. There are no logs at all about something happened.

Also, when I try to cast a camera exposed to google home (with the stream component properly setted up), the “bling” also sounds, but only a “Smart home Camera” string is displayed, and there is no video at all. This has been tested in a nest hub and a MIBOX3, and the problem is the same

Previously, with my ISP router, everything works, so this should be something related to a network configuration, but I can’t find anything regarding needed configurations or ports mandatories to make this work.

this is my camera configuration (custom firmware dafang), it works in the frontend with the stream enabled, and the stream worked before the router change

camera:
  - platform: generic
    name: dafang camera
    still_image_url: https://192.168.1.140/cgi-bin/currentpic.cgi
    stream_source: rtsp://192.168.1.140:8554/unicast
    verify_ssl: false
    username: root
    password:  *****
    authentication: basic

I don’t have any configuration for the nest hub / google homes, they are automatically discovered by HA and they appear as media_players in my entities

image

More info: the casting from another sources works properly, also the home assistant cast is working properly, so it smells like some kind of internal configuration in the network is not working, because the only issue is from local network to local network.

Can someone show me some light, or maybe some ideas about how to trace this problem?

Regards!

Posts: 1

Participants: 1

Read full topic

Qubino (Goap) ZMNHBDx Flush 2 Relays - Switch entities missing!?

$
0
0

@antonpettersson wrote:

Hi community!

I got two Qubino units. One Dimmer and one dual relay. The dimmer works fine but the dual relay seem to have missing entities.

Qubino (Goap) ZMNHDD1 Flush Dimmer:
zwave.qubino_zmnhdd1_flush_dimmer
sensor.qubino_zmnhdd1_flush_dimmer_power
sensor.qubino_zmnhdd1_flush_dimmer_exporting
sensor.qubino_zmnhdd1_flush_dimmer_sourcenodeid
sensor.qubino_zmnhdd1_flush_dimmer_power_management
switch.qubino_zmnhdd1_flush_dimmer_switch
sensor.qubino_zmnhdd1_flush_dimmer_energy
sensor.qubino_zmnhdd1_flush_dimmer_alarm_type
sensor.qubino_zmnhdd1_flush_dimmer_alarm_level
light.qubino_zmnhdd1_flush_dimmer_level

Qubino (Goap) ZMNHBDx Flush 2 Relays:
zwave.qubino_goap_zmnhbdx_flush_2_relays_2
sensor.qubino_goap_zmnhbdx_flush_2_relays_energy_4
sensor.qubino_goap_zmnhbdx_flush_2_relays_energy_5
sensor.qubino_goap_zmnhbdx_flush_2_relays_energy_6
sensor.qubino_goap_zmnhbdx_flush_2_relays_power_4
sensor.qubino_goap_zmnhbdx_flush_2_relays_power_5
sensor.qubino_goap_zmnhbdx_flush_2_relays_power_6

Im missing something like this:
switch.qubino_goap_zmnhbdx_flush_2_relays_switch_4
switch.qubino_goap_zmnhbdx_flush_2_relays_switch_5
switch.qubino_goap_zmnhbdx_flush_2_relays_switch_6

Is there a genius out there that know whats going on?

Posts: 1

Participants: 1

Read full topic

Return light to previous state after automation

$
0
0

@arti wrote:

Hello everyone, what is the best way to remember current light (state, colour, brightness) and return it later in automation or script if required? I thought I would hold global variables as MQTT sensors, so in automation I’m able to save state but I’m unable to apply settings to the light when needed.

Posts: 2

Participants: 2

Read full topic

Proper way to implement “variables” or virtual devices?

$
0
0

@nick67 wrote:

I’m trying to figure out the most HA-appropriate way to store and edit arbitrary values - i.e. variables.

Example: guest mode

I want a virtual switch in Lovelace that lets me set a Boolean for whether or not I have guests visiting. This Boolean will interact with the rest of the system in 2 ways:

  • I’ll have automations listening for a Boolean state change that will do some things as soon as this switch is flipped
  • Other automations will have this Boolean as a condition, and only run if guests aren’t here

Example: ideal brightness

  • I want to store an integer ideal light brightness based on time of day. A series of automations would set this “ideal brightness” variable to 60 at sunset, 15 when I press my goodnight button, 40 at 6am, and 100 an hour after sunrise.
  • When I turn on a light, the brightness in the turn on automation will be templates off of this ideal brightness variable.
  • Unlike the guest Boolean, I don’t need to expose or edit this variable in the UI

Are these “variables” both virtual sensors of some kind? (One a binary sensor, one a numeric sensor). If so how do I create arbitrary virtual sensors and how do I update them? Am I thinking about this architecture all wrong for the HA paradigm?

Posts: 3

Participants: 3

Read full topic

Nexa ZV-9101

$
0
0

@Henrik1986 wrote:

Hi! I installed a Nexa ZV-9101 and it’s working but I have a problem.

When i turn off the light on the wall switch and the brightness is low Hass.io change the boolean to off. But if i turn off the light on the wall switch and the brightness is high Hass.io don’t change the boolean to off.

Posts: 1

Participants: 1

Read full topic

Viewing all 109599 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>