@mstudent100 wrote:

Integrating my boiler system into HA. Got most everything working, i.e. boiler lockout over 60 degrees F, single device zones working properly. ESPhome based. Master bedroom has 2 zone valves that I’m trying to put onto 2 separate relays as follows:

 - platform: generic_thermostat
    name: Master bedroom
    heater: switch.relay_channel_1
    heater: switch.relay_channel_2
    target_sensor: sensor.lumi_lumi_weather_28344b04_temperature
    min_temp: 62
    max_temp: 75

Works, but only brings on switch.relay_channel_2, not both. If I remove the switch.relay_channel_2, it will bring on switch.relay_channel_1. Does generic thermostat only allow for one device to be controlled?

Posts: 4

Participants: 2

Read full topic

@JEDI_JF wrote:

I am still new to Home Assistant and Z-Wave so I am still learning. I am running Hass.io in Docker on a PC and I have the Aeotec Gen5 USB Z-Wave stick. I bought a Dome Z-Wave Siren (battery powered) that I wanted to beep when a door was opened or closed. It was working OK but the delay was making me crazy. It took about ~2 seconds to make the noise but sometimes it was fast (if I remember correctly it was fast after the first trigger). I want things to be responsive so that is one of the reasons I chose Home Assistant since everything is local.

I assumed there was a delay with the Dome Siren because it is battery powered (I suppose that in order to preserve batteries, it must be sleeping and then waking up to listen to commands) so I sent it back for a refund. I bought a Neo Coolcam Z-Wave Siren that can be powered using a USB charger. I paired it in secure mode in Home Assistant while being powered by USB (I don’t even have batteries anyway). It seems to be working fine BUT I still experience a delay. I moved it next to the Aeotec Stick (~40 cm distance) and when I switch it on the Home Assistant UI, it takes about ~1.5 seconds to make the sound. Then if I trigger it again it is very fast, there is no delay that I can experience. Since the device is powered, I would have expected not to have any delay at all time. Is it normal? I don’t have light switches yet but if there is a ~1.5 delay I will be very disappointed.

Also, the Coolcam siren reports 24% battery level even if there is no battery, could it be configured wrong? I added it as secure, should it be added as non-secure? I am running the lastest version of Hass.io.

Here is the log, my understanding that the command was sent from HA at 13:32:58.708 but the confirmation that the siren was triggered was received at 13:32:59.939

