Hi there,
I had integrated the Mitsubishi Melcloud, but since some time when I use the remote control to control my airco units, I see the Melcloud is showing right information (so on the Mitsubishi server), but HA is not getting that information, like the Airco is off …
Is there anything I can test / check to solve this ?
I see this in my HA 
To be honest I do not recall where I had entered my credentials on Melcloud anymore
;-(
Many Thanks !
1 post - 1 participant
Hi, I created the template sensor
- trigger:
- platform: time_pattern
hours: /1
action:
- service: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.openweathermap
response_variable: hourly
sensor:
- name: Home Weather Forecast Hourly
unique_id: f257b8b3-1cee-4130-9dd6-158a1e8f13da
state: "{{ now().isoformat() }}"
attributes:
forecast: "{{ hourly['weather.openweathermap'].forecast }}"
And an automation
service: telegram_bot.send_message
data:
message: >-
Outside temperature is {{
states.weather.openweathermap.attributes.temperature }} °C.
The raining chances are: {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[0].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[0].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[1].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[1].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[2].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[2].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[3].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[3].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[4].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[4].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[5].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[5].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[6].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[6].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[7].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[7].precipitation_probability }}% {{- '\n' -}} At {{
state_attr('sensor.home_weather_forecast_hourly', 'forecast')[8].datetime |
as_timestamp | timestamp_custom('%H:%M') }} - {{
state_attr('sensor.home_weather_forecast_hourly',
'forecast')[8].precipitation_probability }}%
Where to input an if statement to receive only the lines if precipitation_probability is greater than zero and if all values are zero, to not receive at all?
2 posts - 2 participants
Hi there,
had to install my HA again and just used a backup-file. Nevertheless I am stuck with MQTT, I
am not able to get it connected to HA in docker.
I installed the MQTT package on my synology, then changed the misquitto.conf accordingly (listener 1883, allow_anonymous false, password_file /var/packages/mosquitto/var/password and created a password file (user:password) and then encrypted it.
At my synology port 1883 at the firewall is open
In HA I used the MQTT integration to connect, but always with no success…it always says:
connection failed
Any ideas what I might have missed?
3 posts - 2 participants
Hi everyone
I’m a Home Assistant newb, so any help, guide, or key words to search would be greatly appreciated.
I’ve attached an Aqara window sensor to a car seat sensor to use as a seat occupancy sensor. I’m trying to create an automation so the standing desk will rise if I sit down for more than 1 hour. I’m using Zigbee2MQTT and the sensor works really well. Pleasantly surprised how instant the sensor is.
The problem is when I fidget or move while still sitting down, the sensor will go to a “clear” state for a second and reset the 1 hour timer. This sensor doesn’t have a separate sensitivity expose in zigbee2MQTT.
I’m thinking if I use the last 5 minute average of the occupancy state, then it should provide enough buffer to lessen the sensitivity.
I’ve tried creating a template binary sensor with the following code.
sensor:
- platform: statistics
name: "Seat occupancy 5 min average"
entity_id: binary_sensor.seat_occupancy_sensor_contact
state_characteristic: average_step
max_age:
minutes: 5
I’m not sure if its doing anything, but it doesn’t update at all. I’m assuming the state is never changing. Do I need to force the sensor to start every 5 mins? Is there a way to continuously output the last 5 minute average state?
I’m currently trying to use the last 5 minute average of the state to lessen the sensitivity. I’m sure there are smarter ways to approach this.
Any ideas, help would be great.
Thanks!
1 post - 1 participant
I have a Olimex ESP32 POE board and tried to use it as a Bluetooth Proxy and as a ESPresense device that is located in the living room and all I want is for it to be able to trigger an automation when my phone (an Android, but can also be a Tile device or a Blue Charm Bluetooth device).
I tried following the concept of ESPresence, but I ultimately became confused as it seems as though there are overlaps between that an Room Presence / MQTT Rooms.
Currently, I have the MQTT add-on enabled and Room Presence enabled and in my config file for HA, I have:
sensor:
- platform: mqtt_room
name: "IronFoldable"
device_id: "iBeacon:519199c9-ca2b-4e33-8f54-48d22607f684_100_1"
state_topic: "espresense/devices/ironfoldable"
I tried changing the state topic to espresense/devices and that auto discovery never kicked in.
On the devices page, I have added MQTT and configured it to point to my HA instance, and so far it just shows “changeme” and “ESPresense basement” (which is the name of my Olimex ESPresense device). If I click on it, it shows information.
I’ve also tried enrolling my phone on the ESPresense device.
Knowing me, I’ve overcomplicated this somehow and got my signals crossed and have too much going on. I feel so close though as the ESPresense device tells me, by device, how many meters away another device is. And at the end of the day, I just want to trigger an automation when a device is less than X meters and when it’s more than X meters.
Any help/advice/clarity would be greatly appreciated.
Thanks,
AJ
1 post - 1 participant
I will remove myQ from my network pretty soon. I have configured the Meross smart garage door opener in Home Assistant as a HomKit Device. I am just waiting for the additional device that will enable HA (and HomeKit) to open/close my Liftmaster WiFi garage door opener. I am sick and tired of not having a garage door system integration in HA. After the complete installation of the Meross system, I will block the garage door opener’s myQ WiFi from going out to the Internet. I will be done with myQ then and I can control my garage door system in HA.
1 post - 1 participant
I am two weeks with the ecobee thermostat which I integrate with HA via the HomeKit Device integration. It replaced a Nest learning thermostat which I loved dearly before Google wants me to migrate from the Nest system to the Google cloud. And on top of that, (I believe) HA integration of the Nest thermostat needs Google cloud which I don’t like. Anyway, I’m happy with the ecobee integration in HA. Now, I utilize the motion detection attribute of the ecobee in HA to automatically turn on a smart switches in the kitchen and living room at night to turn on lights. However, I miss the granular scheduling of the Nest thermostat. Maybe there is a way to mimic that granularity in the ecobee using HA automation - I have to research on this.
1 post - 1 participant
Hi, is core/homeassistant/components/default_config/manifest.json at cd8dac65b39c71b63495a385c4e36ff9b1e45ae3 · home-assistant/core · GitHub the same as default_config: ?
I pasted this instead of default_config in my configuration.yaml file and got the error below
I want to remove default_config because I want to disable cloud component.
1 post - 1 participant
I began building out my HA system in the last year. I chose Z-Wave as the protocol of choice partly because I already had a couple of devices from a previous system but also because Z-Wave appeared to have more options in the US. I have installed a Z-Wave switch pretty much everywhere in my home, as well as a few other battery-powered devices for locks, door sensors, and motion sensors.
My home is rather small, 1,100 square feet above grade, and has a finished basement with a detached garage. The home is brick with lapboard and plaster walls, and the garage is constructed of basic wood and paneling without any insulation. The entire lot the house sits on is less than 4,700 sq ft.
My Z-Wave devices are either series 700 or 800 and a Zooz ZST39 LR 800 Series Long Range USB Controller. I have not touched any of the settings on the controller other than setting the RF Region to “USA (Long Range).” The Normal power level is set to 0 dBm and the Measured output power 0 dBm (I was told not to mess with those settings). The system started with the Aeotec 700 series stick and was even worse. There was a slight improvement with the Zooz 800 series stick. There are presently 53 devices in the network (besides the controller).
HA is presently running in Docker and Z-Wave JS is on the same computer also running in Docker on an Intel NUC.
My problem is that all except one of the Z-Wave devices are incredibly slow to respond and sometimes do not respond at all. However, all devices will respond to a ping from the controller. It is not unusual for a door that has opened and closed to show as still open. One of the doors is less than 10 feet from the controller (with a wall between them). The one reliable and instantaneously responsive device (one of the furthest from the controller) is in the garage and works flawlessly and immediately every time.
Being that the collection of Z-Wave devices has easily been the largest investment in my system, this has become incredibly frustrating. I kept thinking adding more devices so the Z-Wave mesh network could be expanded would help, but it did not.
Does anyone have any advice on improving the reliability of my Z-Wave system (or advice on a better system)? The SmartHome is not that useful if it doesn’t work reliably or is so delayed that lights that should be automatic take too long to activate.
2 posts - 2 participants
Hi,
i d like to get all “warning” inside “warnings” one sensor per “warning” - the problem I have that this could be 1…n.
At the moment I address them static which can result in an error if there are no warnings at all.
How can I change the warnings[0] to a more dynamic request?
thanks
eg:
rest:
API Call:
{
“type”: “Feature”,
“properties”: {
“location”: {
“type”: “Municipal”,
“properties”: {
“gemeindenr”: 30740,
“name”: “Schwechat”,
“urlname”: “schwechat”
}
},
“warnings”: [
{
“type”: “Warning”,
“properties”: {
“warnid”: 4149,
“chgid”: 6,
“verlaufid”: 2,
“warntypid”: 1,
“begin”: “27.03.2023 08:00”,
“end”: “27.03.2023 18:00”,
“create”: “2023-03-27 06:00:00+00”,
“updategrund”: “”,
“warnstufeid”: 1,
“rawinfo”: {
“wtype”: 1,
“wlevel”: 1,
“start”: “1679896800”,
“end”: “1679932800”
}
}
},
{
“type”: “Warning”,
“properties”: {
“warnid”: 4150,
“chgid”: 2,
“verlaufid”: 1,
“warntypid”: 1,
“begin”: “28.03.2023 08:00”,
“end”: “28.03.2023 18:00”,
“create”: “2023-03-27 08:00:00+00”,
“updategrund”: “”,
“warnstufeid”: 1,
“rawinfo”: {
“wtype”: 1,
“wlevel”: 1,
“start”: “1679983200”,
“end”: “1680019200”
}
}
}
]
}
}
2 posts - 2 participants
After an update of zigbee2mqtt, 2 of my OSRAM light strips are no longer available as light entities, only the update entity is still available. The following error message also appears:
Error 'some but not all values in the same group of inclusion 'color_mode' @ data[<color_mode>]' when processing MQTT discovery message topic: 'homeassistant/light/0x8418260000caa9df/light/config', message: '{'availability': [{'topic': 'zigbee2mqtt/bridge/state'}], 'brightness': True, 'brightness_scale': 254, 'command_topic': 'zigbee2mqtt/0x8418260000caa9df/set', 'device': {'identifiers': ['zigbee2mqtt_0x8418260000caa9df'], 'manufacturer': 'OSRAM', 'model': 'Flex RGBW (4052899926110)', 'name': '0x8418260000caa9df', 'sw_version': 'V1.03.07', 'via_device': 'zigbee2mqtt_bridge_0x00124b0018e24a4b'}, 'effect': True, 'effect_list': ['blink', 'breathe', 'okay', 'channel_change', 'finish_effect', 'stop_effect', 'colorloop', 'stop_colorloop'], 'json_attributes_topic': 'zigbee2mqtt/0x8418260000caa9df', 'max_mireds': 666, 'min_mireds': 125, 'name': None, 'object_id': '0x8418260000caa9df', 'origin': {'name': 'Zigbee2MQTT', 'sw_version': '1.37.1', 'support_url': 'https://www.zigbee2mqtt.io'}, 'schema': 'json', 'state_topic': 'zigbee2mqtt/0x8418260000caa9df', 'supported_color_modes': ['xy', 'color_temp'], 'unique_id': '0x8418260000caa9df_light_zigbee2mqtt', 'platform': 'mqtt'}'
Deleting and re-adding has not brought any improvement.
1 post - 1 participant
I configurated a new dehumifier through Smart Life App and I can control it (setting the desired umidity level etc.)
Is there a way to integrate that into HA?
I looked for some custom component but didn’t find anything
The dehumifier model is Argo dry pury evo wf
2 posts - 2 participants
Been fighting with this for a minute, bad not making progress…
I’d like to us ‘auto-entites’ and their filters to supply the entities for ‘multiple-entity-row’. Can’t seem to get the syntax right.
Here’s what I’ve got so far:
- type: vertical-stack
title: Speakers
cards:
- type: custom:auto-entities
card:
type: custom:multiple-entity-row
secondary_info: last-changed
filter:
include:
- domain: device_tracker
integration: unifi
area: Speakers
exclude: []
sort:
method: friendly_name
card_param: entity
Which, funny enough, just gives me a blank
So how would I pass the filtered auto-entities, into multiple-entity-row?
I’m kind of at a loss, or it’s just not making sense.
Any advice or pointers would be appreciated. Thanks.
If I change the type; from custom:multiple-entity-row to entities it seems to work fine. Was hoping card_param: entity would fix that, but it doesn’t…
1 post - 1 participant
Hi everyone
Please help me with automation
Description :
Lights turn on manually by switch and should be turned off considering all this conditions:
So if someone turned lights on lights should be turned on at least for 5 minutes. Also if someone passed by motion sensor - it should increase turned on time for 2 minutes each time
A tried a lot of ways, I used repeat until , wait, I tried some blueprints - no luck. I get some issues and wrong behavior. Please help
3 posts - 3 participants
I often read about performing an energy scan to see what zigbee channel to use if experiencing interference or high channel usage. However I am wondering what is the best way to perform the scan and how to interpret the data.
My production system is on ch25 in this first scan:
Based on the above scan, it would appear that ch20 is a perfect choice given it is at 5.83%, while ch25 is at 88.05%. However, here is where I have a doubt. If all your zigbee devices are on ch25, then it is normal for the energy scan to return a high value… and why is it therefore considered bad?
Anyhow, I moved to ch20 and from my test system I performed another energy scan. Now we see that ch20 is at ~50% (different location and coordinator).
Now we see that ch25 has dropped to ~14% (see disclaimer above) which is still higher than ch20 was but low enough to be a good choice. I actually prefer ch25 as on WIFI ch6 can interfere (likely highest power output) if the channel is set wide enough. I keep my 2.4GHz WIFI channels strictly to 20MHz as there are no performance devices on my 2.4GHz SSID.
I guess my point is that the energy scan makes most sense when you are starting from zero, with no installed zigbee devices. Once you have an active network, how is judging the channel you are using useful given the energy scan is likely showing lots of usage due to your own devices?
Note: If you are comparing the two scans above, please note they were performed by a SiLabs based controller (above) and a TI based controller (below) and they are in two different rooms with two significantly different antennas. The change is visible, however the measurements may not be comparable due to differences between the two coordinator setups.
I have a really cheap spectrum analyzer (TinySA Ultra) that I am still learning on how to use, but this is what the spectrum looks like for zigbee ch20 to ch25:
My goal is to hunt for interference sources but not sure yet on the best way. Suggestions welcome!
2 posts - 2 participants
Hello,
I have added several Sonoff Zigbee door sensors for alarms when absent. For this I added a helper “AlarmArmed” that can be on or off. When it is on and a door is opened it fires several alerts, e.g. Telegram messages. This works so far.
What I would like to add now is, that if AlarmArmed is turned on, the state of every door sensor is checked and a Telegram message is sent that tells me of this, including the friendly name of every door sensor that is open. I managed to do this by creating a separate automation for each door.
My question is: can I do this in a more elegant way in yaml, by doing a “for each” loop and in case the current sensor is open it writes the friendly name along with a newline char in a buffer and then after iterating over every sensor it sends a message with the buffer as message body? I tried to find necessary functions in the documentation, but no luck. I don’t need someone to write it for me, I’d be very happy if someone could drop the necessary function names.
Thanks a lot!
1 post - 1 participant
I have 4 Phoscon Hive Battery lights on my Zigbee ZHA network.
While I can control the lights without any issues and the devices are running the latest firmware, the battery status does not display.
However, I can read the battery status using the Cluster command and get a correct value from 0 to 200 for battery_percentage_remaining (id: 0x0021).
Interestingly, the lights are showing as main-powered instead of battery-powered.
Does anyone have any ideas on how to solve this issue?
1 post - 1 participant
I was looking for a simple way to use a single push of the Fibaro Button to toggle a light. A lot of examples I found were very flexible in the use of the button but complicated. After adding the button normally as a ZWave device, this simple automation worked so I thought I would share.
(FYI: if you need to find the device id: Settings, Devices, select the button device - the device ID is the last part of the resultant URL.).
If you leave the value_raw line out it will fire anytime the button is pushed. Adding this line allows you to fire only for a certain number of pushes/holds. The values are not consistent but you can find them via the Developer tools and events. Listen to the zwave_js_value_notification and then press/hold the appropriate button the desired number of times.
alias: Fibaro "The Button" toggle
description: Toggle light with button push
trigger:
- platform: event
event_type: zwave_js_value_notification
event_data:
device_id: xxxx
property_key: "001"
# optional line to detect numbers of presses (0=1 press) and holds
value_raw: 0
condition: []
action:
- type: toggle
device_id: yyyy
entity_id: zzzz
domain: switch
mode: single
or an alternative trigger you can toggle with:
trigger:
- platform: event
event_type: zwave_js_value_notification
event_data:
device_id: xxxx
label: Scene 001
1 post - 1 participant
Hi.
I did add Dyson device, it’s fully controlable. But for some reason I can’t add some of the controls, like night mode to the overview dashboard. It seems I am lacking some kind of config? What I am doing wrong?
1 post - 1 participant
I have a question about the alignment. I’ve tried everything, but I can’t get this card right. I’m also sharing my code. As you can see, it should be the same as the other cards (right side)
- type: horizontal-stack
cards:
- type: custom:state-switch
entity: template
template: >-
{% if is_state_attr('media_player.sonos_woonkamer', 'source', 'Spotify
Connect') and is_state('media_player.sonos_woonkamer', 'playing') %}
spotify
{% elif is_state_attr('media_player.sonos_woonkamer', 'source', 'TV') and
is_state('media_player.sonos_woonkamer', 'playing') %}
tv
{% else %}
hide
{% endif %}
states:
spotify:
type: custom:mushroom-template-card
primary: '{{ state_attr(''media_player.sonos_woonkamer'', ''media_artist'') }}'
secondary: '{{ state_attr(''media_player.sonos_woonkamer'', ''media_title'') }}'
icon: mdi:spotify
layout: vertical
icon_color: grey
picture: ''
entity: media_player.sonos_woonkamer
card_mod:
style: |
ha-card {
{% if not is_state(config.entity, 'idle') %}
background-image: url('{{ state_attr(config.entity, "entity_picture") }}');
background-position: center;
background-repeat: no-repeat;
background-size: cover;
background-color: rgba(var(--rgb-card-background-color), 0.7);
background-blend-mode: overlay;
{% endif %}
--rgb-state-media-player: var(--rgb-teal);
box-shadow: var(--card-box-shadow);
margin: 0px 0px 0px 14px;
}
tv:
type: custom:mushroom-template-card
primary: '{{ state_attr(''media_player.lg_webos_tv_up77006lb'', ''source'') }}'
secondary: Soundbar
icon: ''
icon_color: grey
picture: >-
/api/media_player_proxy/media_player.lg_webos_tv_up77006lb?token=14bd9a7da2a506cb14b503fa5ad19988481a2c72777b0c39a3a23786538a75c5&cache=e33f2d5224fb5709
entity: media_player.sonos_woonkamer
fill_container: false
multiline_secondary: false
layout: vertical
card_mod:
style: |
ha-card {
{% if not is_state(config.entity, 'idle') %}
background-image: url('{{ state_attr(config.entity, "entity_picture") }}');
background-position: center;
background-repeat: no-repeat;
background-size: cover;
background-color: rgba(var(--rgb-card-background-color), 0.7);
background-blend-mode: overlay;
{% endif %}
--rgb-state-media-player: var(--rgb-teal);
box-shadow: var(--card-box-shadow);
margin: 0px 0px 0px 14px;
}
- type: conditional
conditions:
- condition: state
entity: media_player.ps5_console
state_not: 'off'
card:
type: custom:mushroom-template-card
primary: '{{ state_attr(''media_player.ps5_console'', ''media_title'') }}'
secondary: >-
{% if is_state('media_player.ps5_console', '') %}
{{ states('media_player.ps5_console') }}
{% else %}
Speeltijd: {{ timedelta(states('sensor.playstation_aan_vandaag') |
float(0) / 24) }}
{% endif %}
icon: mdi:sony-playstation
icon_color: grey
picture: ''
entity: media_player.ps5_console
layout: vertical
card_mod:
style: |
ha-card {
{% if not is_state(config.entity, 'idle') %}
background-image: url('{{ state_attr(config.entity, "entity_picture") }}');
background-position: center;
background-repeat: no-repeat;
background-size: cover;
background-color: rgba(var(--rgb-card-background-color), 0.7);
background-blend-mode: overlay;
{% endif %}
--rgb-state-media-player: var(--rgb-teal);
box-shadow: var(--card-box-shadow);
margin: 0px 0px 0px 14px;
}
2 posts - 2 participants