Smart devices keep going offline

[#1]

Thank you, I've found it now and can view it as desktop site.

[#2]

Thanks everyone for your replies so just so I know what I need to do this week.
I'll reconnect the radiators and again just using 2.4ghz band and switch off 5ghz.
It's highly likely they'll lose connection again so I'll export the log from the router and upload it here?.
I can try changing the lease seeing as well to see if that helps and regarding the IP address as I'm not that technical enough to mess about with it too much but it's defaulted to use the IP address it's given already.
Not sure what else I can do as all my other devices as in TV, internet radio, phone etc have no issues with connection just the radiators.
I've also emailed the manufacturer to see if they have any ideas.

[#3]

@Townman @Dan_the_Van 

Evening both, I've just reconnected my radiators again so I'll be able to send the router log of they disconnect again.  I've just tried extending the lease to 21 days but it changed it for all devices. I changed it back but noticed it's now saying it's assigned a static IP address? Never seen that it always said DHCP..  is that because I temporarily changed lease time?.

I'm not technical enough to understand it. Am I better changing it back to 21 days and see how it goes?. I've got the manufacturer also looking at this issue.

I've attached a picture if it works and definitely says static for all my connected devices.

[#4]

@Dan_the_Van 

I've attached the event log from my router, they had all stayed connected for a few days but one of them have just dropped offline

 I've cut and pasted the disconnection log note as well, it's bizarre as the radiator was on at the time and not offline. 

18:19:19, 08 Nov.2.4G client Mac: 38:2C:E5:83:F0:6F Deauthentications (Reason:Disassociated due to inactivity )

18:18:49, 08 Nov.DHCP device Disconnected: 192.168.1.145, 38:2c:e5:83:f0:6f, unknown

Any help would be appreciated, I'd set the lease time to 21 days but clearly hasn't helped and it is set to yes to keep using the same IP address.

[#5]

In relation to the length of the lease how long did the radiator remain connected?  50%?

[#6]

Looking at the event log and the devices MAC address I see

18:19:18, 08 Nov. 2.4G client Mac: 38:2C:E5:83:F0:6F Deauthentications (Reason:Disassociated due to inactivity )
18:18:48, 08 Nov. DHCP device Disconnected: 192.168.1.145, 38:2c:e5:83:f0:6f, unknown
18:18:48, 08 Nov. LAN [DEL] ARP 192.168.1.145 with 38:2c:e5:83:f0:6f from br0
18:18:44, 08 Nov. ARP [del] br0 192.168.1.145 38:2c:e5:83:f0:6f
05:35:20, 05 Nov. DHCP lease issued 192.168.1.145 to 38:2c:e5:83:f0:6f , lease duration is 1814400 seconds
05:35:20, 05 Nov. 2.4G Client associate from 38:2c:e5:83:f0:6f (IP=192.168.1.145) RSSI=-48, Rate=72Mbps, host

17:35:38, 04 Nov. ARP [add] br0(wl1) 192.168.1.145 38:2c:e5:83:f0:6f
17:35:30, 04 Nov. DHCP device Connected: 192.168.1.145, 38:2c:e5:83:f0:6f, unknown
17:35:30, 04 Nov. DHCP lease issued 192.168.1.145 to 38:2c:e5:83:f0:6f , lease duration is 86400 seconds
17:35:30, 04 Nov. 2.4G Client associate from 38:2c:e5:83:f0:6f (IP=192.168.1.145) RSSI=-45, Rate=65Mbps, host 
17:35:30, 04 Nov. LAN [ADD] ARP 192.168.1.145 with 38:2c:e5:83:f0:6f from br0(wl1)

lease duration 86400 = 1 day

lease duration 1814400 = 21 days

Looks like a 12 hour renewal 05:35 05 Nov then the next least time was 21 days.

RSSI=-45 - that is not a weak signal

[#7]

@Simon_James 

Could you try changing the Hub WiFi to use Mode 2, which should make it more compatible to some IoT devices

Leave the DHCP lease time at 21 days for now.

[#8]

I set the lease time to 21 days last Tuesday evening so not sure how quickly it came into effect.
It was only one radiator that dropped connection last night and that's the one closest to the router.
All the others upto this point have stayed connected since last Tuesday when I changed the lease time.

[#9]

Thank you, happy to change the setting to mode 2 and leave everything else as is.
Just to add I've still currently not enabled 5ghz and have 2.4ghz set to channel 11 and not using smart settings.
I'm not back there until Tuesday evening now so I'll be in touch with an update later in the week.
Really hoping this resolves it as the other three radiators have stayed online upto now.
Am I right in thinking that a fixed IP as such would have to actually be done on the device? And with this been a radiator I don't have that option so ensuring the setting always use the same IP address is set to yes that's the best I can do?.

[#10]

@Simon_James 

Good idea to not touch anything further. What was the wifi extender make/model you tried?

There has been a mixup on terminology which has been corrected.

A DHCP assigned IP address which is  'Always use this IP Address'  is actually referred to as a Fixed IP address.

When an IP address is manually configured on the device it is referred to as a Static IP Address.

Not many/if any IoT devices are able to use anything other than DHCP.

Edit: I found DHCP IP Address 'Fixing' on a Hub two a bit flaky, so for that reason and wanting WiFi 6 I bought my own router.

[#11]

This is the WiFi extender I bought - TP-Link TL-WA854RE N300Mbps.
It's a single band 2.4ghz so thought it would have been ok for my radiators, but as it happens I was having the same issues.
I don't even know if I actually needed it as I live in an apartment all on one level.
Thanks for explaining the fixed IP set up.
Could that be for issue here that it's not fixing or just trial and error with settings?
It's definitely improved stability with changing the lease time, well assume it's that.
If you think it's with trying that extender again I can, also will switching 5ghz back on cause any issues?.
I'll not do that until hopefully all this gets sorted.

[#12]

---

@Dan_the_Van wrote:

A DHCP assigned IP address which is  'Always use this IP Address'  is actually referred to as a Fixed IP address.

When an IP address is manually configured on the device it is referred to as a Static IP Address.

---

In different places these terms have been used interchangeably.  For example where Plusnet used to offer a not-a-dynamic IP address, that is ones assigned by their radius server (i.e. a Plusnet DHCP server) that has always been referred to as a STATIC IP address.  That is an address reserved by the network, not one 'hard coded' into the device as per the above description of "static".

Sometimes short hand labels for slightly longer descriptions create unhelpful ambiguity: it might be clearer to use

• DHCP reserved addresses
• Device configured address

A "DHCP reserved address" ensures that the device, when on that network, will always gets the same address.

A "Device configured addresses" ensures that the device will always have the same address regardless of what network it attaches to ... which is probably very undesirable.

If the device is never moved from one network to another, then the above difference will be of no concern.  If it does move networks then such will be a significant issue.  Even if not moved, where there are additional network components involved (such as a WAP or WiFi extenders), there is some opportunity for confusion if that network device has its own DHCP server and a different (or indeed overlapping) subnet.  I have seen devices which have DHCP pass through or run their own DHCP server leading to a double-NAT configuration.

That is a possibility I ought to have considered earlier here.

[#13]

Sometimes "keep it simple" is best. (KIS)

I'd say there should be no confusion for the way a Broadband public IP addresses assigned with devices behind the router NAT?  They should be considered different network implementations.

plusnet would have no interest in what happens with IP Addressing on a clients network all they see is the Public IP Address assigned to the router by them,  by which ever mechanism being used.

For a device you would be either set to use DHCP or a manually setup using a Static IP Address

1) configured Static IP Address on a device network interface card/adapter, means the device will only communicate to other  devices on the same network range. Considerations need to be made moving between networks

For an device on a client network managed by a DHCP server

2) Set DHCP to always use this IP Address for a given MAC Address from the DHCP address pool. 

3) Allow DHCP to allocate a IP from it's address pool.

In case 1 and 2 they can be by some be referred to as having an Fixed IP Address.

To me I do not believe a second router is involve here which would be required a for double-NAT, no evidence of a second DHCP server.

[#14]

@Dan_the_Van 

Evening, just a quick update sadly another radiator dropped offlline so I've downloaded the log again for you just to have a look at.

This is the message I think relates to it going offline.

07:07:21, 11 Nov.2.4G client Mac: 38:2C:E5:83:ED:D6 Deauthentications (Reason:Disassociated due to inactivity )

07:07:02, 11 Nov.DHCP device Disconnected: 192.168.1.101, 38:2c:e5:83:ed:d6, unknown

I've just set the router to mode 2 so I'll reconnect the one offline and see how it goes.

If this doesn't work I feel I'm kinda out of options!, unless you'd be able to come up with anything as I'd be grateful of anything

It made no difference when I had that extender connected previously and wasn't even sure it was needed as I live on one level.

Anyway I'll let you have a look at the log and see what you think, I've left lease time as 21 days and see what happens on mode 2

[#15]

@Simon_James 

Thanks for the update, it's a different device from the last time, I can see many different devices are seeing "Reason:Disassociated due to inactivity"

The Hub thinks a device has gone off-line so it is removed from the active devices list.

When you used the wireless extender, did you mirror the wireless name or use something else? Problem with extenders is they repeat the signal on the same channel they are mirroring, so they could add to the issue where wireless congestion exists.

From my reading Mode 2 should help with IoT devices, some more research may be required.

Thread getting a but long has a wifi analyser been suggested to see if 2.4GHz channel being used is not congested. You need to check next to a device location.

EDIT: do you have another modem/router we could try?