I’m currently using my Tasmota devices using the native MQTT discovery mode offered by earlier versions of Tasmota (I’m on 8.3.1) but I see there’s a new Tasmota integration. What would be the benefit of moving to the new integration?
I see that both need a running MQTT server so I can’t see why I would want to switch.
1 post - 1 participant
Hi,
I this YAML running, it reads my PV power meter. it works fine, except that my power meter sometimes report a negative number.
sensors:
smartmeter_import:
device_class: power
unit_of_measurement: 'kWh'
value_template: '{{ states.sensor.smartmeter.attributes["CounterReadingImport"]|float }}'
is there a way to ignore a value that less that last good reading ?
6 posts - 3 participants
Like many on here, I am looking for a candidate video doorbell that “does it all”. This being namely:
So there we are.
I’m looking at this:
https://www.heyimhome.co.uk/all-products/smart-video-doorbell?gclid=CjwKCAiA-_L9BRBQEiwA-bm5fr22orZcEzdbhgyGH06anQCOfC_g4VgBSKohmCfh1IoWeYsRnlxP7BoCfEkQAvD_BwE
Key thing here is that it - like many - is Alexa/Google compatible. I’m a python developer and did a lot with IPTV dreamboxes etc. I dont run Alexa or Google Assistant nor do I wish to. Question I have is if devices are Google/Alexa compatible, then should that mean it could be integrated into HA. For example if the “Skills” are source code that is available on the web, then it might be able to emulate the interactions as an integration / component. Is this the case? Are there any examples you know of that I could look at?
1 post - 1 participant
Hi all – first post, and excited to join this community. I’ve been working to integrate my Home Assistant universe for control and status in HomeKit for my iOS devices. I’m having mostly success at the moment, but I’m wondering if anyone has insights or suggestions about troubleshooting the following frustrating functionality quirk.
This all WORKS:
From iOS14.2 iPhone or iOS 14.2 iPad:
“Hey Siri, turn on the lights in the Kitchen”
-> instant response (through HASS -> zwave)
“Hey Siri, turn open the shades in the Bedroom”
-> instant response (through HASS -> zwave)
Manually changing the device state in the iOS Home app on either device also functions as expected.
DOESN’T WORK:
If I talk the same commands above to my new HomePod mini, it always responds,
“Sorry, I did not hear back from your devices.”
I have a HomeKit certified LG TV. I can control that TV (eg. power on/off) by voice command to HomePod mini, or in the iOS Home App. This tells me the issue is some interrelation between the HomePod and HASS homekit integration, not simply a problem with the HomeKit Mini.
I did a factory reset of the HomePod mini and after new setup arrived back to the same state - no change in behavior.
All my mobile devices are on the same WiFi router.
I am using the logger integration and DEBUG for HomeKit. I see normal looking communication activity between my iOS devices and the homekit integration in the logs. When issuing a voice command to the HomePod mini, I do not see any homekit integration log activity, but the HomePod of course says, “Sorry, I did not hear back from your devices.”
Can anyone report successful HomePod control to HASS devices via the integration?
How might I troubleshoot this further?
By the way, I set up the HomeKit Integration (by configuration.yaml) following the steps in the documentation.
1 post - 1 participant
So, I have a weird problems. I have two Z-Wave thermostats both same model for upstairs and downstairs.
On the upstairs one, I cannot see the target temperature
However, on the downstairs one, I can.
I can restart home assistant multiple times and it randomly shows up. But it is not consistent and I haven’t been able to figure why this is not working.
1 post - 1 participant
Hello, I’m a bit new to templates. I’m trying to achieve Alexa Announce using notify.alexa_media service, but with some state attributes.
For example, I can get this working easily:
message: It is currently {{states.weather.thermostat.state}} and {{state_attr(‘weather.thermostat’, ‘temperature’)}}
But I would also like to include the high/low forecast for today, which appears in state attributes, but it appears with the rest of the week’s forecast like below. How do I call those state attributes that have many with the same title? In the below example, I’d like to call the first set of temperature: and templow:
temperature: -4
humidity: 56
pressure: 1030
wind_bearing: 335
wind_speed: 7
visibility: 16
attribution: ‘Ecobee weather provided by FI:CYND at 2020-11-24 16:02:40 UTC’
forecast:
- condition: sunny
temperature: -2
templow: -8
wind_bearing: 335
wind_speed: 7
datetime: ‘2020-11-24T16:19:45.547530+00:00’- condition: snowy
temperature: 3
templow: -5
wind_bearing: 100
wind_speed: 6
datetime: ‘2020-11-25T16:19:45.547530+00:00’- condition: rainy
temperature: 5
templow: 1
wind_bearing: 94
wind_speed: 6
datetime: ‘2020-11-26T16:19:45.547530+00:00’- condition: rainy
temperature: 5
templow: 2
wind_bearing: 217
wind_speed: 3
datetime: ‘2020-11-27T16:19:45.547530+00:00’- condition: rainy
temperature: 5
templow: 1
wind_bearing: 259
wind_speed: 7
datetime: ‘2020-11-28T16:19:45.547530+00:00’
friendly_name: Thermostat
Thanks for bearing with me. 
1 post - 1 participant
I am trying to get remote access working for ha. i have followed multiple treads and videos, but not one of them is working for me. Is there a updated easy to follow thread that explains how to do it?
1 post - 1 participant
Hi Guys
I bought the Wifi Smart garage door opener and it works with Tuya. I have used the Tuya integration & its working fine with the App & Google. I can open & close the garage door with HA however it comes up as a Switch.
Is there a way that it can come up as a Door and show the door open or closed etc.
Thanks
1 post - 1 participant
as per https://github.com/home-assistant/core/issues/23506
I’m using Mosquitto 1.6 with LetsEncrypt Certs which work fine using something like MQTT Explorer. But when I try and shift HA to use the encrypted port it fails to connect and in the Mosquitto Logs I see :
1606242033: New connection from 192.168.1.100 on port 8883.
1606242033: OpenSSL Error[0]: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
1606242033: Socket error on client , disconnecting.
looks like the previous solution was to ass tls_version: tlsv1.2 to the config file but this doesn’t work with HA > 115.
Any one got any advice ?
1 post - 1 participant
Was having trouble with the phone app… I uninstall from the phone, delete from the integration… now it doesn’t show there…
I reinstall the app… and it just connects up! as if nothing ever happened… but … it doesn’t show up in the mobile phone integration! It’s not a device that’s recognized… there’s no device_tracker entry. What do I do to get the phone registered?
Also just noticed that when I reinstall it and it connects up on its own… it seems to have the Device Name the same as my old phone! So I think google is doing something dumb where it’s restoring old config files when I install the app?
But then, if I go in and delete all the data from settings > apps in android… then the next time I run it it tries to onboard, but when I click the instance it just hangs… nothing happens, the onboarding doesn’t occur. The only thing that works is uninstall the app and reinstall and then it magically reconnects.
1 post - 1 participant
Hello,
I’m new to Home Assistant and I don’t get the creation of custom cards.
If I add the card for my Bravia TV there is a button for turning it on and if I turn it on I can control the Volume. But if I click on the cast-icon, I can switch the program and see what I’m watching. I want these controls to be on the frontpage of my remote, but I can’t figure out if it’s possible at all.
Can somebody help me with this issue?
1 post - 1 participant
Hi all
I’ve followed the instructions at https://www.home-assistant.io/integrations/nest/ . and https://developers.google.com/nest/device-access/get-started
Successfully registered in the DAC, enabled events, linked to GC platform, created OAuth 2.0 credentials, created a project, linked and authorised my account, configured the pub/sub pull subscription, got access/refresh tokens, listed devices thru curl, and made sure both google.com and my nabu casa URL are listed in the OAuth authorised redirects.
I can see messages (events) from my devices in the google cloud console fine.
Where I’m falling down is the HA setup.
I’ve added the client ID, secret, project and subscriber IDs to my config.yaml. When I try to set up the Nest integration, it asks me to choose a Google account, lists my devices with the permissions I’d previously selected, then when I click OK it dumps me to the redirect_uri_mismatch error:
The redirect URI in the request, https:/xxxxxxxx/auth/external/callback, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/${your_client_id}?project=${your_project_number}
I have tried my nabu casa address with and without port number, and with and without the /auth/external/callback. I can’t find any approach that works. I am using the external URL to try and config.
How do I go about addressing this? Pun sorta intended
1 post - 1 participant
I have successfully configured the “Google Calendar Event” integration. When I look at the calendar through the front-end, each of my calendars has a color associated with it. I would like to be able to change/define which color each calendar is.
Is there any way to do this?
1 post - 1 participant
I added a Zigbee/Zwave switch and was able to add a Lutron remote. I can create an automation through the UI, however I’d like to see how I can automate using yaml. Where can I see all the various triggers that I see in automation UI? (such as “turn on button pressed”)
1 post - 1 participant
Tried to update from 0.118.2 to 0.118.3 today and I get this:
20-11-24 19:00:08 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 0.118.3
20-11-24 19:00:08 INFO (SyncWorker_4) [supervisor.docker.interface] Updating image homeassistant/raspberrypi4-homeassistant:0.118.2 to homeassistant/raspberrypi4-homeassistant:0.118.3
20-11-24 19:00:08 INFO (SyncWorker_4) [supervisor.docker.interface] Downloading docker image homeassistant/raspberrypi4-homeassistant with tag 0.118.3.
20-11-24 19:01:35 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/raspberrypi4-homeassistant:0.118.3 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi4-homeassistant:0.118.3: No such image: homeassistant/raspberrypi4-homeassistant:0.118.3").
20-11-24 19:01:35 INFO (SyncWorker_4) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 98.8 GiB
20-11-24 19:01:35 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Space is definitely not an issue and have tried rebooting a few times but no luck.
Looks as though it can’t find the image?
Any ideas?
1 post - 1 participant
Hey all,
I have a set of automated gates they work great and I’ve also managed to get a sonoff with relay to toggle them and it’s been working fine for a year. I’ve now got openalpr recognising number plates thus triggering the gates.
My problem is that my gates are dumb in the fact they are toggle based in that if they are closed and you press it it opens and vice versa. It doesn’t really know whether the gates are open or closed to start with as it uses a power surge to cut off its motors when they reach their mechanical limit.
Can anyone think of a novel and non complicated way of working out whether my gates are open or shut?
Thanks in advance!
1 post - 1 participant
I have an Insteon controlLinc (2430) that successfully controls 2 dimmer plugins (2456D3) via 2 buttons. I run HA with an insteon PLM. I can manually turn on/off the lights via the HA GUI, so I know HA can communicate through the PLM to the dimmers, but if I use the controlLinc buttons to turn on/off, HA doesn’t see the state change. The state of those switches don’t change in the GUI. Other insteon devices change just fine when I press their controlling insteon devices. So I know that HA can monitor other insteon devices and update the GUI.
I used pyinsteon to monitor insteon messages when I press the on button on the controlLinc and I see this message:
2020-11-24 13:50:52,453 INFO samples Topic: 156885.1.on.all_link_broadcast data: {‘cmd1’: 17, ‘cmd2’: 0, ‘target’: 000001, ‘user_data’: None, ‘hops_left’: 1}
So I know there is some message that can be visible to HA via pyinsteon.
I tried adding an automation to trigger on the insteon.button_on event to turn on the dimmer, and that didn’t trigger either.
Any ideas of what to check or change?
1 post - 1 participant
Recently there was a change in HA that caused my previous method of accounting for presence to break… I have no clue which version did it as I obviously missed mention of it in the version notes.
Previously I had a configuration like this:
A group called group.presence_all containing 2 person entities and an input_boolean for “guest_mode”. This group worked perfectly in my automations which needed to tell if anyone was “home” or everyone was “not_home”.
Now for some reason, looking at the group.presence_all states shows “on” and “off” instead of “home” and “not_home”… I only started digging into this because all my presence based automations stopped working with a recent update… so there was obviously a change to the way groups work when used in this way.
I tried changing my guest input_boolean to a template binary_sensor of type presence that triggers off of the original input_boolean. In the UI this shows as “Home” and “Away” but the states still read as “on” or “off”… so this didn’t fix my group issue…
My question then is this: is there a way to return to the previous functionality without having to convert all my automations to read “on” and “off” instead of “home” and “not_home” as they have always done? More concretely, is there a way to have a presence group that will show “home” and “not_home” as the states? It definitely used to work this way behind the scenes… so why was it changed?
1 post - 1 participant
Given this sensor configuration:
platform: bayesian
name: 'is_sleeping'
prior: 0.33
probability_threshold: 0.95
observations:
- entity_id: 'device_tracker.phone'
platform: 'state'
to_state: 'home'
prob_given_true: .3
prob_given_false: .01
If the current state of device_tracker.phone is home, why does the value of prob_given_false change the calculated probability rather than get ignored?
If I understand what this is saying, it’s that
In other words, for predicting whether I am sleeping, given that I am at home, what does it matter whether I would be sleeping if I weren’t at home? As prob_given_false goes to 0, the bayesian goes to 1, and vice versa.
More to the point: what is prob_given_false exactly? The docs say it is
The probability of the observation occurring, given the event is false
My understanding is that:
device_tracker.phone is in the home stateIf my phone is not at home, the probability that I am sleeping is basically 0. That doesn’t mean that when I am home, I am 100% guaranteed to be asleep… but I believe that’s the behavior I am seeing, so I must be misunderstanding something about this.
1 post - 1 participant
getting error:
Message malformed: expected dict for dictionary value @ data[‘sequence’][1][‘data’]
with this script:
alias: rack adjust ac setpoint
sequence:
- condition: or
conditions:
- condition: state
entity_id: input_boolean.rack_mode_acrecirculate
state: 'on'
- condition: state
entity_id: input_boolean.rack_mode_acvent
state: 'on'
- service: input_number.set_value
data: >-
entity_id: input_number.rack_sensibo_setpoint
value:
{% if is_state('input_boolean.rack_temp_above_setpoint', 'on') %}
{{(states('sensor.wirelesstag_rack_upper_tag_temperature') | float - 2 )}}
{% else %}
{{(states('sensor.wirelesstag_rack_upper_tag_temperature') | float + 2 )}}
{% endif %}
mode: single
1 post - 1 participant