I understand that Wiz lights are now supported by Home Assistant. Currently, I’m using the HACS integration and the lights work fine. Did I need to do anything special to switch over to Home Assistant integration? Thanks for support. Gary
1 post - 1 participant
Hi, I have some shelly devices (e.g. 3EM) on Hassio, using shelly integration. Everything works very fine, but I notice that the status of the sensor (e.g. Power, current, voltage) is updating very fast, and for this reason Influx database is growing very fast. Is there a way to reduce the update of the sensor?
I do not want to delete old data (e.g. < 1 year). I want to mantain the data, but having a low sensor frequency update .
Thanks
4 posts - 2 participants
Hello!
I have a question regarding the “Entity IDs”, because they are starting to drive me crazy 
The following problem… when switching to another ZigBee stick, the previous devices were listed, but no connection could be established. The only option was to put each device into pairing mode again and have HA detect it.
However, this created new entity IDs. With a fatal consequence… all automations in which the “old devices” were selected, do not work anymore. Absolute chaos!
In the user/people interface, I can select a track device, so that you do not have to change the automations, if there is a new device or an additional should be added.
Is there something like that for Devices/Entity IDs? So that you can assign a name to a device and then assign an entity ID to it?
It can’t be that you always have to change all automations when you change Entity IDs. That is total madness!
I hope it is understandable what I wanted to explain!? ;-))
Thanks in advance for any tips and help!
Take care!
1 post - 1 participant
Hello,
I am trying to have a basic automation to turn the light on when my sonos alarm clock turns on. I am using the GUI interface to automate:
but somehow, it does not work out: the light switch on randomly during the day. Any idea ?
Many thanks
Philippe
1 post - 1 participant
Hi,
i want to create a sensor that takes the next three hours cost and give an average cost. The sensor has the following attributes (see below), I were thinking to use the “today:” values, there is one value per hour (24). But i am completely lost how to get this working. I will use this average value to steer what appliances that can run and not based on the price.
current_price: 3
average: 3.4
off_peak_1: 3.1
off_peak_2: 2.8
peak: 3.2
min: 1.3
max: 9.1
unit: kWh
currency: SEK
country: Sweden
region: SE3
low price: true
tomorrow_valid: true
today: 2.1, 1.3, 1.6, 2.1, 2.4, 3, 3.2, 9.1, 8.6, 5.4, 3.1, 2.9, 2.8, 2.8, 2.8, 2.9, 2.7, 3.2, 3.7, 3.4, 3.1, 3, 2.9, 2.2
tomorrow: 2, 2, 1.9, 1.8, 2.2, 3, 3.4, 7.9, 7.4, 3.3, 3.2, 3.1, 3.1, 3, 3, 3, 3, 3.1, 3.1, 3.1, 3, 3, 1.1, 0.4
raw_today:
- start: '2022-03-08T00:00:00+01:00'
end: '2022-03-08T01:00:00+01:00'
value: 2.1
- start: '2022-03-08T01:00:00+01:00'
end: '2022-03-08T02:00:00+01:00'
value: 1.3
- start: '2022-03-08T02:00:00+01:00'
end: '2022-03-08T03:00:00+01:00'
value: 1.6
- start: '2022-03-08T03:00:00+01:00'
end: '2022-03-08T04:00:00+01:00'
value: 2.1
- start: '2022-03-08T04:00:00+01:00'
end: '2022-03-08T05:00:00+01:00'
value: 2.4
- start: '2022-03-08T05:00:00+01:00'
end: '2022-03-08T06:00:00+01:00'
value: 3
- start: '2022-03-08T06:00:00+01:00'
end: '2022-03-08T07:00:00+01:00'
value: 3.2
- start: '2022-03-08T07:00:00+01:00'
end: '2022-03-08T08:00:00+01:00'
value: 9.1
- start: '2022-03-08T08:00:00+01:00'
end: '2022-03-08T09:00:00+01:00'
value: 8.6
- start: '2022-03-08T09:00:00+01:00'
end: '2022-03-08T10:00:00+01:00'
value: 5.4
- start: '2022-03-08T10:00:00+01:00'
end: '2022-03-08T11:00:00+01:00'
value: 3.1
- start: '2022-03-08T11:00:00+01:00'
end: '2022-03-08T12:00:00+01:00'
value: 2.9
- start: '2022-03-08T12:00:00+01:00'
end: '2022-03-08T13:00:00+01:00'
value: 2.8
- start: '2022-03-08T13:00:00+01:00'
end: '2022-03-08T14:00:00+01:00'
value: 2.8
- start: '2022-03-08T14:00:00+01:00'
end: '2022-03-08T15:00:00+01:00'
value: 2.8
- start: '2022-03-08T15:00:00+01:00'
end: '2022-03-08T16:00:00+01:00'
value: 2.9
- start: '2022-03-08T16:00:00+01:00'
end: '2022-03-08T17:00:00+01:00'
value: 2.7
- start: '2022-03-08T17:00:00+01:00'
end: '2022-03-08T18:00:00+01:00'
value: 3.2
- start: '2022-03-08T18:00:00+01:00'
end: '2022-03-08T19:00:00+01:00'
value: 3.7
- start: '2022-03-08T19:00:00+01:00'
end: '2022-03-08T20:00:00+01:00'
value: 3.4
- start: '2022-03-08T20:00:00+01:00'
end: '2022-03-08T21:00:00+01:00'
value: 3.1
- start: '2022-03-08T21:00:00+01:00'
end: '2022-03-08T22:00:00+01:00'
value: 3
- start: '2022-03-08T22:00:00+01:00'
end: '2022-03-08T23:00:00+01:00'
value: 2.9
- start: '2022-03-08T23:00:00+01:00'
end: '2022-03-09T00:00:00+01:00'
value: 2.2
raw_tomorrow:
- start: '2022-03-09T00:00:00+01:00'
end: '2022-03-09T01:00:00+01:00'
value: 2
- start: '2022-03-09T01:00:00+01:00'
end: '2022-03-09T02:00:00+01:00'
value: 2
- start: '2022-03-09T02:00:00+01:00'
end: '2022-03-09T03:00:00+01:00'
value: 1.9
- start: '2022-03-09T03:00:00+01:00'
end: '2022-03-09T04:00:00+01:00'
value: 1.8
- start: '2022-03-09T04:00:00+01:00'
end: '2022-03-09T05:00:00+01:00'
value: 2.2
- start: '2022-03-09T05:00:00+01:00'
end: '2022-03-09T06:00:00+01:00'
value: 3
- start: '2022-03-09T06:00:00+01:00'
end: '2022-03-09T07:00:00+01:00'
value: 3.4
- start: '2022-03-09T07:00:00+01:00'
end: '2022-03-09T08:00:00+01:00'
value: 7.9
- start: '2022-03-09T08:00:00+01:00'
end: '2022-03-09T09:00:00+01:00'
value: 7.4
- start: '2022-03-09T09:00:00+01:00'
end: '2022-03-09T10:00:00+01:00'
value: 3.3
- start: '2022-03-09T10:00:00+01:00'
end: '2022-03-09T11:00:00+01:00'
value: 3.2
- start: '2022-03-09T11:00:00+01:00'
end: '2022-03-09T12:00:00+01:00'
value: 3.1
- start: '2022-03-09T12:00:00+01:00'
end: '2022-03-09T13:00:00+01:00'
value: 3.1
- start: '2022-03-09T13:00:00+01:00'
end: '2022-03-09T14:00:00+01:00'
value: 3
- start: '2022-03-09T14:00:00+01:00'
end: '2022-03-09T15:00:00+01:00'
value: 3
- start: '2022-03-09T15:00:00+01:00'
end: '2022-03-09T16:00:00+01:00'
value: 3
- start: '2022-03-09T16:00:00+01:00'
end: '2022-03-09T17:00:00+01:00'
value: 3
- start: '2022-03-09T17:00:00+01:00'
end: '2022-03-09T18:00:00+01:00'
value: 3.1
- start: '2022-03-09T18:00:00+01:00'
end: '2022-03-09T19:00:00+01:00'
value: 3.1
- start: '2022-03-09T19:00:00+01:00'
end: '2022-03-09T20:00:00+01:00'
value: 3.1
- start: '2022-03-09T20:00:00+01:00'
end: '2022-03-09T21:00:00+01:00'
value: 3
- start: '2022-03-09T21:00:00+01:00'
end: '2022-03-09T22:00:00+01:00'
value: 3
- start: '2022-03-09T22:00:00+01:00'
end: '2022-03-09T23:00:00+01:00'
value: 1.1
- start: '2022-03-09T23:00:00+01:00'
end: '2022-03-10T00:00:00+01:00'
value: 0.4
unit_of_measurement: SEK/kWh
icon: mdi:flash
friendly_name: nordpool_kwh_se3_sek_1_095_025
1 post - 1 participant
Sorry all, but looked for a long time.
Really new to this.
Roommate wants me to do the graphics and I found kibibits.
Looks great.
Having trouble doing this.
quote
Right now, this theme requires you to add the Comfortaa font as a resource to your lovelace configuration:
resources:
- url: https://fonts.googleapis.com/css?family=Comfortaa&display=swap
type: css
quote
I can goto the the hidden directory of .storage and
nano lovelace
or
lovelace.michelle_test.
But not a clue where to add it.
here is lovelace
Sorry cannot copy outof nano.
its the default lovelace file.
Where do I put the 3 lines from above.
thanks all
2 posts - 2 participants
My living room media centre isn’t too complex. TV has a Roku Streaming stick, Sonos Beam used mostly for TV sound but also music, and a PS4.
Problem? I currently have three mini media players on my dashboard and would love to condense them into one. I did try and configure a universal media player a while back with limited success. Seems straightforward that I’d want the currently active media player showing cover art, volume controls fixed on the Sonos Beam, and play pause etc. on either the Roku or Sonos depending on which is playing. When I tried before I couldn’t get the state/child player to switch reliably depending on activity.
Does anyone do a similar thing and willing to share some tips/advice before I give it another bash?
1 post - 1 participant
I bought a Broadlink rm4 mini (I already have two perfectly integrated rm3 mini).
I added the device to the app, configured the wifi with fixed ip, and disabled the lock.
However, the integration is not detected, trying to enter it manually with the ip address I get: device not supported.
How can I solve?
Thx
2 posts - 2 participants
I would like to add some sort of button with an editable value to HomeAssistant, in such a way that if I edit it, it sends the value as MQTT command to Tasmota, right from the Lovelace desktop.
Specifically, I would like to be able to easily make ad-hoc changes to Tasmota MaxPower setting. So set it to 1000W one day, and 2000W another day.
I did find I likely need to give a MQTT command like this but how to do this from a self made sensor is something I would appriciate some example.
1 post - 1 participant
Since updating to core_2022.2.9, my single Z-Wave device has become practically unusable. Originally I was using ZWaveJS2MQTT but I took the downtime as an opportunity to switch to the official ZWaveJS addon, the symptoms are the same:
The lock will sometimes respond to lock/unlock commands, but much slower than it used to. Sometimes it just doesn’t do anything. This happens within HASS and also in HomeKit.
When physically turning the bolt, the lock state in HASS and HomeKit rarely changes. Either it’ll update a few minutes later or it will simply show the incorrect state. This too used to be instant.
I have tried excluding and re-pairing and have had no luck. I’ve tried with and without my USB extension and in different USB ports. Changed out the batteries on the lock too. I briefly thought I’d fixed things, the network seemed responsive again, but 10 mins later, nothing.
Currently running HASS OS on a Pi 4
1 post - 1 participant
Tried to search, but could not find it.
As I noticed an automation did not stop after the duration set in trigger, I start to wonder why. Only thing I did was adding new automations during that time.
Is it true that a duration is reset/gone when editing/saving a new automation during the time the automation with the duration was started? Hope you know what I mean?
1 post - 1 participant
I have the following sensor:
- platform: rest
name: Temperature
scan_interval: 10
resource: http://xxx.xxx.xxx.xxx?id=21
json_attributes:
- Temp
value_template: >
{{ value_json['Temp'] | float }}
This works fine, but I want to add a temperature icon. Is this possible? I tried several options, but they seems not to work with a rest platform!
2 posts - 2 participants
I’m trying to run a script which turns on my LG WebOS TV and plays a Plex video playlist for my kids from their account.
They have a seperate Plex account called “kids”, and the playlist I want to run is saved under this account.
I’ve managed to get the script working in as far as I can turn on the TV run plex and then succesfully run the media_player.play_media service, and run playlists I have created under my account.
The problem is the service only seems to play media from my Plex user account.
I want to run media_player.play_media using the kids Plex account rather my mine. Is there a way to do this?
1 post - 1 participant
Early this morning the SMA integaration and/or my solar inverter sent some bad data into the yield entity
but restored itself to the original value a couple of hours later. The consequence is that the Energy dashboard recorded this as a 141kWh entry at 06:00.
I have tried with updating the statistics SQL entries for the failing two hours, both the states field as well as correcting the following sum field, but the correction is not reflected in the entity history nor in the Energy dashboard.
update "statistics_short_term" set state=141.625 where metadata_id=190 and state=0
and
update "statistics" set state=141.625 where metadata_id=190 and state=0
Is there any additional table that needs to be updated in order to set things straight?
2 posts - 2 participants
Using ZHA can anyone explain or point me in the direction of what the number, colours and different types of numbers mean?
I have red, grey single digit numbers from 0 to 107 I have one line that say 1/1 another with 87/156.
One device that has no line to anything but seems to work just fine.
1 post - 1 participant
I need the “for idiots” path to do the following, hopefully a pre-published blueprint that I can modify with ease:
I’d like to use my ring doorbell (or even my blink camera) to change the state of an RGBW (Tuya) light bulb when motion is detected. So, motion at my side door (Ring), change fireplace light to red. After motion clears, resume the original state of the light. During the day, the light is off unless foul weather, at night - the light is typically blue.
I think I understand what needs to take place here - motion detected, grab current on/off and color, store it, turn light red … motion clear, turn light back to state previously stored.
Is this possible? Can anyone assist or point me in the “for idiots” direction?
Thanks!
2 posts - 2 participants
Hi there,
i have HA running on my little Debian based Server and it runs very well!
Beside i also have a PI3 running doing some MQTT things.
I want to have HA installation running on the PI too, but it must be 1:1 copy of the running system.
Goal is: if the Server dies or HDD gets defected or PSU gets bad , the PI should overtake and keep HA running.
Must be a kind of forwarding from PI to Server .
But if the config files are stored at another safe place, can PI & Server get same acces to files?
Or is a realtime copy of the files better?
Is there a possibility to do something like this?
Any Ideas to this?
1 post - 1 participant
I have had an external MQTT server defined in my configuration.yaml file for ages. With the upgrade to 2022.3.x, I see that the use of the Configuration.yaml entry is deprecated. Has anyone removed this and used the integrations panel to add it back? Did it change any of your sensors/devices using MQTT?
Log Details (WARNING)
Logger: homeassistant.components.mqtt
Source: helpers/config_validation.py:817
Integration: MQTT ([documentation](https://www.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: 4:51:41 PM (4 occurrences)
Last logged: 4:51:41 PM
* The 'broker' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'discovery' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'password' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'username' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
2 posts - 2 participants
I am following Mark Watt Tech’s guide on creating Alexa Actionable Notifications. I am at the stage where I post the Github script on Home Assistant but I am getting the error: “Message malformed: extra keys not allowed @ data[‘script’]”
What am I doing wrong? Here’s the script:
script:
activate_alexa_actionable_notification:
description: 'Activates an actionable notification on a specific echo device'
fields:
text:
description: 'The text you would like alexa to speak.'
example: 'What would you like the thermostat set to?'
event_id:
description: 'Correlation ID for event responses'
example: 'ask_for_temperature'
alexa_device:
description: 'Alexa device you want to trigger'
example: 'media_player.bedroom_echo'
sequence:
- service: input_text.set_value
data:
entity_id: input_text.alexa_actionable_notification
value: '{"text": "{{ text }}", "event": "{{ event_id }}"}'
- service: media_player.play_media
data:
entity_id: "{{ alexa_device }}"
media_content_type: skill
media_content_id: amzn1.ask.skill.3c5se72-47b2-430-a43-d134543949a
1 post - 1 participant
I’m a noob and it’s been less than a week since I’ve moved from HE to HA. The transition has gone well but I’m stuck at 1 issue I’m having which is more of a reflection on me than it is on HA. I have an automation that turns off all the lights in the house. However I do not want to be able to execute the automation when a door is open. I have tried several variations but cannot get it to prevent the automation from running.
platform: device
device_id: fed4a3e5fbd0fc2926ddb5dc3ee3f632
domain: zwave_js
type: event.value_notification.central_scene
property: scene
property_key: '002'
endpoint: 0
command_class: 91
subtype: Endpoint 0 Scene 002
value: 2
condition: state
entity_id: binary_sensor.samjin_multi_490e0301_ias_zone
state: Closed
service: scene.turn_on
target:
entity_id: scene.goodnight
metadata: {}
Thanks for any help you can provide.
2 posts - 2 participants