Speaker Hub not integrated yet, 6 months ago said it would be but to date its not, just bought one, I’m about to return it because I need it for HA…
Ah that explains a lot, so the speaker hub is not integrated and thats why my sensors aren’t showing correctly. I’ll need to return it.
@Eric-YoLink or anyone else who can comment, is there a plan to integrate the Smart Power Fail Alarm into the Home Assistant integration. I only use the water sensor (integration is great!) and the Power Fail Alarm and it would be great if the latter was supported in HA.
Issue with leak sensor - always reading dry.
I have several leak sensors set up in reverse (water exhaustion sensing) in tanks. The actual sensor itself works great - and I am getting YoLink notifications via push and email - but the readings are NOT being communicated via YoLink’s HA integration. Has anyone else run into this?
My regular leak sensors (not reversed) seem to work fine.
@Eric-YoLink any insight you may have here would be helpful.
Thanks in advance!
About once every year, I have noticed bizarre items like this. What resollved the issue for me was to just pull the power cord out of the Yolink Hub and plug it back in. Give it a couple of minutes to reconnect - then give it another try.
Unfortunately this does not resolve the issue.
I tested my regular leak sensors, and they again worked fine.
Is anyone having problems with Home Assistant getting state updates when the YoLink Smart Lock M1 is locked/unlocked using the YoLink App to lock or unlock? Locking/unlocking from the lock itself seems to be working fine, I get the state updates in HA (and the YoLink app). Locking and unlocking from HA seems to be working fine (I get the state changes in both the YoLink app and HA). It’s only when I use the YoLink app to lock or unlock when HA becomes out of sync with the lock state. If I reload the YoLink integration HA shows the proper state once again (until the YoLink app is used).
I’ve been having problems with YoLink for at least a couple of weeks. Events from my YoLink motion sensors, which are a critical part of my home automation due to horrible light-switch placement, are not making it into HomeAssistant.
The sensors appear to be working properly when I check the YoLink app, and the events are making it to Alexa, but I’m seeing perhaps 1 in 20 in HA.
What is the best way to troubleshoot? Is this likely to be a problem with the YoLink integration, or the API it calls? Perhaps the API is throttling calls that are not coming from certain apps?
Would love to know folks’ thoughts so I don’t have to use Alexa for the motion sensing responses and don’t have to replace the sensors.
I have joined the YoLink Community and have the same problem. I have two critical Yolink outdoor sensors which are working with Alexa and the Yolink speaker hub. Both are giving me audible feedback that motion was detected a second after motion occurred. In HA, the event logs for the sensors are static and therefore my automations are not being triggered by the YL outdoor sensors. The automation does run when I trigger it manually, so I know the automation is configured correctly. Only when I click on the Reload Integration for YoLink are the logs being updated and the automation runs as I configured. I think I have the same situation where the Yolink events are not making it to HA unless I manually force a refresh of the Yolink Integration. I also noticed when I reload the Yolink Integration the timestamp of the event is the time I reloaded the integration and NOT the timestamp of the actual motion detected by the sensor. Any ideas on how to fix this? Thank you.
The version of HA I am running is below:
Home Assistant 2023.2.3
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest
What is it I dont understand about LoRa and Youlink local control. Everywhere I read it say that a server is a must. Selfhosted or cloud. There is many providers of LoRaWanout there ut all are the same, cloudbased. So is local control possible at all?
I startred running into wonky weird problems similar to yours - and just yanking the power cord out of my yolink hub and plugging it back in fixed the issue. This only needed to be done after the relay had been up and running for a long time. Possibly a very tiny memory leak (bug) in the code that cause a problem once or twice a year? Give this a try, see what happens
Been on a bit of a hiatus with this… I’ve been moving, job has been busy, etc. In the process of moving I was able to get my hands on two more of the basic Yolink Hubs and able to get into one of them. Long story short, that is a dead end unless you want to reflow a new ESP32 onto the board. They have encrypted the bootloader and the flash storage with a one-time key and that key is required to remove the encryption. Any further attempts to update the flash must be performed over OTA – while I can get it to connect to WiFi (it looks for a YoSmart SSID), I can’t do anything beyond that. It runs a web server but I don’t know any of the URLs so it just says ‘404’.
Ultimately if someone wanted to replace the ESP32 on the board, you could probably make this work but that is quite a bit of work. The board does have a perfectly usable Semtech LLCC68 LoRa radio on it to use (tied through i2c) and an ethernet interface using the IP101. Both of these are well supported within the ESPHome arena so you could potentially flash that. Right now, I just don’t have the available time to go further with this. Shoot, I don’t even have Home Assistant running (and haven’t since August of last year when I moved) because I just haven’t had the time to devote to setting it all up in my “new” house.
Best of luck to everyone… remember… Zigbee still exists (even though I’ve never had good luck with it) and Matter is coming around soon – get your Sky Connect early!
I’ve power cycled my yolink hub a few times, because it’s connected to the same UPS as half of my network gear, but it hasn’t helped.
I just moved HA from an RPi to a VM on my proxmox server, and moved all of my IoT devices to a new vlan with new IPs. I’m super curious to see if that has any impact on the yolink motion sensors. Should know more in a few minutes.
If that doesn’t change anything, I’ll pull the plug on the hub (temporarily ), then share the results.
Side note - I was initially very enthusiastic about the YoLink motion sensors, but my current issue with not being able to use them with HA, and the fact that a firmware update a couple of months ago disabled the built-in temp and humidity sensors is making me consider replacing them.
The YoLink integration (when they first rolled it out) very early on was not reliable as it relied upon their servers in the cloud and the way they set up their servers for this, they were not 100% reliable. (For a little while I was using the Yolink Integration AND IFTTT (which was not affected by their server issues it seems) to report motion from their motion sensors into HA so I would always get two notifications about motion from two sources, but that is no longer needed. The IFTTT notification from a Yolink motion sensor is very slow, but whiule there was an issue it was better toi get one late report then none at all!) That has changed dramatically and they are VERY reliable.
My Yolink sensors are all up to date with the latest firmware and they do report the temp but I don’t use it because it is not very accurate. The temp and battery levels were at one point classified as “diagnostic” sensors (which are treated differently and not always visible in all cases, not meant for public consumption). The logic behind that was that they are not normally meant for use as they are not really very accurate. Then recently - it seems like the diagnostic sensors were now always available in a more recent release but I may be wrong… Anyway you can expose any and all diagnostic sensors for any device - to be exposed everywhere within home assistant by showing it as a fully available template sensor in the configuration.yaml file. Below are some examples of some of the ones I have set up (the last one being temperature):
(Note that YoLink battery levels are not very exact and as such they are diagnostic sensors, they only report the % battery level rounded to the nearest 25%. Under the covers using the API (which I don’t do, I use the integration) if I remember correctly their developer told me it reports as 1,2,3 or 4.)
So, code with this type of format in your configuration.yaml (you will have to restart HA for the changes tro be visible):
sensor:
# Exposes diagnostic sensors to all of HA
- platform: template
sensors:
# Yolink leak sensor - battery level
battery_status_basement_furnace_leak:
friendly_name: Basement Furnace Leak Sensor Battery
value_template: >-
{{ states('sensor.furnace_battery') }}
icon_template: >-
{% set batterylevelicon = states('sensor.furnace_battery') | int(0) // 10 * 10 %}
{% if batterylevelicon == 100 %}
mdi:battery
{% else %}
mdi:battery-{{batterylevelicon}}
{% endif %}
unique_id: battery_status_basement_furnace_leak
unit_of_measurement: "%"
# Ring Doorbell battery level
battery_status_ring_doorbell:
friendly_name: Ring Doorbell Battery
value_template: >-
{{ states('sensor.ring_doorbell_battery') }}
icon_template: >-
{% set batterylevelicon = states('sensor.ring_doorbell_battery') | int(0) // 10 * 10 %}
{% if batterylevelicon == 100 %}
mdi:battery
{% else %}
mdi:battery-{{batterylevelicon}}
{% endif %}
unique_id: battery_status_ring_doorbell
unit_of_measurement: "%"
# Backup battery (as there is a solar panel) level for Ambientweather WS-2902C weather station.
# Their goofy diagnostic sensor only shows "off" if "Ok" and "on" if it needs to be changed
battery_status_weather_station:
friendly_name: Weather Station Battery
value_template: >-
{% if is_state('binary_sensor.ridgewood_estate_personal_weather_station_battery','off') %}
Ok
{% else %}
Change Battery!
{% endif %}
icon_template: >-
{% if is_state('binary_sensor.ridgewood_estate_personal_weather_station_battery','off') %}
mdi:battery
{% else %}
mdi:battery-90
{% endif %}
unique_id: battery_status_weather_station
# Temperature for Shelly +1 Relay in a receptacle behind wall switch:
relay_temp_back_door_light:
friendly_name: Back Door Light Relay Temp
value_template: >-
{{ states('sensor.back_door_shelly_1_relay_device_temperature') }}
icon_template: mdi:thermometer
unique_id: relay_temp_back_door_light
unit_of_measurement: "°F"
Hope that helps, let me know!
The network changes I made had no impact (not a surprise).
But I realized I had moved the yolink hub from its dedicated usb power adapter, to a usb power hub, around the same time my problem started (within weeks, not hours). The yolink was plugged into one of the lower-power ports so I moved it to a higher-power port, and shortly thereafter I got one motion event in home assistant, though I could see several in the yolink app.
Then I moved yolink to a dedicated usb power adapter, but no more events in home assistant.
I’m at a bit of a loss, but perhaps my experience can aid in the overall troubleshooting.
I’ve been using the power adapter that was provided with the unit, if you can dig that one up and switch back to it that may resolve your issues - especially since your issues started when you switched away from it
Can anyone help? this is driving me crazy. I can’t add Yolink integration. After authorizing on redirect url it does nothing, I tried external, internal instance urls.
Not sure of how to resolve your issue but I remotely acces my instance with tight security this way without having any separate company have access to my HA instance and it costs $0. In addition to that for maximum security I also am connecting to it via VPN on top of that. (However I do strongly believe in supporting and encouraging the success of Nabu Casa and feel everyone should subscribe for the service even if they do not rely upon it similar to my situation.) Just thought it was something you might like to consider.
I’ve got two water leak sensors that don’t seem to be reporting their status to HA but they do report in YoLink app. I’ve removed and re-added both the devices themselves in YoLink and the integration in HA to no avail. Any known issues here? Everything is up to date.
@Eric-YoLink Any updates on the SpeakerHub working from within HA ? I just picked one up after seeing the Yolink integration but was a bit sad to see no support for the SpeakerHub