Homey unresponsive after 12 hours.in v2

Questions & Help
#49

I felt as well like it has to be something w/ am interference and a pretty poor eeehm sensitive wifi chipset on Homey.

Tried all the stuff mentioned here, stronger adapter, different cable, checked firewall and router, disabled 5GhZ but for sure I’m not going to change my router as it’s simple:

The issues started w/ v2.0 and therefore it usually cannot be simply related to the hardware.

Can imagine the channel may cause issues - however, still waiting for the 2nd answer of Athom support… let’s see …

#50

I borrowed both wifi and zigbee sniffers, was the last shot to try :blush:

#51

Okay, my mistake, use a arduino nano selfmade amp meter. Made a mistake in the Code.
After correcting the code, messurements are for the Homey-pro max 1.14 (spike) so asume that 2 amps would be suitable.

thanks

#52

Anyone got some answer from Athom about the memory problem? I´ve just got one answer from bram that it was forwarded to devs some weeks ago… But when i asked after a while if they needed any more from info me an how it was going with the case there was no response at all.

#53

Did send a email about status of the call towards athom, but no response mail today.
Can’t tell you the status.

#54

Today i received a email reply from homey.

They told me that they going to fix the problem for the memory leak.

They have not give me anymore details what the problem is and when the fix will be released.

Looks like a problem in the homeycore not in any apps

2 Likes
Red ring (of death?)
#55

Its same in 2.0.5-rc2, unresponsive after 12 hour.

#56

I recieved an email about the memory leak from support today. They hope to be able to fix it soon.

#57

I have this problem as well. What is soon ??

#58

definition of soon
But in this case, 2.0.5 currently in experimental is already better :slight_smile:

#59

Good question, i wish i knew.

Athom takes the stand things come when they come. When they go and mention a time they come with things, they put pressure on themself. Like coming with Homey 2.0, they stick with ‘soon’.

#60

For now i looks oké in version 2.05
No response from athom yet if its realy ifixed

#61

For me it’s not OK. Yesterday evening I had to reboot Homey again after updating to version 2.0.5. So no difference. After a few MQTT broker calls (I think) I saw Homey using more memory!

#62

no diffrence in Homey v2.0.5 experimental needs restart every 12th hour.

#63

I am also experiencing some issues around the MQTT broker. Homey needs restart occasionally and after 2.05 I have found the broker “paused” i n Homey as well.

#64

I wonder how long time Athom needs to fix the “leek” It starts to get really annoying.

Nieuw Homey ... loopt vast
#65

Maybe it’s a mqtt broker issue and not a homey core issue?

#66

Finding a memory leak is like finding a tiny needle in a massively huge hay stack, incredibly difficult to find the main cause, so how long it takes really depends if they can find the leak, or maybe even multiple leaks.

1 Like
#67

If I restart the wireless weather sensor app every night the memory is below 120mb all the time and I don’t lose connection to homey and do not need to restart homey every night

#68

Did you deselect all discover-able brands from devices you don’t have from the list?
It’s recommended by the creator…

I am also running the app and i don’t have any problem with it. In my list only “cresta” is selected.