2020-01-25 13:32:58.708 Info, Node005, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2020-01-25 13:32:58.708 Info, Node005, SwitchBinary::Set - Setting node 5 to On
2020-01-25 13:32:58.708 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x44, 0x5a
2020-01-25 13:32:58.708 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x45, 0xa5
2020-01-25 13:32:58.708 Detail,
2020-01-25 13:32:58.708 Info, Node005, Sending (Send) message (Callback ID=0x44, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x44, 0x5a
2020-01-25 13:32:58.718 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-01-25 13:32:58.718 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2020-01-25 13:32:59.939 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x44, 0x00, 0x00, 0x7b, 0xd4
2020-01-25 13:32:59.939 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x44 received (expected 0x44)
2020-01-25 13:32:59.939 Info, Node005, Request RTT 1230 Average Request RTT 796
2020-01-25 13:32:59.939 Detail,   Expected callbackId was received
2020-01-25 13:32:59.939 Detail,   Expected reply was received
2020-01-25 13:32:59.939 Detail,   Message transaction complete

But if I send a second command quickly, the command is sent a 13:33:01.480 and the reply received at 13:33:01.510 (which makes sense because I can’t hear a delay of 30 ms)

2020-01-25 13:33:01.480 Info, Node005, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2020-01-25 13:33:01.480 Info, Node005, SwitchBinary::Set - Setting node 5 to On
2020-01-25 13:33:01.480 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x46, 0x58
2020-01-25 13:33:01.480 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x47, 0xa7
2020-01-25 13:33:01.480 Detail,
2020-01-25 13:33:01.480 Info, Node005, Sending (Send) message (Callback ID=0x46, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x46, 0x58
2020-01-25 13:33:01.490 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-01-25 13:33:01.490 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2020-01-25 13:33:01.510 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x46, 0x00, 0x00, 0x03, 0xae
2020-01-25 13:33:01.510 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x46 received (expected 0x46)
2020-01-25 13:33:01.510 Info, Node005, Request RTT 29 Average Request RTT 223
2020-01-25 13:33:01.510 Detail,   Expected callbackId was received
2020-01-25 13:33:01.510 Detail,   Expected reply was received
2020-01-25 13:33:01.510 Detail,   Message transaction complete

Posts: 4

Participants: 2

Read full topic

@geeked wrote:

Hi there!

I am looking to have an automation sent when a certain phone in our household connects via wifi using this sensor sensor.connection_type_2. How can I create an automation to send me a push notification when this happens?

The only triggers I see are battery, pace value, distance, floors and steps. It would be easier if “connection type” was in there but unfortunately it is not.

image614×502 9.53 KB

Posts: 2

Participants: 2

Read full topic

@nordscan wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@lucas3d wrote:

Hi everyone,

End of last year, I started using HA and I’m using recently Zigbee2Mqtt 1.9.0 without any issue.
Both of them are running in Docker on my Synology NAS. Very easy to configure and use…

It looks like after 0.104 updates, my Zigbee devices are unavailable after HA restarted. I didn’t find any error in HA and Zigbee2Mqtt logs.

The only solution to get my devices available is to restart Zigbee2Mqtt.

Does someone have the same issue?
Does a better solution exist?

Thanks

Posts: 2

Participants: 2

Read full topic

@mrrodge wrote:

Getting ‘Unknown’ in HA for the following config, can anyone help? Temp is reported in hex so assume I’ll need to convert to decimal somehow (?) but humidity is already decimal so surely should show?

RFLink Loader works great in same location so I know signal is no issue.

Not sure on how to check the logs for this, any help would be greatly appreciated!

Thanks!

rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__0042_55731323436351113051-if00
  
sensor:
  - platform: rflink
    automatic_add: false
    devices:
      AcuriteV2_ebdf_TEMP:
        sensor_type: temperature
      AcuriteV2_ebdf_BAT:
        sensor_type: battery
      AcuriteV2_ebdf_HUM:
        sensor_type: humidity

Posts: 9

Participants: 2

Read full topic

@silver323 wrote:

I’m using the standard weather integration of met.no but now something noticed me that the data or days not changing. In alle days it’s display the same.

Screenshot_20200125-2052571440×787 80.4 KB

What can I do with this?

Posts: 1

Participants: 1

Read full topic

@helgemor wrote:

Please help! I upgraded from 0.104.2 to 0.104.3. Nothing else is done.
Now Node Red (hassio add-on) is unable to execute call service. The node red log is full of “Call-service API error.”
I have tried restarting everything, and reboot, and uninstall/reinstall node red. Nothing helps.
I also have the same problem with zigbee/deCONZ. Node red is unable to connect to it. I have changed the port to 40850.
What can I do?

Posts: 1

Participants: 1

Read full topic

@Byrkjis wrote:

Hello everyone,
Im trying to figure out how to solve a automation with attention to control lights at daytime due to weather conditions.
my criteria is:

• tracking device must be “home”
• use sunrise as i only need this automation on daytime. (another automation trigger when sunset).
• and, of course, use weather condition as a trigger/condition.

i have tried a mixes with a test automation-setup with out any luck so far. it seems that it goes on even when im “not_home” and after daytime…

• Do I need to implement “tracking device” since I have a another automation for turn off all lights when leaving home and on when i get home?

• Also, i want to have more than “cloudy” in weather trigger. how do solve that ?

take a look at config for this automation:

  alias: test
  description: ''
  trigger:
  - entity_id: weather.hjemme
    platform: state
    to: cloudy
  condition:
  - condition: and
    conditions:
    - after: sunrise
      before: sunset
      condition: sun
    - condition: state
      entity_id: device_tracker.mm
      state: home
  action:
  - entity_id: light.dimmable_light_1
    service: light.turn_on

Posts: 2

Participants: 2

Read full topic

@sd_dracula wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@grafalex wrote:

Hello,

I have a few Xiaomi devices connected to HA via zigbee2mqtt. All devices connected in auto-discovery mode. I can set up automations for all of the devices, but there is one issue: I can’t read batter level for my 2-button wireless switch.

Interestingly, I see batter level data in the MQTT message:

zigbee2mqtt/extra_switch: b'{"battery":97,"voltage":2995,"linkquality":99}'

Unfortunately I can’t see batter level on an auto-generated sensor.extra_switch_battery. What could go wrong? I see batter level for other battery-powered devices no problem.

Posts: 2

Participants: 2

Read full topic

@iz3man wrote:

I was looking for ANY siren able to play different sounds (Wifi or Zigbee) but couldn’t find any.
I’d like to have something like my old fashioned alarm system that was beeping slowly when armed, and faster once pre-alarm was triggered. And then there was an internal and external siren as well of course triggered once the alarm went off.
So the device i’m looking for shoud be able to play different pre-defined sounds. Just a special beep…beep… and another beep-beep-beep etc …
Or even some other sound files based on several other events.

Could Alexa do this, and if so: HOW?

Or does someone now another device being capable of what i want?

Posts: 3

Participants: 3

Read full topic

@TiBo wrote:

Hello,
i need a little help programming an ESP.

My ESP has following setup:

• at GPIO2 an LED
• at GPIO4 an Dallas ds18b20
• at GPIO13 an Relay
  (it is an Sonoff TH16 V2.1 2019 with PIN EXT-LOG aka GPIO2 )

1. I want that the LED is slowly blinking when the temperature is rising. (~20° - 86°)
2. above 86°C the LED the LED is constant on
3. if the temperature is falling below 85° the LED is fast blinking
4. below 60° the LED turns off.

is this possible with ESPhome configuration and lambda programming?
at the moment i use as on_value_range with some steps but the rising/falling is much smarter . also it should be possible to track times.

optional i want to track the Time how long it takes to reach the 86°C Temperature. Starting point to measure the Time is switch the relay on

(why 86° and not 85°? If the Dallas chip has problems with the wires the sensor gives 85° back)

I’m looking forward to the solution.

Posts: 1

Participants: 1

Read full topic

@Sander_Wolschrijn wrote:

Hi All,

I’m running the laters version of hass.io on a RPI4

Is there a possibility to join/unjoin Yamaha musiccast speakers?

I have a receiver RX-V483 and a speaker WX-030.

This is the configuration in yaml.

# Musiccast Keuken
platform: yamaha_musiccast
host: !secret mc_keuken
port: 5004
# Musiccast Woonkamer
platform: yamaha_musiccast
host: !secret mc_woonkamer
port: 5005

I have created a mini media player card

entity: media_player.woonkamer_main
type: 'custom:mini-media-player'
artwork: cover
speaker_group:
  platform: yamaha_musiccast
  show_group_count: true
  entities:
    - entity_id: media_player.keuken_main
      name: Keuken

Every time I try to join speakers I get the error message

Failed to call service yamaha_musiccast/join. Service not found. 

Posts: 1

Participants: 1

Read full topic

@eoren1 wrote:

I have Hass.io installed on a Plex Synology DS918+ via Docker.

Through trial and error, I ended up with multiple instances of myself in the Integrations section. I also decided to sign up for the Cloud service and figured a clean install of the HA Companion app on my phone was a good idea.

I went in and deleted all of the iPhone integration entries (there were 2 for me, 1 for my wife and a couple for me that did not have any of the iPhone icons associated) as well as the app off my iPhone. I restarted HA. Reinstalled the HA Companion App. I now have 1 entry in configuration for my iPhone.

However, when I click on Persons and my name, I see the Track Device entries and, clicking on the drop down, reveals three device trackers with a 1, 2 or 3 at end. I’m not sure where these are coming from. Looking in Developer Tools - States, I only see one of the device trackers (the one ending in _2).

I have a separate device_tracker entry in configurations.yaml to ping all devices to show home/away in the badges in Lovelace but that is not what is driving this.

I also integrated Homekit through the input_boolean that was suggested somewhere for better presence detection but don’t think that is causing this behavior.

Would really appreciate any help in cleaning this up. For now, I put all three of the iPhone device trackers under my name in Persons just in case…

Posts: 1

Participants: 1

Read full topic

@dgaust wrote:

Hi,

I’m going through building a UI for a basic remote based on the logitech harmony. I’m wondering if there is an easy way to send command based on the current activity rather than send the command to a selected device.

For example, if the activity is Play Xbox the commands for up, down, left and right need to be sent to the xbox device. However, if the activity is Watch Fetch, those commands need to be sent to the Fetch TV box. The physical remote is setup to do this, but I cannot find a service option to send command to an activity (so the hub can decide the code) rather than device.

At the moment I’ve simulated this by using scripts like this

'1579329073616':
  alias: HarmonyButtonEnter
  sequence:
  - service: remote.send_command
    data_template:
      entity_id: remote.lounge
      command: >
          {% if is_state("sensor.currentactivity", "Watch TV") %} 
            OK
          {% elif is_state("sensor.currentactivity", "Watch Fetch") %} 
            Select
          {% elif is_state("sensor.currentactivity", "Play Xbox") %} 
            Ok
          {% else %}
            Ok
          {% endif %}
      device: >
          {% if is_state("sensor.currentactivity", "Watch TV") %} 
            38539290
          {% elif is_state("sensor.currentactivity", "Watch Fetch") %} 
            38539289
          {% elif is_state("sensor.currentactivity", "Play Xbox") %} 
            46058342
          {% else %}
            38539290
          {% endif %}

But that means creating a script for every option, and then calling that script from a button in the UI.

Am I overcomplicating it, or is this the only approach?

Posts: 1

Participants: 1

Read full topic

@Linuxmale wrote:

I switched from /dev/ACM1 to the full USB path because of startup issues. Is there any way to recover the devices w/o repairing them all?

Posts: 1

Participants: 1

Read full topic

@willh wrote:

By setting a Tasmota v8.1.0 dimmable bulb to use the PWM directly ( SetOption15 0 ) instead of 0-100% dimmer, I can get my bulb to a much lower brightness. This is great since I use it as a night light. I sorted out the configuration below and it works well except that unlike in the Dimmer configuration, hitting the toggle does not restore the light to its previous brightness. Instead, it turn it on the max value in the brightness_scale.

This seems like a bug but I wanted to check if there is something wrong with my configuration. Note that in Pwm config, the bulb doesn’t publish tele/%topic%/STATE so instead I have to subscribe to stat/%topic%/RESULT with that complete payload being:

{
“PWM”: {
“PWM1”: 52
}
}

• platform: mqtt
  unique_id: ff_front_br_night_light
  name: “Night light”
  command_topic: “cmnd/DVES_89ADF0/Pwm”
  state_topic: “stat/DVES_89ADF0/RESULT”
  state_value_template: “{% if value_json.PWM.PWM1 | float > 0 %}ON{% else %}OFF{% endif %}”
  availability_topic: “tele/DVES_89ADF0/LWT”
  brightness_command_topic: “cmnd/DVES_89ADF0/Pwm”
  brightness_state_topic: “stat/DVES_89ADF0/RESULT”
  brightness_scale: 120
  on_command_type: “brightness”
  brightness_value_template: “{{value_json.PWM.PWM1}}”
  payload_on: “ON”
  payload_off: “OFF”
  payload_available: “Online”
  payload_not_available: “Offline”
  qos: 1
  retain: false

Posts: 1

Participants: 1

Read full topic

@SylvainGa wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@kevinkk525 wrote:

A few days back I had a strange problem: All my home-assistant lost internet access. The caldav integration couldn’t sync anymore and hacs threw connection errors. However the ping integration worked just fine and showed that everything was reachable. Also checking the internet connection inside the docker container through bash worked just fine and the rest of my RPI3 had internet access too.
I had to restart the docker container for everything to work again.
Any idea how this could happen?

Posts: 1

Participants: 1

Read full topic