@NicolasG wrote:
(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Posts: 1
Participants: 1
@NicolasG wrote:
(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Posts: 1
Participants: 1
@eric_g_atx wrote:
Hello all, I’m using the generic camera snapshot function to grab still images from some recent Dahua cameras. All is working well however it seems to be quite slow in grabbing the image. I’m seeing a 3 to 5 second delay on average. My system is running on a NUC with processor load extremely low. I’ve tried disabling snapshot authentication on the cameras but they’re still a delay. Anyone have some thoughts on what might be wrong? When I hit the url from a browser, the image is quite fast to load.
Posts: 1
Participants: 1
@cabalforces wrote:
Hi! I am trying to control IOT Link on my pc through mqtt with input selects. There are multiple serious issues with this, namely that I am terrible at programming, not familiar with the syntax of jinja or yaml just impatient in general for any kind of debugging. I have tried to basically copy-paste code i have found on the site but of course it does not work.
This is what it looks like:- id: computer_state alias: Power trigger: - platform: state entity_id: input_select.pc_power condition: [] action: - service: mqtt.publish data_template: entity_id: input_select.pc_power option: >- {% set mydict = { 'logoff': 'Log Out' 'lock': 'Lock', 'reboot': 'Reset', } %} {{ mydict.get(action.topic) }} topic: "iotlink/workgroup/odin/commands/{{action.topic}}" payload: ''
And this is the error it throws:
Invalid config for [automation]: invalid template (TemplateSyntaxError: expected token ‘,’, got ‘:’) for dictionary value @ data[‘action’][0][‘data_template’][‘option’]. Got None. (See /config/configuration.yaml, line 48).
Invalid config for [automation]: Entity ID input_select. is an invalid entity id for dictionary value @ data[‘trigger’][0][‘entity_id’]. Got None
expected str for dictionary value @ data[‘id’]. Got None
string value is None for dictionary value @ data[‘alias’]. Got None. (See /config/configuration.yaml, line 48).Line 48 is an enter, with nothing else, line 49 is:
automation: !include automations.yaml
Very helpful.
Thank you in advance for your help
Posts: 19
Participants: 3
@bedfellow wrote:
I have the following scenes in configuration.yaml and I would like to move them to scenes.yaml:
scene: input_boolean: boost: name: Boost icon: mdi:thermometer zigbee_permit_join: #zigbee2mqtt name: Allow devices to join initial: off icon: mdi:cellphone-wireless
I have moved them and added
scene: !include scenes.yaml
to configuration.yaml, but get the following error when I check the configuration:Configuration invalid Invalid config for [scene]: required key not provided @ data['states'][0]['entities']. Got None required key not provided @ data['states'][0]['name']. Got None. (See /config/configuration.yaml, line 20).
My scenes.yaml looks like:
input_boolean: boost: name: Boost icon: mdi:thermometer zigbee_permit_join: #zigbee2mqtt name: Allow devices to join initial: off icon: mdi:cellphone-wireless
What am I doing wrong?
Posts: 3
Participants: 2
@dmitry.mukhach wrote:
I installed HA to pi4 and long time can’t update from Operating System 3.10 to any new version. Now to 3.3.
Got error:20-02-15 15:55:28 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi4-3.10.raucb: 20-02-15 15:55:28 ERROR (MainThread) [asyncio] Task exception was never retrieved future: <Task finished coro=<HassOS.update() done, defined at /usr/src/hassio/hassio/hassos.py:149> exception=HassOSUpdateError()> Traceback (most recent call last): File "/usr/src/hassio/hassio/hassos.py", line 160, in update int_ota = await self._download_raucb(version) File "/usr/src/hassio/hassio/hassos.py", line 110, in _download_raucb raise HassOSUpdateError() hassio.exceptions.HassOSUpdateError
How fix it? How update? Please, help!
Posts: 1
Participants: 1
@pdwonline wrote:
I have homeAssistant running in docker on a nuc using an SSL offloading proxy and seperate mariadb image. (see screenshot from portainer showing the 3 containers running). HomeAssistant seems unable to connect to the database image based on the docker image name (which is ‘mariadb’ in my case. I have created a database and user and granted the user rights to the database. here is the prhrase of my config that define the connection in homeAssistant
dbconnection: mysql://hassuser:@mariadb/hass_db
When I start HomeAssistant, the log says:
2020-02-15 17:55:36 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (MySQLdb._exceptions.OperationalError) (2005, “Unknown MySQL server host ‘mariadb’ (-2)”)
Since I have set this up succesfully in the past I must be overlooking something stupid…
Posts: 6
Participants: 3
@PieBru wrote:
Hi all,
Inside and outside my home I have more than a dozen of cheap 433 MHz temperature/humidity sensors like this:
I’m structuring my configuration.yaml much like Frenck and others did, so I’m grouping those RF sensors in a
rtl_433
directory containing one yaml file for each sensor. I welcome better solutions.All those RF sensors all working well, but spanning any configuration patch/innovation/update on every sensor .yaml file is asking for troubles.
So I’m looking for a better way to define them, some alternative to copy/paste 50 yaml lines each.In my dreams, the only difference could be something like assigning the unique “id” to a “parameter” like ${rtl433_temp_humid_id} (“190” in the example below) and then including a templated file.
My actual definition(s):
## Analog sensors: https://www.home-assistant.io/integrations/sensor.mqtt/ # rtl_433/Nexus-TH/190/2 {"time":"2020-02-04 11:42:39","model":"Nexus-TH","id":190,"channel":2,"battery_ok":1,"temperature_C":20.4,"humidity":54} - platform: mqtt state_topic: "rtl_433/Nexus-TH/190/+" name: "rtl433_NexusTH_190_rawtemp" device_class: temperature # https://www.home-assistant.io/integrations/sensor/#device-class unit_of_measurement: "°C" expire_after: 180 # Defines the number of seconds after the value expires if it’s not updated. force_update: true # Sends update events even if the value hasn’t changed. Useful if you want to have meaningful value graphs in history. value_template: "{{ value_json.temperature_C }}" # https://www.home-assistant.io/docs/mqtt/processing_json/ - platform: filter # https://www.home-assistant.io/integrations/filter entity_id: sensor.rtl433_NexusTH_190_rawtemp name: "rtl433_NexusTH_190_temperature" filters: - filter: outlier window_size: 4 radius: 2.0 - filter: lowpass time_constant: 10 precision: 1 - filter: time_simple_moving_average window_size: 00:20 # HH:MM precision: 1 - platform: mqtt state_topic: "rtl_433/Nexus-TH/190/+" name: "rtl433_NexusTH_190_rawhumid" device_class: humidity unit_of_measurement: "%" expire_after: 180 force_update: true value_template: "{{ value_json['humidity'] }}" - platform: filter entity_id: sensor.rtl433_NexusTH_190_umidity name: "rtl433_NexusTH_190_umidity" filters: - filter: outlier window_size: 4 radius: 2.0 - filter: lowpass time_constant: 10 precision: 1 - filter: time_simple_moving_average window_size: 00:20 # HH:MM precision: 1
BTW I’m open also to more efficient filtering tricks
to smooth the graphing and reduce value changes, as each one generates a DB update.
Any hint?
Thanks,
Piero
Posts: 1
Participants: 1
@pdwonline wrote:
I have restored HomeAssistant to another NUC since the one Home Assistant was running on crashed. On my backup I have copied the .storage folder including the account information. For some reason this seems not to work. After restore I started Home Assistant and It was starting in onboarding mode asking for a new owner account setup. Ok fare enough, I entered account details and pressed the blue button ‘account aanmaken’ (because I use a Dutch version), but nothing happens.
Then I decided to do the account reset procedure as described on the site, by removing some auth files form the .storage folder. (I do this using a local network connection on http://192.168.0.26)
Again nothing happens when I press the button… What am I doing wrong, and why is my backup not simply working?
Posts: 1
Participants: 1
@Koffeinuser wrote:
I have a FGD-212 Fibaro dimmer where I today control a floor lamp with the 2nd button - all done within the Vera.
I’d like to catch when the 2nd button (Group ID 2 in Vera) is pressed. Do anyone have a suggestion on how to do this?
The purpose is to control a WiFi or a Zigbee device from the Fibaro button.
Posts: 1
Participants: 1
@Canedje wrote:
Hello,
Today is did start up my new Raspberry Pi 4B with HA.
I’m coming from a Homey and want to migrate to HA.
I installed HA, Samba, the configurator, Node-RED and DuckDNS. All working fine.
I installed a ZWAVE.me and Zigbee Conbee II Dongle (deCONZ) after some trouble also running fine.
I added a NEO coolcam wallplug as test for ZWAVE and a Xiaomi doorsensor at deCON.
Also succeeded that.The questions I have:
I did try to start a simple Que in Node-RED switching the NEO Coolcam wallplug on and off depending o the state of the Xiami Door Sensor.In the even-state tile I do see the NEO coolcam entity ID but not the Xiaomi Zigbee sensor as an option to chose?
Where to find the Zigbee door sensor? Or did I install the Zigbee wrong.
Beside this the Zwave NEO coolcam is showen in the overview, I don’t see the Zigbee sensor?If I look at the deCONZ part I can see the doorsensor and also changing the state
I’m a newbee so please help.
Posts: 1
Participants: 1
@Arsenal10108 wrote:
I am trying to set up a history states sensor to simply count the total time a switch is set to the on position. Should be pretty simple but its kicking my butt
I don’t have any special configs for History or Recorder, for recorder I just have Purge_keep_days: 30
Basically its a D1 Mini(tasmota) that will be tied to the contacts of a relay. So when the relay contacts close it sets the switch to on, when they open: off. The coil side of the relay will be tied to my Oil Boiler pump to get actual run time of the burner.The sensor for the tasmota topic works as it updates HA with on or off perfectly but the history stats just shows as unknown.
Here is the config I am trying to work with
#Oil Boiler Sensor History - platform: history_stats name: Boiler time entity_id: sensor.boiler_switch state: "ON" end: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}' duration: days: 30 #Oil Boiler Switch Sensor - platform: mqtt state_topic: stat/Boiler/POWER name: boiler switch
Posts: 6
Participants: 3
@raymondoooo wrote:
I’m looking to see if anyone has a way to display the average time that the HVAC fan runs daily. I have the sensor that shows me on/off, but I would love to be able to see the avg. time that the fan runs every day. I was torn on how to do this and figured I would see if anyone has already pulled off something like this.
I do also do have grafana/influxdb configured, I’m sure I could put something in there then present it over to HA, but I don’t even know where to start to setup something like this in there.
Any thoughts?
Posts: 4
Participants: 3
@JamesDenby wrote:
Hello all,
I am a quite the Noob, but I have managed to get most things working. I am doing an updated Home Assistant Core on a Rpi4 (fresh install) and in preparation I will be using ZHA with the Nortec dongle (used deCONZ in my last install). I then went to configuration > integrations > and scrolled down to find ZHA. I can’t find it. At first I thought maybe my spelling was wrong but it is unavailable on both my installs. Here is what I am presented with:
I also searched to see if I could find any documentation that mention it no longer being available. Am I missing something? Has this been deprecated?
Thank you for your guidance and suggestions.
Posts: 3
Participants: 2
@ColoradoAutomator wrote:
My Raspberry Pi 3B running HASSIO locked up twice recently so I concluded that the uSD card was bad. After reintstalling HASSIO on a new card and enabling the Z-Wave integration, HA finds all of my Z-Wave devices but for the switches, where Overview used to display sliders that allowed me to control the swtiches, it now only displays their status of “Ready”. How do I get back to having switch controls in the interface?
Posts: 1
Participants: 1
@gromar wrote:
First of all I decided to switch on/ off ventilation using Xiaomi switch.
The automation looks like that (and it works flawlessly):# Załączamy/ Wyłączamy Wentylator w Łazience - alias: Załącz/ Wyłącz Wentylator w Łazience trigger: platform: event event_type: xiaomi_aqara.click event_data: entity_id: binary_sensor.switch_158d000373c264 click_type: single action: service: switch.toggle data: entity_id: switch.przelacznik_lazienka_wentylator
Next thing I decided to add is a delay to auto-switch off after 5 minutes if I forget to press a button. I modified the code:
# Załączamy/ Wyłączamy Wentylator w Łazience - alias: Załącz/ Wyłącz Wentylator w Łazience trigger: platform: event event_type: xiaomi_aqara.click event_data: entity_id: binary_sensor.switch_158d000373c264 click_type: single action: - delay: '00:05:00' - service: switch.off entity_id: switch.przelacznik_lazienka_wentylator
I can switch it on/ off via pressing a button but unfortunately the delay doesn’t work. What’s wrong with the code here?
Posts: 4
Participants: 3
@jmadden91 wrote:
Hi, is it possible at all to download the still image that homeassistant uses as a preview for Ring camera’s last video?
Basically now that the android app can receive images in notifications, I want to send a notification to my phone when there is motion at the front door with a still image of the latest video. Just like how they show up in homeassistant.
Thanks
Posts: 1
Participants: 1
@JayF wrote:
Good day,
I’m trying to figure out a way thereit would be possible to have the lovelace navigation sideways, on the left. idealy, I would like to remove the Home Assistant hidden menu as well. Please see screenshot:
If it is not possible to move my navigation menu item on the left, would it be possible to center those in the middle of the blue menu bar?
Thanks for your help!
Posts: 2
Participants: 2
@rs443 wrote:
As the default group.all_lights are no longer automatically maintained, you are supposed to use entity_id: all in service: light.turn_on/off. Pretty straightforward. But how do you call all the lights when using them in an automation?
I have an automation that triggers when all lights are off, like this:
- alias: Automation X trigger: - platform: state entity_id: group.all_lights to: 'off' for: minutes: 20
Is there an easy way to replace the group.all_lights here? Without manually create a group containing all lights.
Posts: 3
Participants: 3
@bigverm23 wrote:
can someone please help me understand why this is failing?
Invalid config for [automation]: [platform] is an invalid option for [automation]. Check: automation->condition->0->platform. (See /config/configuration.yaml, line 12).
- id: work_leave alias: Leave Work trigger: platform: zone entity_id: device_tracker.life360_ken zone: zone.dc3 event: leave action: service: notify.gmail data: message: Ken has left work - id: work_arrive alias: Arrive At Work trigger: platform: zone entity_id: device_tracker.life360_ken zone: zone.dc3 event: enter action: service: notify.gmail data: message: Ken has arrived at work - id: sunset_lights alias: Lights on at sunset trigger: platform: sun event: sunset offset: "-00:15:00" condition: condition: state entity_id: sensor.home_occupied state: 'Occupied' action: entity_id: scene.sunset_lights service: scene.turn_on - id: office_day_motion alias: Office Motion office_day_motion trigger: platform: state entity_id: binary_sensor.office_sensor to: 'on' condition: platform: sun after: sunrise before: sunset action: - service: timer.start entity_id: timer.office_motion - service: light.turn_on data: kelvin: 2700 brightness: 254 transition: 10 entity_id: light.officedesk - id: office_timer alias: Turn off office after no motion (10 mins) trigger: platform: event event_type: timer.finished event_data: entity_id: timer.office_timer condition: condition: state entity_id: binary_sensor.office_sensor state: 'off' action: service: light.turn_off data: transition: 10 entity_id: light.officedesk
Posts: 5
Participants: 3
@TheQue42 wrote:
I’ve been trying to figure out the url/media_content_id for any video on my synology nas.
Wiresharking have shown that VLC will use a GET to http://10.9.24.28:50001/v/NDLNA/22556.mp4 (although a relative url) but whatever combo I try to use I cant get it to work.
Swiching source works fine. But how am I to figure out the url for play?I am on 0.104.2 currently.
Posts: 1
Participants: 1