@Jaques-Ludwig wrote:
I tested the new “helpers”. I used it as dummy-switches.
In the past I programmed those switches in the configuration.yaml. Where are the helpers saved which I created within the UI?Thanks,
Jaques-Ludwig
Posts: 2
Participants: 2
@gnammyx wrote:
Hi,
I need help with 2 Dyson Purifiers, configured in my instance of Home Assistant.
The two different models, one HP04 and one HP02 seems to working ok, but, when I started configuring custom cards for both, I noticed the HP04 doesn’t have the Climate entity.
I don’t know if it’s normal, without the climate entity I can’t control all the functions of the purifier (I’m trying to create a card similar to the Dyson iOS App)
What’s happening? ThanksMy config is
dyson: username: xxxx@xxx.xxx password: xxxxxxxxxx language: IT devices: #HP04 - device_id: A1A-EU-********. device_ip: xxx.xxx.xxx.xxx #HP02 - device_id: PT4-EU-******** device_ip: xxx.xxx.xxx.xxx
Posts: 1
Participants: 1
@koQuarium wrote:
I added an Aeotec Z-wave stick to my Rpi 4b HA-setup and it al works fine.
The disco lights of the stick however drive me crazy.
I know it is possible to turn them of
My question regards the note “You should only do this when Home Assistant has been stopped.”
I normally stop HA from the Supervisor Systems menu, but in that case it is not possible to SSH to the Rpi for entering the required “stop disco command”.
What’s the way to go?
How to stop HA from the command line enabling me to kill the lights?Regards, Ko
Posts: 1
Participants: 1
@swollef wrote:
I am attempting to create an automation that picks up when the washing machine wattage goes over 10
im trying to use the value_template as per the automation trigger docs
trigger: entity_id: sensor.tumble_dryer_power platform: state value_template: "{{ sensor.tumble_dryer_power.replace(' W','')|float }}" to: 'above: 10'im constantly getting the following error:
Message malformed: extra keys not allowed @ data['trigger'][0]['value_template']ive tried changing sensor. to state. within the value_template but this seems to make no difference to the error I receive
any help appreciated as always (still only in my second week with HA)
Posts: 11
Participants: 4
@Pavel-Demidyuk wrote:
Hi,
I’m new to HA, so I’m sorry if my questions is dumb, but I still need some help to understand HA philosophy.
I’ve built some custom mqtt controlled lights and switches using 1-wire and now I’d like to expose them into HA. I’ve added this to configuration.yaml:
light: - platform: mqtt name: "test_lamp" unique_id: "a1c386fc-7777-11ea-bc55-0242ac130003" state_topic: "test_lamp/light/status" command_topic: "test_lamp/light/switch"Ok, now I have test_lamp entity on the home screen. But as long as it’s just an entity, I can’t add it to any area, since I has to be a device then. So I wonder how to turn an entity into a device, but I feel like my question doesn’t make sense and I’m missing something.
Please suggest! Thanks.
Posts: 4
Participants: 3
@AlexanderPCT wrote:
im using
automation: !include_dir_merge_list automation/for my automations.
but the gui uses one big automations.yaml, is it possible to usw BOTH? my own in sperate files and that one big auto-generated?
Posts: 3
Participants: 3
@andyh6278 wrote:
hey guys
hoping thins is an easy one to help with.
Firstly, I am terrible at turning off the side alley light once it is manually switched on to put the bins out. is there a way i can configure that light to switch off after say 15 minutes once a manual activation has occurred? I dont want to set up a sensor out here as the local cats will be setting it off all night long.
Any help would be appreciated, or even just a point to a thread with this on. I have looked, but all I find seems to be triggered by a sensor or automation. I could figure out how to turn those off easily enough.
TIA
Posts: 3
Participants: 2
@MarkR wrote:
Hello
I am getting power readings from a RPIZ_CT3V1 and sending to HA via node red/mqtt… Everything works except i am getting negative values when a certain item is off, -2 or -3 instead of zero. How can I get HA or node red to ignore the negatives or better still make them send just 0 not negative please?
Cheers
Mark
Posts: 1
Participants: 1
@Mariusthvdb wrote:
hi,
coming from here trying t solve some unexpected scripting behavior, Ive turned on home assistant.core: debug, and now notice the group.all_automations, group.all_devices, etc are still in the system…
I’ve havent set them up manually, nor do I use a script to create these groups on startup. I take it it cant be caused by auto-entities cards, but to be sure ive renamed these as follows:
card: type: entities title: All Switchex show_header_toggle: false filter: include: - domain: switch options: secondary_info: last-changed - type: custom:auto-entities card: type: entities title: All Devicex show_header_toggle: false filter: include: - domain: device_trackerAnyone got an idea how these groups can still be logged in the system?
2020-04-06 23:32:22 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=group.all_automations, old_state=None, new_state=<state group.all_automations=on; entity_id=('automation.xxx, listing of all automations, cut her to keep post tidy'), order=61, auto=True, friendly_name=All Automations @ 2020-04-06T23:32:22.444093+02:00>>same for lights, remotes, scripts, switches:
you can spot the manually created ones.
Since maintaining these groups costs a lot of system resources, I would have hoped them to be gone by now…
please have a look, thanks!
Posts: 2
Participants: 2
@thermseekr wrote:
Hello all
I’m running V107.7 and I have Alexa integrated through Nabu Casa. Everything was working fine, I had around 30 entities exposed using YAML under
cloud:in configuration.yaml. When installing my Echo Dot Gen3 for the first time all entities got discovered on the first attempt.A few days ago I decided to try
node-red-contrib-amazon-echoin Node-RED, and for that I had to disable Alexa integration in Home Assistant Cloud.After re-enabling Alexa in Nabu Casa my entities wouldn’t get discovered anymore. A lot (A LOT) of debug hours later I found that if I exposed a given entity - a media_player - nothing would get discovered.
I don’t know if this had any influence, but on the same day I renamed several entities to follow a naming standard I had recently defined, including the mentioned media player.
I went through all configuration files in /config and subfolders trying to find what could be wrong, but found nothing.
Has anyone seen such a behavior before? I really can’t tell if it’s related to home assistant exposing the entity in a wrong way, some problem in the skill running in Alexa, or the Alexa account/service. Looks like this media_player entity is stuck somewhere. It’s a two zone Denon receiver integrated through the native Denon integration. The problem is with the first zone, the second one gets discovered ok.
Thank you for any help.
Tales
Posts: 1
Participants: 1
@Mariusthvdb wrote:
Just to be sure, and before re-starting to use scenes again, please let me ask if we can safely use groups as entities in scene definitions. we could before, but since I cant find any reference to a group on https://www.home-assistant.io/integrations/scene/ I thought it safer to ask any of you who already have used the new scene implementation
thanks for having a look and confirming/negating my question…
Posts: 4
Participants: 4
@Manuel82 wrote:
Hi,
i recognized some (not all) of my input_selects are unavailable since a few days. Also a restart does not help. It also makes no difference if i set a initial value or not. Any ideas how to fix that?
Posts: 4
Participants: 3
@Akriss wrote:
I want to tweak the MariaDB addon settings.
I found the file on my HA server located in.
\addons\core\mariadb\rootfs\etc\my.cnf.d\mariadb-server.cnf
That seems to contain the DB settings I’m after. However the changes made to that file are not persistent.How do I pass along setting to that file?
Many Thanks
Kris.
Posts: 1
Participants: 1
@bcowell wrote:
I’m trying to get AndroidTV notifications to work but I can’t get the service to show up. It seems every time I want to do something it’s a battle.
I have the following code in my configuration.yaml file:
notify: - platform: nfandroidtv name: Loungeroom host: 192.168.0.40I have installed the Notifications for Android TV app on my Nvidia Shield and rebooted. The Shield has a static IP Address. I have rebooted the shield and HA.
I would expect at this point to look in to my services in HA and see a new service called notify.loungeroom but it is not there, why?
I have tried rebooting HA multiple times, moving the notify integration around in my configuration.yaml file but can’t get it to work.
Posts: 1
Participants: 1
@sparkydave wrote:
I am trying to get ZHA working with a Conbee2. I’m running HA on Ubuntu Server on a NUC. After playing around installing the Deconz software in Ubuntu I was then able to add devices to ZHA through the HA config GUI. Not sure if installing Deconz in Ubuntu was required but prior to that I was not seeing the Conbee2 in the ZHA config menu despite it being listed in Supervisor / System / Hardware (in HA side menu)
The two zigbee devices were working perfectly and I was happy… until I restarted HA (for other reasons).
In the HA error log I got the below and the Conbee2 is not showing up in the HA ZHA config menu
2020-04-07 11:20:03 WARNING (MainThread) [zigpy_deconz.api] No response to ‘Command.read_parameter’ command
2020-04-07 11:20:03 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2120390-if00 for zha
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 215, in async_setup
hass, self
File “/usr/src/homeassistant/homeassistant/components/zha/init.py”, line 103, in async_setup_entry
await zha_gateway.async_initialize()
File “/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py”, line 137, in async_initialize
await self.application_controller.startup(auto_form=True)
File “/usr/local/lib/python3.7/site-packages/zigpy_deconz/zigbee/application.py”, line 45, in startup
self.version = await self._api.version()
File “/usr/local/lib/python3.7/site-packages/zigpy_deconz/api.py”, line 310, in version
(self._proto_ver,) = await self[NetworkParameter.protocol_version]
File “/usr/local/lib/python3.7/site-packages/zigpy_deconz/api.py”, line 280, in read_parameter
r = await self._command(Command.read_parameter, 1 + len(data), param, data)
File “/usr/local/lib/python3.7/site-packages/zigpy_deconz/api.py”, line 210, in _command
return await asyncio.wait_for(fut, timeout=COMMAND_TIMEOUT)
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 449, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutErrorI’m not sure how to make sure the Conbee2 works properly on restarts, any ideas?
Posts: 1
Participants: 1
@zamzon wrote:
Hi
I need google home to tell me the state on my window, but it tells my the state on/off not open/closed
- id: '1586112057634' alias: google cloud say description: '' trigger: - at: '10:00:00' platform: time condition: [] action: - data_template: entity_id: media_player.nest_hub message: vinduet i stuen er, {{ states('binary_sensor.stort_vindue') }} service: tts.google_cloud_sayI did set the device type to window, and it shows correct in Lovelace
- id: 83034 name: Stort vindue inverting: true note: Magnet contact position: Stue manget i vindue type: window
Posts: 3
Participants: 2
@eroji1 wrote:
I made a banner-card with card-mod customization for guest wireless information. While this shows up perfectly on my PC browser and HA app on iOS, I’m using a Fire 10 HD with Fully Kiosk. It shows the card with weird border artifact that I can’t figure out how to get rid of.
This is my current card configuration
entities: - entity: sensor.guest_network name: NETWORK - entity: sensor.guest_username name: USERNAME - entity: sensor.guest_password name: PASSWORD heading: - 'mdi:wifi' - Guest Wireless style: | ha-card { overflow: hidden; } ha-card .heading { color: white; font-size: 20px; font-weight: 450; margin-top: 20px; margin-bottom: 15px; } ha-card .entity-value { font-family: Courier New; font-size: 18px; margin-bottom: 10px; } type: 'custom:banner-card'
Posts: 1
Participants: 1
@maurizio53 wrote:
I was using this wait_template with my google home device:
wait_template: "{{ is_state('media_player.home', 'idle') }}"And all was working as expected. Now i want to use that template with one of my echo devices and used this template:
wait_template: "{{ is_state('media_player.echo_show_5', 'idle') }}"But i noticed the echo devices doesn’t go to idle state as it remains always in standby state so the template doesn’t work.
How to change that template to have the automation working again ?
Posts: 4
Participants: 2
@robysan wrote:
Hi all,
i insalled hassio on my raspberry and link it to my domotic knx system. it works very well with every kind of device (lights, covers, etc…) also with alexa (not nabu home cloud). now i connect smartthings because i have a samsung tv and 3 samsung air conditioner. using HA i can control all devices but now i want to control them whit alexa. i tried to search new device but i failed. i think that i’m missing some steps… can anyone help me please? thank you
Posts: 1
Participants: 1
@AhmadK wrote:
Hi All,
I think it won’t harm if I share my method of migrating from UI-configured Lovelace to YAML.
I started using yaml mode recently when the opportunity to create dashboards was introduced so I had my default dashboard in UI mode and created a new one withmode: yaml.
It became apparent that for various reasons I no longer use most of the UI configuration features and on top of that I wanted to try lovelace_gen.
The task is simple - you need to transfer your current Lovelace configuration toui-lovelace.yamland configurelovelaceintegration so it works in yaml mode and uses all necessary resources (if any).
After checking the docs that in yaml mode I’ll still be able to create a UI-controlled dashboard (viaConfiguration -> Lovelace Dashboards) I went ahead and here’s what you need to do:
- Go to Supervisor -> Snapshots and create a full snapshot, just in case.
- On your Overview screen click on three dots in the top right corner and select “Configure UI”.
- Click on three dots again and select “Raw configuration editor”.
- Select all text (
Edit -> Select Allin your browser).- Copy it (
Edit -> Copyin your browser) and click onxsign next toEdit Configuration.- Open your favourite text editor, create a new file and paste your configuration into it (
Edit -> Paste).- Save it as
ui-lovelace.yamlin <Home Assistant configuration folder>- (Optional step if you use any resources i.e custom cards etc.) Open in your editor file <Home Assistant configuration folder>/.storage/lovelace_resources
a. Remove anything apart from entries like"type": "module", "url": "/local/stack-in-card.js"and change them so the result is something likeresources: - url: /local/stack-in-card.js type: module - url: /local/button-card.js type: module ...b. Select all text (`Edit -> Select All`) and copy it (`Edit -> Copy`).
- Open in your editor
configuration.yaml.- Add the following
lovelace: mode: yaml
- If using any resources, paste the copied at step 8 text below
modeso the result islovelace: mode: yaml resources: - url: /local/stack-in-card.js?v=0.1.0 type: module - url: /local/button-card.js?v=20200319 type: module ...Restart your HA and in
Configuration -> Lovelace Dashboardsyou’ll see your default dashboard as ‘Configuration method: YAML file’.Hope it’s useful to someone.
Here is official documentation on yaml mode and dashboards.
Posts: 1
Participants: 1
