WiFi thermostat is not working or cannot connect to the internet – common causes and solutions

We are still preparing products.

But you can look at other categories.

WiFi thermostat is not working or cannot connect to the internet – common causes and solutions

A WiFi thermostat is now almost a given for many homeowners – controlling heating from a mobile device, automatic schedules, integration with smart home systems. Yet precisely this dependence on wireless connectivity brings a specific category of problems that you simply won't encounter with a traditional thermostat. A customer calls in upset that their thermostat "has stopped working," even though they set it up yesterday. In most cases, however, the problem is not the thermostat itself – it's the router, the network, the app settings, or the installation environment.

In this article, we will systematically go through all the common reasons why a WiFi thermostat is not working, is losing connection, or is not connecting at all. We will examine it from the perspective of the network, hardware, software, and physical installation. If you've just bought a new device and can't pair it, or your old thermostat suddenly disappears from the app – this guide will help you locate and resolve the issue without unnecessary calls to the service center.

Why are problems with WiFi thermostats so common – basic context

Unlike a traditional programmable thermostat, which operates completely independently, a WiFi thermostat depends on several layers of technology at once: the home WiFi network, the router, the manufacturer's cloud server, the mobile app, and the correct firmware of the device. If any of these layers fail or change, the thermostat will stop working – despite the fact that the device itself is physically fine and the heating could technically still run.

From experience, I know that about 70% of reported issues with WiFi thermostats are not actual faults in the true sense of the word. They are configuration or network problems that can be resolved without any hardware replacement. The remaining 30% are genuine faults – a faulty module, a damaged antenna, power failure. But let's proceed systematically.

Network issues – the most common cause of disconnection

2.4 GHz vs. 5 GHz band – a crucial detail people overlook

This is by far the most common mistake during the first pairing. Most WiFi thermostats – including Emos P5623 – support only the 2.4 GHz band. Modern routers, however, typically broadcast on both bands (2.4 GHz and 5 GHz) and sometimes combine them under a single network name (so-called band steering). The thermostat then tries to connect, but the router offers it a 5 GHz connection, which the device simply cannot handle – and the pairing fails.

Solution: In the router settings, temporarily separate the 2.4 GHz network under a unique name (e.g., "MyWiFi_2G") and pair the thermostat exclusively to this network. Later, you can re-enable band steering, but keep the thermostat permanently logged in to the 2.4 GHz SSID.

Weak signal and dead zones

The WiFi signal in older buildings (thick walls, reinforced concrete ceilings, metal partitions) can be surprisingly weak at the thermostat's installation location – even if your phone shows "full signal." The phone is right next to the router, but the thermostat is hanging in the entrance hall behind three doors. The thermostat may connect during the first pairing, but later, when the router is slightly loaded by other devices, it simply loses connection.

The recommended RSSI (signal strength) value for reliable operation of a WiFi thermostat is at least –70 dBm, ideally –60 dBm or better. Values worse than –75 dBm (a negative number with a higher absolute value) cause unstable connections and frequent dropouts. Most thermostats display the signal status directly in the app or on the display – check it.

Solution: Use a WiFi repeater or mesh system to extend the signal. Make sure the repeater is in the same VLAN segment as the main router, otherwise the thermostat won't reach the cloud. When installing a new thermostat, always first measure the signal at that location using a mobile device (there are apps like WiFi Analyzer for Android).

Changed password or network name

Have you changed your WiFi password? Or did you replace the router and forgot to set the same SSID and password? The thermostat remembers the credentials from the first pairing and, when the network changes, it remains "offline" – without any warning, without any message. You simply won't find it in the app.

Solution: The thermostat needs to be reset and paired again. The reset procedure varies by model – usually it's a long press of a combination of buttons (see the manual). After resetting, it will appear as a new device in the app and you can pair it with the new network credentials. If you plan to replace the router, note down the current SSID and password in advance and set them up the same way on the new device – the thermostat won't notice the change.

Firewall, MAC filtering, and client isolation

This is an advanced issue, but it occurs in practice especially in households where the router was configured by a "technically skilled" family member. If you have the following enabled in your router:

