Hello,
my RFXtrx works fine with my solar somfy cover.
I try to do the same with my somfy portal.
I have used rfx manager and under it it works well. Like this I have an ID that I have reported into homeaasistant. Homeassistant found the entity but the buttons doesn’t work (they were working fine with rfx manager).thanks
1 post - 1 participant
Hy guys!
I did a fresh HASSIO instalation last weekend, in my PI4, but the samba share addon doesn’t appear in addon store. Any clue about waht’s happening?
2 posts - 2 participants
Hi
i’m new to this fantastic world of HA.
i’ve already tried esphome and it works perfectly, but i want to do the same things via a wired link.
i’ve found a 8 in 8 out modbus module but i have a question: if i hold for half a second a push button wired to an input of the modbus module i want to toggle a scene. is it possible with modbus?
Thank you!
Alex
1 post - 1 participant
I originally had surveillance station up and running via the old Synology platform integration and everything worked fine. I attempted to switch over to the new Synology DSM integration as the old one is deprecating in 118.
All of the hardware sensors show up fine, but the cameras are not showing. Under the users permissions in Synology I have surveillance set to read/write and the surveillance station app set to read/write. Everything else is set to deny. Am I missing something?
1 post - 1 participant
Yesterday and today I received an e-mail from OpenWeatherMap, warning me I had exceeded my free API limit of 1000 calls a day. This doesn’t ring a bell. It is configured for two calls every hour. So that would mean 48 calls daily.
For a long time, the documentation about scan_interval mentions ‘These options are being phased out and are only available for single platform integrations.’ Has this moment finally come? How can I find out?
This is in my configuration.yaml:
- platform: rest
name: openweather_report
json_attributes_path: "$.daily[0]" # 0=vandaag
json_attributes:
- temp
value_template: "{{ value_json['current']['dt'] | timestamp_custom('%Y-%m-%d %H:%M', true) }}"
resource: !secret openweathermap_resource
scan_interval: 3600
- platform: template
sensors:
openweather_maxtemp_today:
value_template: "{{ states.sensor.openweather_report.attributes.temp.max }}"
openweather_temp_tonight:
value_template: "{{ states.sensor.openweather_report.attributes.temp.night }}"
openweather_mintemp_today:
value_template: "{{ states.sensor.openweather_report.attributes.temp.min }}"
- platform: rest
name: openweather_report2
json_attributes:
- current
- daily
value_template: "{{ value_json['current']['dt'] | timestamp_custom('%Y-%m-%d %H:%M', true) }}"
resource: !secret openweathermap_resource2
scan_interval: 3600
- platform: template
sensors:
openweather_temp_day0_v3:
value_template: "{{ state_attr('sensor.openweather_report2', 'daily')[0].temp.day }}"
openweather_temp_night0_v3:
value_template: "{{ state_attr('sensor.openweather_report2', 'daily')[0].temp.night }}"
openweather_temp_day1_v3:
value_template: "{{ state_attr('sensor.openweather_report2', 'daily')[1].temp.day }}"
openweather_temp_night1_v3:
value_template: "{{ state_attr('sensor.openweather_report2', 'daily')[1].temp.night }}"
Thanks in advance,
Roelof
1 post - 1 participant
Hello,
I try to scrape a simple text from a very simple webpage. The commandline is very suboptimal, but it works in the HA docker container - I wanted to try it out before tweaking the command…
When loading it in HA, the sensor value is empty. Please note that I integrate my sensors via the following in “configuration-yaml”:
sensor: !include_dir_list sensors
and each sensor has its own file, which content is the below. Thus e.g. “platform” has no indent or hyphen.
platform: command_line
command: "curl 'https://opendata.dwd.de/weather/text_forecasts/html/VHDL50_DWPG_LATEST_html' 2>&1 | awk '/<pre/,/<\/pre>/' | sed 's/^<[\/a-z\"-:= ]*>//g' | tr -d '\n' | tr -d '\r'"
name: "Wetter heute Berlin"
scan_interval: 900
The intention is to read the summary or the full weather text, I will most likely do everything in awk, but I am not aware of full awk syntax, thus using the weird combination of commandline tools :-)…
I tried to use the scrape sensor as well:
platform: scrape
resource: https://opendata.dwd.de/weather/text_forecasts/html/VHDL50_DWPG_LATEST_html
name: "Wetter heute Berlin"
select: "pre"
but this doesnt work (with ’ select: “strong” ’ it works for the summary at least). According to my reading from beautiful soap it should work, but the output is “unknown”… This is why I tried the commandline sensor above as well.
Thanks, regards
1 post - 1 participant
I have been running Home Assistant for half a year or so for my alarm. All has been well. We are running on an Rpi, and have installed DuckDNS and NGinx per https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy?gclid=CjwKCAiA-f78BRBbEiwATKRRBLL6gzPz1XjTQ16gBgVlNh7w-HtzQaEmDWl2C2FVdcI2VXqLKnhiXBoCSx4QAvD_BwE
We are now on a trip, and halfway through the trip have lost remote connection, mostly.
I use the HA Android app, but also was able to connect via browser in my android or laptop, at https://[mydomain].duckdns.org. We lost connection, and have been unable to restore. Unfortunately, I did not set my router to pass through SSH, so I have limited ability to do anything.
I asked my neighbor who is cat watching to reboot the Pi, but that did not solve.
Within the house on the local network (using http), the wall-mounted tablet (running WallPanel) still communicates ok.
From my tablet on the road, the app indicates “Unable to connect to home assistant”, with wait, refresh, and settings. It does display the HA logo (behind the pop-up) with a “retry” link.
From tablet in browser, it would render the top blue bar and the HA logo, with retry link. If I hit retry, then it would try to go to https://[mydomain].duckdns.org/lovelace, and would say “This site cannot be reached”, might be down or may have moved permanently to a new web address. I tried deleting cached data from the browser, which logged me out, so next try was same sequence (HA screen but no connection, then cannot be reached), except now the site is https://[mydomain].duckdns.org/auth/authorize?xxxxxxx where xxxxxx is a bunch of stuff, probably related to my key.
It would appear therefore that the router at home is not the issue, it seems to be passing me through to the Pi. But the Pi is not allowing access, though it serves up the logo.
Now for the strange part. Despite not being able to log in via the app or browser, I am still getting notifications via the app. When neighbor goes to feed the cat, I get a notification that the door opened, and the alarm is disabled.
So clearly the path is open, and we are getting some communication, but the web interface does not work. It does appear to work within the home (http, not https).
I have port 443 forwarded through the router to HA on the Pi. I think 80 and 8000 are redirected to camera system, but I don’t recall for sure.
I suspect that it has to do with the certificate. Some posts have indicated that cert may need to be renewed. Others indicate that should be automatic. If this is the case, how do I do that, and if needed, can you give explicit enough instructions that neighbor could do it from the wall panel? (Although that account may not have privileges). If not the cert, what else should i look at?
On the Pi I am running the Hassio image installation.
Thanks for any insights. Even if I have to wait until I get home, at least with your help I can resolve this.
Chuck
1 post - 1 participant
CENTRAL HEATING TIMES SELECTION
(First of all a apology, this is the first time I have posted here, if I have got the formatting wrong then be gentle with me and help me get it right in future. I have inserted 3 ticks ``` around the code but can’t seem to get it acceptable).
I am emulating an old central heating programmer.
I have all the ON/OFF timers working, 3 periods (morning, midday/afternoon and evening/night) and control of the Hot Water and Radiators so that the radiator pump cannot be ON without the boiler being on. It’s all working well so much so that I have turned off the old programmer.
I’m now working on the selection of major times period without having to reprogram the timers every time. This all need a ‘ Dr Zzzs WAF ’ (if you know what I mean).
The issue is I have four buttons as below which I want to use as radio buttons so thy are all mutually exclusive of each other. Not being used to HA and YAML I am pleased with my progress so far but now need some pointers.
Only the [ Programmer ] and [ 24 hours ] buttons act as intended but the others don’t. I also want to make it so there is always one button ON, there must NEVER be all OFF. Help !
LOVELACE PANEL:
LOVELACE CARD
Here’s the image of the four buttons.
Nomenclature:
input_boolean.ch_radio_button_xxx
Shutdown = completely off.
Here’s the YAML, I have removed the STYLE settings for ease of reading.
HELPERS, one for each button (4)
type: horizontal-stack
cards:
- type: button
tap_action:
action: toggle
icon: 'mdi:radiobox-marked'
name: Programmer (opposite)
show_state: false
show_icon: true
hold_action:
action: none
icon_height: 32px
entity: input_boolean.ch_radio_button_prg
- type: button
tap_action:
action: toggle
icon: 'mdi:radiobox-marked'
name: Day (1st ON to last OFF)
show_state: false
show_icon: true
hold_action:
action: none
icon_height: 32px
entity: input_boolean.ch_radio_button_day
- type: button
tap_action:
action: toggle
icon: 'mdi:radiobox-marked'
name: 24 Hours (continuous)
show_state: false
show_icon: true
hold_action:
action: none
icon_height: 32px
entity: input_boolean.ch_radio_button_24h
- type: button
tap_action:
action: toggle
icon: 'mdi:radiobox-marked'
name: OFF (completely)
show_state: false
show_icon: true
hold_action:
action: none
icon_height: 32px
entity: input_boolean.ch_radio_button_shutdown
SCRIPTS, one for each button (4)
I have executed each script from the /config/script/dashboard and they function as required.
alias: 'CH, Radio Prg Pressed'
sequence:
- service: input_boolean.turn_on
data: {}
entity_id: input_boolean.ch_radio_button_prg
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_day
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_24h
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_shutdown
mode: single
alias: 'CH, Radio Day Pressed'
sequence:
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_prg
- service: input_boolean.turn_on
data: {}
entity_id: input_boolean.ch_radio_button_day
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_24h
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_shutdown
mode: single
alias: 'CH, Radio 24h Pressed'
sequence:
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_prg
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_day
- service: input_boolean.turn_on
data: {}
entity_id: input_boolean.ch_radio_button_24h
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_shutdown
mode: single
alias: 'CH, Radio ShutDown Pressed'
sequence:
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_prg
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_day
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.ch_radio_button_24h
- service: input_boolean.turn_on
data: {}
entity_id: input_boolean.ch_radio_button_shutdown
mode: single
Thanks in anticipation everyone.
1 post - 1 participant
Since a few days my alarm randomly goes to the triggered state. When checking the logbook it says “Home Alarm changed to Arming by Hass.io”, anyone have any clue to where this might come from?
I’ve tried enabling debug logging on homeassistant.components.alarm_control_panel, but nothing pops up in the logs unfortunately.
1 post - 1 participant
I have a HA Virtual Box installation on a Windows host machine which worked perfectly fine until we had a few power failures and the HA virtual hard drive failed.
I created a new Virtual Box image and I imported the most recent snapshot but the Aotec Stick always shows as unavailable in my VB installation.
Any ideas what is going on?
1 post - 1 participant
Hi,
I have a system that will tell me from 4 zones, which ones have a heating demand and I can choose to turn the boiler on.
However I imagine that the more zones I have, the more likely it is for any one of those zones to demand some heat, especially if they don’t take heat from a previous request earlier in the day.
So that could lead to the boiler being on more often, perhaps nearly continuously.
I then took an unexpected direction, and averaged the demand across all zones. Which would effectively turn frequent and short demands into less frequent but longer demands. This Reduces the response, and the ability drive up the temp in particular room.
My implementation is relatively simple.
I’m using OZW 1.6 which supports Eurotronic Spirtz thermostats.
I have events and timers that configure the set points as you would expect (15 at night, 19 in the day, 16 when away at not night)
The thermostats have their own logic, and their valves are opened accordingly.
I then use a boolean entity to model if the value is open enough to qualify as a demand for heat. I use an input_number so that I can adjust this value, typically I find that 20% valve open isn’t far off a usable trigger state. (to reduce hysteresis).
These entities (one per thermostat) are represented in a group.
if any entity in the group is demanding heat, then the group is in demand heat mode, and an automation will turn the boiler on.
When the group is out of demand heat mode, then an automation will turn the boiler off.
The average demand mode is effectively the same,
I create a new sensor that averages the value opening % of each thermostat (add them together, and divide by the number of thermostats (no surprises there))
and then the automation to turn the boiler on triggers if the averaged demand exceeds the input_number high value (10% seems to work ok)
and the automation to turn off the boiler when the averaged demand is less than or equal to the the input_number low value (5% seems to work).
I’m not sure I have problem necessarily that I need solving. Although I am concerned I could be running the system much more efficiently, and that was after-all the main goal in automating it.
Please send me your thoughts,
1 post - 1 participant
Hello, I have a motion sensor that I would like to use for turning on two lights when it detects motion.
This is the device, as you can see it is working and have just been detecting motion recently:
I have tried to use it as trigger like this:
But without luck, it doesn’t seem to trigger even though it reports that it detected motion.
Any ideas how I can make it trigger?
Link to device: https://www.aqara.com/us/motion_sensor.html
Integration: through smartthings
1 post - 1 participant
I’m just getting started with understanding how the automation works with HA, and setting up a basic outside lights on/off script.
So I want my lights to turn on 15 mins before sunset. Then turn off at midnight. Then turn on later the next morning about about 2 hours before sunrise and then back off at sunrise.
Can you do all of that in 1 script/rule? Or do I need to set up each one separately? I read that you case use ‘for’ to change the state for an XX minutes. But can you change the light to ON and then have go off later at a specific time all in 1 rule?
This is the first have for sunset. Do you need 2 separate?
automation:
- alias: Outside Lights on at Sunset
trigger:
platform: sun
event: sunset
offset: "-00:15:00"
action:
service: switch.turn_on
entity_id: switch.outside_garage_light_switch
entity_id: switch.frontporchlight_switch
- alias: Outside Lights off at 11pm midnight
trigger:
platform: time
at: "23:00:00"
action:
service: switch.turn_off
entity_id: switch.outside_garage_light_switch
entity_id: switch.frontporchlight_switch5 posts - 3 participants
So, I’m looking for a way to track where my home assistant instance is getting HTTP requests from.
I have a text_helper that gets updated with the IP address when a request comes in, and I want to geolocate that IP.
I have a shell scripts that uses the the IPinfo API to get the data, but this is where i’m stuck.
I need to pass the IP address as an argument to that shell script and then get the output and save it to maybe a text_helper in home assistant for tracking.
Does anyone have any idea how to do this or ever propose a better way to do it?
2 posts - 2 participants
Hello, I have created a light group (yeelight) and want to create a custom flow so that both lights have same color / pattern. I have tested with following code and can see it does not works.
It only works when i use that on individual light i.e. downstairs light.
entity_id: light.upstairs_light
action: stay
transitions:
- TemperatureTransition:
- 1900
- 1000
- 80
- TemperatureTransition:
- 1900
- 1000
- 10
Thanks
1 post - 1 participant
Quite often I am finding that my sensors and history stats have stopped updating, Usually a reboot fixes this. It is causing my history stats to become eratic and unreliable.
In this example I am trying to track how long each zone in my house calls for heat. So I have a dry contact relay attached the boiler controller and HA monitors the contacts as a binary sensor and then History stats keeps track of that sensor for 30 days. However it often “messes” up throwing off my entire stats for that month.
You can see in the Pic the History stat went nuts and even reported 15 decimal places when its only ever reported 2 in the past.
- platform: history_stats
name: Kids Room Heat Time
entity_id: binary_sensor.kids_rooms_heat
state: "on"
start: '{{ now().replace(day=1).replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
I have tried migrating over to MariaDB thinking it was a sqlite issue but the issue is still happening.
Is there a “best practice” setup for history stats or even MariaDB or is it just unstable HA??
I am running HA Core 0.116 On Pi4 running on a 120GB solid state drive.
I am not really 100% sure where to start troubleshooting this.
1 post - 1 participant
Hello, I want to improve the behaviour of thermostats.
For that, I will start the heating earlier if the temperature is below one of couple time / temp.
For exemple I will start the heater if:
at 6h30 the temperature is below 18.8 or
at 5h30 if the temperature is below 17,7 or
…
I don’t know how to write the automation…
Many thanks for your help !
Best regards
1 post - 1 participant
I am kind of late in removing custom_header and it is not on HACS anymore to uninstall. Is there a discussion/guide somewhere in the forum that details how to manually remove it? Would prefer an idiot proof guide, if any. 
1 post - 1 participant
I had another thread about battery levels in Lovelace, but during that process I saw that a subset of Zooz ZSE40 multisensors were not exposing entities for battery levels.
For example, this is a problem multisensor I’ve excluded, factory reset and re-included at least 6 times with no change. Other entities are exposed (eg. temp, humidity and burglar) but not battery level:
At first I thought this was a limitation of the Zooz Multisensor, but I noticed other ZSE40 sensors I have DO expose the battery level. Here’s one from our bedroom:
Given the fixes for this stuff is usually an exclude + reset + inclusion loop, and this didnt’ fix it, I’m out of ideas.
1 post - 1 participant
I seem to have a persistent discovery of UPnP/IGD: OnHub on my HA install.
No matter how many times I ignore it, upon the next restart it is auto-discovered again. Even if I add it as an integration it also reappears and I end up with multiple entities.
Any ideas?
1 post - 1 participant
