I find mine throu either asuswrt or nmap?
It shows up in my known_devices.yaml
Try to add it in your known_devices.yaml with the ikea bridges mac adress
just copied the code and swapped out the switch part, seems to be working =)
Do we have a tradfri user who has a working gateway at all? In other words, is it worth to swap it for a new gateway at Ikea?
I bought mine in May or early June and I only had to restart it 2 or 3 times since then. No problems since the firmware update as far as I can remember.
I also need to restart mine every day, running 1.1.0015.
I can however still ping mine when it is dead so the above ping solution for power cycling it won’t work. Might have to power cycle it on a scheduled basis instead.
Mine seem to be “pingable” too when down, mine have gotten much more stable lately so i havent have had to restart it much.
My GW hangs too. The Gateways seems to be a quite bad product. I’ve documented my experience with Tradfri here: http://myconnectedthings.blogspot.se/2017/10/ikea-had-20-off-for-tradfri-products.html
BR
Could it be a problem with the DHCP client in the bridge? When I unplug my router when the ikea bridge is online the middle LED on the bridge will start pulsating. When I plugin the router again the bridge won’t go online. The LED keeps pulsating.
Devices like smartphones iPads, laptops reconnect properly to the router after it’s plugged in again. I had the same problem with a Popcorn Hour Media Player. The dhcp client did not obtain a new lease after the router came online again. Maybe the TRÅDFRI bridge has the same issue.
Does anybody know if I can define a static IP for the bridge? Not a static dhcp but a real static IP address.
I’m also suspecting the DHCP client of the Tradfri gateway to be the problem. The weekly reboot of my router causes the Tradri gateway to disconnect from the network.
am having an issue where the gateway crashes every night without fail, it has only started doing this since the latest firmware has been installed. When it goes off i cannot ping the gateway at all and all lights on the gateway are solid on.
I plan to setup a ping to check exactly what time it stops responding to see if i can find any sort of pattern or reason why.
Then it will be a factory reset, if it continues after that back to ikea it goes for replacement.
In my case, I lose control from the hass frontend over lamps connected through the Ikea gateway. The gateway works fine (several weeks without a hitch) but hass shows the lights as on although they’re not, and toggling to off does nothing, Hass just puts them back to on. The thing is that I can still control the Ikea lights through the emulated hue component in Hass (harmony remote) so that tells me that he hasn’t totally lost control of the lights… all works great if I reboot Hass, but then after a while, the problem reappears.
How does one debug this?
2 Likes
get the same issue here. Infrequent I hasten to add.
Meanwile my MiLight bulbs are working a treat 
What TRÅDFRI firmware and hass version are you guys running?
I have the same problem. The light status does not update when the light turns on. I’m able to turn off the light using custom automation (which turns off all the lights). So I’m figured the gateway accepts the commands but HA cannot read the current status from the Tradfri gateway.
Restart of HA fixes the problem temporary. I’m not sure after how many hours or days the problems start. Seams to work no for the last 2 or 3 days (HA version 0.70.1).
Going to search for the current Tradfri firmware version, will update this post.
HA version: 0.65.5
Tradfri version:
Gateway 1.3.14
Lights 1.2.217
Remote 1.2.214
Same problem here. Switches in HASS return to on no matter which state the bulbs are in.
The only way the state changes is trough Developer tools -> States. And even here I experience a peculiar issue.
I turned off a light and that worked trough States, but then I tried switching the group off and it did switch it off but broke the page of the Web UI where the switches were shown. The error I get when opening the mentioned page is “Service system_log/write called”.
I’m at work right now so I don’t have access to logs. I can paste them here later in the evening, so maybe someone will have an idea of what is the issue with these lights/gateway integration.
Regards, Jure
There was nothing in logs and a simple restart corrected the error. Waiting for it to happen again to troubleshoot further.
I’m also having this intermittent (seems daily) Tradfri GW service problem and its getting annoying. I notice the GW is still pingable from my mobile today, though the app reports as not connected. So networking on the GW seems to be working (at least at the ICMP level) but not the services that rely on it.
A temporary reboot workaround for me, will be to connect it to a smart plug and have some rule that reboots it. But this is inconvenient to set up, uses expensive hardware (unless I get a Sonoff in there) and is not how an infrastructure device should be operated. IKEA should be fixing this pronto as it seems to be affecting a lot of customers.
Does IKEA have a bug tracker? Googled, but nothing shows.
You’re not alone, though that’s probably not much consolation.
I have my Trådfri Gateway set up on an electromechanical timer. It turns off every day at 7:00 and back on at 7:01.
I regularly check for and install firmware updates but nothing they’ve done so far seems to have resolved it.
Let me know if you figure anything out!
I’m into same problem. Firmware 1.4.15. Considering buying a switch to reboot gateway.
It’s 2021 now… Did anyone find a solution yet? I’m running 1.15.55 and my gateway crashes just about once every 24 hours of so. No ping replies at all yet just before it starts to stop replying I noticed:
PING ikeahomesmart (10.0.0.48) 56(84) bytes of data.
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=1 ttl=128 time=0.571 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=2 ttl=128 time=0.366 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=3 ttl=128 time=0.358 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=4 ttl=128 time=0.341 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=5 ttl=128 time=0.340 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=6 ttl=128 time=0.343 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=7 ttl=128 time=0.364 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=8 ttl=128 time=0.366 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=9 ttl=128 time=0.332 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=10 ttl=128 time=673 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=11 ttl=128 time=11671 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=13 ttl=128 time=10553 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=14 ttl=128 time=9513 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=17 ttl=128 time=7393 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=19 ttl=128 time=5313 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=22 ttl=128 time=2193 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=23 ttl=128 time=2192 ms
64 bytes from ikeahomesmart (10.0.0.48): icmp_seq=24 ttl=128 time=1191 ms
— ikeahomesmart ping statistics —
25 packets transmitted, 18 received, 28% packet loss, time 808ms
rtt min/avg/max/mdev = 0.332/2816.356/11671.424/4011.548 ms, pipe 12