MAC filtering – the router allows only devices with an approved MAC address. A new thermostat has a different MAC – and simply won't connect.
Client isolation (AP isolation) – devices on the same WiFi cannot communicate with each other. This blocks the initial pairing via Bluetooth or local network.
Strict firewall or DNS filtering – blocks the manufacturer's cloud servers, so the device is locally available, but you cannot access it from an external network.

Solution: Temporarily disable these features, perform the pairing, and then re-enable them – if you want, add the thermostat's MAC address to the whitelist. Unblock the manufacturer's cloud servers in the DNS/firewall rules (addresses can be found in the documentation or the manufacturer's technical support).

Problems with the cloud server and application

Cloud server outage by the manufacturer

The majority of WiFi thermostats communicate through the manufacturer's proprietary cloud server. If this server goes down – whether due to maintenance, a DDoS attack, or a technical failure – the thermostat will appear offline despite being physically powered on, connected to WiFi, and functioning properly. It may even regulate heating locally according to the last set schedule, but the app will not see it.

How to recognize it: The thermostat displays "connected" on the local network (the correct WiFi icon is blinking on the display), but in the app you see "device is offline" or "unable to connect". Check the manufacturer's status page or forums – outages appear there quickly.

Solution: Nothing else but to wait. Most manufacturers have backups and resolve outages within a few hours. The thermostat continues to function according to the programmed schedule – it is not in danger, you just lose access to it via the app.

Outdated app or incompatible version

Manufacturers regularly update their cloud APIs and mobile apps. If you have an outdated app version, it may happen that the new firmware version of the thermostat communicates using a different protocol than your old app expects. Result: the app cannot find the thermostat or displays an error message.

Solution: Always keep the app up to date. On Android and iOS, check the store for any available new version. If you recently updated the thermostat firmware, don't forget to update the app as well – and vice versa. More about how to properly maintain firmware can be found in the article How to maintain and update smart thermostat firmware.

Account or login issue

Some problems with a "non-working" thermostat have a trivial cause: the session in the app has expired, you changed your account password, or you have too many devices logged in at once. The app silently logs you out and the thermostat appears offline.

Solution: Log out and log back in to the app. If you forgot your password, use the recovery function. If your thermostat is registered under an old email (e.g., you changed your email provider), there may be a re-registration issue – some devices can be transferred between accounts, others cannot (depends on the manufacturer).

Installation and power supply issues

Thermostat power supply – batteries vs. wired power

The WiFi module is an energy-intensive component. Battery-powered WiFi thermostats consume several times more power than traditional thermostats and batteries may last significantly shorter than the manufacturer states – especially in cold environments or with weak WiFi signals (weak signal = thermostat must transmit stronger = higher power consumption).

Common scenario: the customer installs the thermostat, it works perfectly for two months, then starts to fail. Culprit? Weak batteries. The thermostat still tries to connect, but it lacks the current to initialize the WiFi module – and appears offline or unresponsive.

Recommendation: For battery-powered models, always use high-quality alkaline batteries (e.g., Energizer, Duracell) or lithium batteries – they last significantly longer and better withstand temperature fluctuations. Do not buy cheap no-name batteries for a WiFi thermostat. If possible, choose a model with wired power supply – more stable performance and no worries about batteries.

Models like Elektrobock PT32 GST are designed for wired connection to the heating system, ensuring stable power supply without dependence on batteries.

Thermostat location – heat, metal surfaces, interference

A WiFi thermostat should not be installed:

Behind a metal cladding or in a metal box – metal significantly blocks the WiFi signal
Near a microwave oven, a DECT cordless phone, or other sources of interference at 2.4 GHz
On an exterior wall in a cold room – electronics typically operate reliably between 0 and 50 °C
Directly above a radiator or convector heater – overheating of the electronics

If the thermostat worked for years and suddenly started having outages – check if something physical has changed in the area: a new microwave, a neighbor's new router, or a wall partition change.

Problems during initial pairing – step by step

The app "cannot find" the thermostat during installation

This is a scenario that troubles every second beginner. They launch the app, press "Add device", and nothing happens. The thermostat is blinking, but the app does not see it. Here is a systematic approach:

Check that you are on a 2.4 GHz network – the phone must be on the same network as the thermostat during pairing.
Enable Bluetooth – many thermostats use BLE (Bluetooth Low Energy) for initial pairing, even though subsequent communication takes place via WiFi. Without BLE, the app will not find it.
Enable location services (GPS) – on Android, this is mandatory for scanning Bluetooth and WiFi devices nearby. Without GPS permission, the app will simply not see the device.
Check app permissions – in the phone settings, the app must have access to the network, Bluetooth, location, and possibly the local network enabled.
Restart the router – if the router is currently assigning many DHCP addresses or has a full ARP cache, the new device may not receive an IP address.
Put the thermostat into pairing mode – refer to the manual to activate "pairing mode". Usually, this means holding the button for 5–10 seconds until it starts blinking.

The detailed procedure for the first launch and configuration can be found in the article Setting up a smart thermostat via the app – first launch and configuration.

Thermostat disappears after a while – unstable connection

The thermostat successfully pairs, works for a few minutes or hours and then "disappears" from the app. This is a typical issue of an unstable WiFi connection. Possible causes include:

Weak signal at the installation location (see above)
Router has aggressive power-saving modes enabled, which disconnect "idle" devices after a certain period of inactivity
DHCP lease time is too short and the thermostat does not receive a new IP address in time – connectivity is lost for minutes
Interference on 2.4 GHz from neighboring networks (in an apartment building, for example, channel 6 may have 12 networks at the same time)

Tip: Set a static IP address for the thermostat in the router (DHCP reservation based on MAC address). This eliminates the issue with IP address renewal and the thermostat will always have the same address. In the router settings, also check the "DTIM interval" – a value of 1 or 2 is better for IoT devices than a higher DTIM.

Thermostat reset – when and how

Reset is the last resort before considering replacing the device. If nothing else works – changing the network, reinstalling the app, new batteries – a factory reset usually resolves most software issues. After the reset, the thermostat will behave like a new one and the entire pairing process must be repeated from the beginning.

Warning: A reset will erase all saved programs, schedules and settings. If you have a complex schedule programmed on the thermostat, take a photo of it or write it down before performing the reset. Some apps allow you to back up settings to the cloud – check this in advance.

The reset procedure depends on the model. For most thermostats, the following applies:

Hold the RESET button (or a combination of UP + DOWN) for 10–15 seconds
The display will reset and the thermostat will start blinking (indicating pairing mode)
If there is no physical RESET button, check the manual – some models can be reset via the menu

Firmware – an outdated version may be the root of the problem

Manufacturers release firmware updates for several reasons: they fix security issues, improve WiFi connection stability, and fix bugs in communication with the cloud. An old firmware version may have a bug that causes the thermostat to disconnect and reconnect every 24 hours – which looks like a hardware problem, but in reality it is a software bug fixed in the latest version.

Most thermostats update the firmware automatically via WiFi (OTA – Over The Air), but only if they are connected. If the thermostat was offline for a long time, or if automatic updates are not enabled, it may be running on a firmware version several versions old. Check the firmware version in the app and compare it with the latest available version on the manufacturer's website. For more details on firmware management, see the article How to maintain and update the firmware of a smart thermostat.

When the problem is likely not the thermostat

From experience – if you have multiple smart devices at home and they all started having connection issues at the same time, the problem is almost certainly in the router or internet connection, not in the thermostat. Restart the router (turn it off, wait 30 seconds, turn it on) and observe what happens.

Similarly: if the thermostat works when accessed via mobile data, but not via home WiFi – the problem is in the local network. If it works at home, but not remotely – the problem may be in the firewall or cloud server.

If you are planning to buy a new thermostat and want to avoid similar problems, read our article How to choose a WiFi thermostat – what to watch out for before buying, where we also cover aspects of reliability and quality of the WiFi module.

Specific situations and less common causes

Thermostat works, but control is delayed by tens of seconds

Latency (delay) of commands via the app is common – the command goes from your phone to the cloud server, then to the thermostat. Normal latency is 1–5 seconds. If you wait 30–60 seconds for each command, something is wrong. Possible causes:

Overloaded cloud server during peak times
Weak WiFi signal at the thermostat – repeated attempts to send a confirmation packet
Thermostat is operating at the edge of the range and messages must be retransmitted

Thermostat responds to local control, but not to the app

If you can change the temperature on the thermostat manually (via buttons), but the app does not respond – the device is working, the problem is in the cloud connection. Check if the thermostat has a WiFi connection (icon on the display) and if the cloud server is available. This is also a scenario where local heating runs normally, but remote control is blocked.

Thermostat does not work after replacing the router

Even if you set up a new router with the same SSID and password, the new router has a different local IP, different DHCP ranges, possibly a different DNS server or different QoS settings. The thermostat may connect, but it may not receive the correct IP or the router may reject DNS requests to the cloud server. Solution: reset the thermostat and perform new pairing. Alternatively, check in the router if the device has been assigned an IP address in the DHCP table.

Comparison: WiFi vs. GSM thermostat in terms of connection reliability

If you have reached this article after a series of frustrating outages with a WiFi thermostat, you may be considering an alternative. GSM thermostats – such as the Elektrobock PT32 GST – operate via a mobile network and SMS messages or data connection via a SIM card. They are not dependent on a home WiFi, router or manufacturer's cloud server.

Advantage of GSM solution: it works wherever the SIM card has signal – including cottages, chalets or industrial buildings. Disadvantage: control via SMS is less convenient than a modern app, SMS costs may arise, and integration with smart home ecosystems (Google Home, Alexa) is limited or non-existent.

A detailed comparison of both technologies can be found in the article WiFi vs. GSM thermostat – what is the difference and which one is worth it.

Frequently asked questions (FAQ)

Why won't my new WiFi thermostat be discovered by the app, even though WiFi is working?

The most common reason: the phone is connected to a 5 GHz network, while the thermostat supports only 2.4 GHz. During pairing, both devices must be on the same network. Another reason: location services (GPS) and/or Bluetooth are not enabled – without them, the Android app will not find the device. Also check the app permissions in your phone settings.

The thermostat worked for months and suddenly it is always offline – what happened?

Possible causes in order: low battery, changed WiFi password/SSID (e.g., after router reset), cloud server outage from the manufacturer, or firmware incompatibility after an automatic update. Proceed systematically: check the batteries, verify network credentials, check the cloud status, and check the firmware and app versions.

Can I use a WiFi thermostat without internet – only in a local network?

It depends on the model. Most standard thermostats require a cloud connection for remote control – without internet, the app will not see the device (even if it communicates physically). There are models with a local API (e.g., compatible with Home Assistant), which work even without internet. If this is important for you, consider it before purchasing – see the article Integration of WiFi thermostats with Google Home, Alexa and smart home systems.

Why does the thermostat work via mobile data, but not via home WiFi?

This means the cloud server is accessible and the thermostat is online – the problem is only in the local network. The thermostat is connected to WiFi and the cloud, but your app at home communicates with the cloud through the local network, where there may be an issue (firewall, DNS filtering, client isolation). Alternatively, the thermostat has a local IP that the router changed, and the app is looking for the old address. Solution: restart the router, check firewall settings, or set a static IP for the thermostat.

What is the recommended distance between the router and the thermostat?

In open space, 2.4 GHz WiFi has a range of 30–50 meters. In a typical house with walls, the real range is 10–25 meters, with each brick wall weakening the signal by 6–12 dBm, and reinforced concrete even more. We recommend measuring the signal at the installation location using a mobile app (WiFi Analyzer) and ensuring that RSSI is not worse than –70 dBm. If not possible, use a WiFi repeater.

The thermostat disconnects and tries to reconnect a few seconds after turning on – why?

This behavior (cyclic restarts of the WiFi module) usually indicates insufficient power or too low battery voltage. WiFi initialization has a short-term peak consumption – if the batteries do not have enough capacity, the voltage drops below the minimum and the module restarts. Replace the batteries with new high-quality alkaline or lithium batteries. If the problem persists even with new batteries, it may be a hardware issue.

Conclusion – a systematic approach saves time and nerves

Issues with a WiFi thermostat are frustrating precisely because the device works physically but "does not respond" – and the error is not immediately clear. The key is a systematic approach: start from the basics (power, signal, network credentials) and proceed toward software and cloud. Most problems can be resolved without any service – it is enough to know where to look.

If you are just in the phase of selecting a new device and want to avoid these problems, take a look at our overview of WiFi and smart thermostats – you will find models with proven connection stability and good app support, including Emos P5623 for simple households and more advanced solutions for higher demands.

Do you have a question about this topic?

Having trouble deciding or dealing with a specific situation in your home? Write to us – we are happy to help.