EE routers and DHCP

[huggons]

Wondering if anyone can assist please.

Since getting Heatmiser smart heating controls a few years ago, which consist of a Heatmiser NeoHub, that connects directly to my EE router with a ethernet cable and a wireless Heatmiser thermostat, I have been facing lots of issues with the smart heating controls.

Heatmiser suspect that the issue is with the EE router and DHCP release times.

This has been the same issue over the years and I have had the exact same issue when connecting the Heatmiser NeoHub with an ethernet cable to the white EE smart hub 2 router and the EE smart hub plus router and the EE smart hub pro router, over the years.

Can anyone comment on the DHCP release time for the routers and have any thoughts if this could indeed be the underlying issue, as Heatmiser support suspect?

Any help would be much appreciated.

Cheers 

Steve

[huggons]

I have set the EE smart hub pro router, to always use this IP address, in admin/my network/address table, for the Heatmiser NeoHub device. I will let Heatmiser know and see how it goes.

[huggons]

No sure why devices show like the is the router admin...

 

[chistery]

If the MAC is not changing, and the device is up and connected, the DHCP lease shouldn't expire.

[huggons]

Thanks.

Will see how it goes now after setting to "always use this ip address"

[JimM11]

@huggons Quick look at the Neo Hub, this is by far the biggest RED issue that i see for sure and from there blurb.

" Local Control (In case of loss of Broadband Connection)
Should the internet connection fail, the heating system
can still be operated within the home by using the
thermostat keypad. As soon as the internet connection is
restored, your neoHub will automatically logon to the
Cloud Server re-enabling app control

Anything you see on the EE Web interface, just take it with a pinch of salt, info is about as much use as a chocolate fireguard.

[Huggons1]

Thanks.

Going to speak with Heatmiser again this afternoon. Will be interesting to hear their thoughts and to see if changing the router settings to "always use this ip address" is the solution. 

[JimM11]

@huggons Certainly worth a try, have all my devices set as static ip's on the EE Router, apart from the ones that drift in and out, visitor's son, his wife, grand daughter and all her many friends that visit that's just far too hard to keep up with when they are all apple, hide change the mac's and up to all the dodge's etc, 

[Huggons1]

Observation update.

Early hours of the morning, I lost the Heatmiser heating system controls. The Heatmiser NeoHub is on a fixed IP address in the EE smart hub pro. I looked in admin of the EE smart hub pro and it wasn't seeing the Heatmiser NeoHub was connected to the ethernet port. After powering off and on the router and the NeoHub, the router now see's the NeoHub is connected.

Any ideas as to why this is happening?

[JimM11]

@Huggons1 Not a EE Pro user, but you have been fighting this Ethernet connected module for a while now, if it was me i would look to put a lower specked Ethernet switch before the EE Nic port, as they are all 2.5Gb/s ports it may just help steady the comm's between the two units, up to you now, have found that the Tp-Link TL-SG105S seems to help a lot, if you wish to power it from the USB port, i use the Lindy 70266 USB A Male to DC-Plug Adapter 3.5mm/1.35mm cable connector, there is a power supply with the unit, Ethernet cable required if you don't have a spare lying around just to patch through.  

[Huggons1]

Thanks for the suggestion, really helpful and I appreciate it

I have spoken to both Heatmiser and EE today. Heatmiser say that the NeoHub is designed to save data by, I guess going offline every so often. They suspect that the EE smart hub pro is then blocking the NeoHub when it requests the connection. It did seem odd that the smart hub pro didn't see the device connected, until I rebooted it.

The gentleman I am dealing with at EE was very helpful and will check and confirm if it is possible that the smart hub could even do this, to a device directly connected through an ethernet port.