myIO is meant to run for years without a restart, so if something does not work, there is a reason, and the reason can usually be found. In our experience most problems are not faults but settings: the router’s, the app’s or myIO’s. Here you can look up what to check, by symptom.
Start here
- What has changed recently? A new router or internet provider, a power cut, a changed setting, a new phone? The cause is most often the last change.
- Do the wall buttons work? If they do, the house is fine and only access is faltering: the network, the app or the remote connection. If the buttons don’t switch either, look at the controller or the settings.
- Try another way in. If the app does not work, open the myIO web interface in a browser; if it does not work from the phone, try a computer. This shows where it gets stuck.
- Save before you change anything. The floppy icon at the right end of the web interface’s menu bar saves the current state, and if something goes wrong you can load it back.
I can’t reach myIO even at home
I don't know the address of my myIO
The address (IP address) of your myIO is shown on the service display in the cabinet: on the controller for V3 and V4 GIGA, on the Expander 16 for V4 Opta. Type it into the browser’s address bar, for example http://192.168.1.170.
If the display is not at hand:
- look for myIO in your router’s device list;
- if myIO does not get its address automatically, its default address is
192.168.1.170; - if the network name is switched on, you can also reach it by name, for example
http://myio-nappali.local.
The browser does not load the myIO page
- Is your phone or computer on the same home network as myIO? The home address cannot be reached from mobile data or from the guest Wi‑Fi.
- The address must start with
http://, nothttps://. - Check in the cabinet that myIO has power and that its network cable is plugged into the router: the light at the socket is on or blinking.
- Restart the router. If it works afterwards, the router was stuck, not myIO.
Since the router was replaced I can't reach it even at home
The new router probably hands out different addresses from the old one, for example 192.168.0.x instead of the earlier 192.168.1.x. If myIO has a fixed address in the old range, it is not visible on the new network.
The simplest fix is to set the same address range on the new router that the old one used. Then myIO and every other device with a fixed address (camera, printer) stays in place. If you don’t want that, the address of myIO has to be changed; your electrician or we can help with it, write to us.
On V4 Opta there is a quicker way too: hold the controller’s USER button for 5 seconds, and the network settings return to default (myIO gets its address automatically), while the login becomes admin / admin. The new address is shown on the service display of the Expander 16. Change the password afterwards.
I forgot the password
- V3 and V4 GIGA: you can reset the users from the service display. After that you get in with the factory login (admin / admin); change the password as the first step.
- V4 Opta: hold the controller’s USER button for 5 seconds. The network settings and the users (admin / admin) return to default, the controller restarts, and its new address is shown on the service display of the Expander 16.
The password is right, but it still won't let me in
If you tried several different wrong passwords before, myIO stops accepting logins from that device for a while, even with the right password. The lock is a few seconds at first, longer with repeated attempts, a quarter of an hour at most. Wait, then try again with the right password.
I can’t reach it remotely, although it works at home
If everything works at home, on your own Wi‑Fi, myIO is fine: the problem is on the way between your home and the internet, almost always at the router or the provider. There are three ways to reach the house remotely; the Control page presents them. First check which one you use:
- you paired the phone with a QR code: myIO Cloud;
- you switch on a VPN on the phone before opening the app: VPN;
- in the app the address of myIO is a name (for example
something.ddns.net), or a number not starting with 192.168: port forwarding.
After replacing the router or changing provider I can't reach it remotely
Port forwarding, the permanent name (DDNS) and the VPN are set up in the router, not in myIO. The new router does not have them, so they have to be set up again:
- Permanent internal address: myIO always gets the same address on the home network (a fixed address in myIO, or an address reservation in the router).
- Port forwarding: you direct an external port of the router to the internal address and port of myIO.
- DDNS: you enter the account details of your permanent name into the new router, so that it follows the changing address.
- VPN: the VPN server has to be created again on the new router, and the phone set up with the new details.
If it was not you who set it up at the time, leave it to whoever installs the router. On V4 GIGA and V4 Opta you can spare all of this with myIO Cloud: it works after a router change too, as soon as myIO has internet again.
Everything is set up, yet it does not work: do you have your own public address?
Port forwarding and a VPN running on the router only work if your home gets its own public address (public IP address) from the provider. More and more providers put several subscribers behind one shared address; this is called CGNAT. Home internet over the mobile network is almost always like this. In that case your router cannot be reached from outside, whatever you set on it.
How to check:
- Look at the internet-side (WAN) address on your router’s status page.
- From home, open a “what is my IP address” page and see what address it shows.
- If the two differ, or the router’s address starts with 10, with a number between 100.64 and 100.127, with a number between 172.16 and 172.31, or with 192.168, you don’t have your own public address.
There are two solutions. Ask your provider for a public address: some give one on request, some for a fee. Or use myIO Cloud (V4 GIGA, V4 Opta), which needs no public address.
There are two routers, one behind the other
If the provider’s device is a router too, and yours sits behind it, a request from outside has to get through both. Either forward the port on the provider’s device as well, towards your own router, or have the provider’s device switched to modem (bridge) mode, so that only yours is a router. When the provider replaces its device, this setting is often lost.
It worked for a while, then stopped: the permanent name (DDNS)
The public address of most homes changes from time to time. DDNS follows this: a permanent name that always points to the currently valid address. If the name stays stuck at the old address, you can’t find your way home remotely.
- Log in at your DDNS provider and see what address your name points to. Compare it with what a “what is my IP address” page shows from home.
- Free DDNS accounts have to be confirmed regularly, otherwise the name lapses.
- In the router, or in the device that updates the address, the DDNS account details should be entered and its status should be successful.
It works at home but not away, or the other way round
In the app one address belongs to one myIO.
- If it is the home address (starting with 192.168), the app only reaches myIO on the home Wi‑Fi. For remote access you need myIO Cloud, a VPN or port forwarding.
- If it is your external name (DDNS), and it works away but not at home: your router does not let you reach your own network from inside by your external address. This can be switched on in the router, if it supports it; it is called NAT loopback or hairpin NAT.
- With a VPN, the app should hold the home address of myIO, and the VPN should be on before you open the app.
myIO Cloud does not connect
- Is there internet at home? myIO connects outwards to the Cloud, over the wired network. If there is no internet at home, you can’t reach it remotely either.
- Is the phone paired? In the myIO web interface, on the myIO Cloud page, the row of your phone should be in the “paired” state. Commands from a revoked phone are not executed.
- Did you switch to a new phone? Pairing is tied to the phone: the new phone has to be paired with the QR code too.
- myIO Cloud works in the installed app, not from the browser.
It doesn’t switch, or not the way I expected
The best help here is the Links panel. On the settings pages of the web interface, right-click the row of an item (long press on a phone), and it shows everything that controls it: buttons, timers, a thermometer, groups.
An item is not shown on the main page or in the app
There can be two reasons: it has no name, or your user has no permission for it. Only named items appear on the main page: on the settings page turn on the SuperVisor switch in the menu bar and give the item a name. If it has a name, check on the System › Users page whether your user may see and switch it.
I switch it on and it switches off by itself, or the other way round
Something else controls the same output too. The most common causes:
- a thermometer controls it, so it works as a thermostat: the temperature decides and overrides manual switching;
- a timer switches it, or the output has its own switch-off time, like a staircase light;
- it is a member of a group, and someone switched the group;
- it follows another output;
- the Energy Manager switches it, or on V4 a Flow rule.
The Links panel shows which one applies. What exactly switched it and when is shown on the System › Log page: every switching has its source next to it (button, web, timer, thermostat).
It won't let me switch it on
Two outputs can lock each other out: the up and down directions of a blind, for example, can never be powered at the same time. While one is running the other does not switch on, and for a few seconds after the clash further requests for the blocked side are dropped as well. This is protection, not a fault. If outputs lock each other out that should not, the “Protection / lockout” row of the Links panel shows the pair.
The wall button switches the wrong thing, or nothing
- On the Input page of the web interface turn on button monitoring and press the button. Its row is highlighted, so you see which input it arrives on and what is assigned to it.
- If nothing is highlighted when you press the button, the signal does not reach the controller. That is a wiring matter for your electrician.
- A button can do three things: short press, long press, release. Check that you assigned the target to the right one.
- The input may also be disabled: check the “Enabled” checkbox.
- You can teach it again with the setup wizard: you press the button on the wall, myIO recognises it, and you choose what it should switch.
It works in reverse: dark when on, lit when off
In the settings row of the output there is an Invert checkbox. Change it, and if it works properly that way, save. If changing the checkbox does not help, the wiring of the relay has to be checked; that is your electrician’s job, and the details are below, in the For professionals part.
My settings were lost after a restart
Changes take effect immediately, but only what you saved survives a restart or a power cut. You save with the floppy icon at the right end of the menu bar. On start-up myIO loads the boot save, so after a bigger change save there.
I changed something and it has not been right since
Load back the last good save: on the Load page under the floppy icon of the menu bar. This is why it is worth saving before every bigger change.
The timer switches at the wrong time
- On the System › General page check the time zone, and whether the time sync works. myIO takes the exact time from the internet.
- If the difference is exactly one hour: the automatic daylight saving time checkbox should be on, and the time zone should be the standard (winter) offset (1 in Central Europe).
- For a timer tied to sunrise or sunset, the geographic coordinates of the house matter too.
After a power cut, what was running did not come back on
This is intentional. When the power returns, myIO restarts and all its outputs start from the off state, so that the lights don’t come on by themselves in the middle of the night. The heating is switched back on by the control, based on the thermometers, wherever it is needed.
Thermometers and heating
A thermometer shows 85 or 127 degrees
This is not a real temperature but an error signal: the thermometer, or the wire leading to it, is not working properly.
- 127 °C (or −127 °C): the thermometer did not answer the query. Mostly a fault of the wire or a connection, more rarely of the thermometer itself.
- 85 °C (or −85 °C): the thermometer lost its supply before the measurement and restarted. It points to a supply or contact fault.
Observe whether one thermometer is faulty or several, and whether constantly or only sometimes. Tell this to your electrician or to us: the place of the fault can be narrowed down from it. The measurement details are below, in the For professionals part.
The thermometer is in the "STALE" state and the heating keeps switching on and off
This happens with thermometers that report over the network (V4): the thermometer did not send data in time. myIO then deliberately heats about half of the time, so that the room neither cools down nor overheats. As soon as the thermometer sends data again, the switching stops by itself. Check the thermometer: does it have power or a good battery, and does it reach the network?
The room is cold, yet the heating is not on
- Check the room’s thermometer and the set temperature in the app or on the main page: heating starts when the temperature falls below the switch-on value.
- If the heating output is on but the radiator or the floor is cold, myIO is asking for heat, and the fault is at the boiler, the heat pump, the valve or the pump. Call the heating engineer.
- Was the window open? On V4, MIA notices the sudden cooling and pauses the heating of the room while the window is open.
- If load limiting in the Energy Manager switches heating circuits too, it may have switched the circuit off at a time of high consumption.
It is warmer or colder than what I set
Heating works between two values: it switches on at the lower one and off at the upper one. If the two are far apart, the temperature swings more; you can narrow this in the settings of the output. It also matters where the thermometer is: in a sunny spot, above a radiator or on an outside wall it measures something different from what you feel in the room. On V4, MIA learns how the room behaves and closes the heating earlier, so that it does not overshoot the target.
The myIO App
In the app myIO is "offline", although its web interface works
Check the address and port of myIO in the app, and that the username and password match the web login. If it is “offline” only when you are away, look at remote access, as described above.
No notifications arrive on the phone
Allow the app’s notifications in the Android settings, and exclude the app from battery optimisation. In the browser, notifications are only certain while the tab is open.
The other app cases, such as use in the car and cameras, are covered in the Installing the app guide and in the last chapter of the app manual (in Hungarian).
If you didn’t find it
There are two more ways, both starting from the Support page:
- Ask your AI assistant. We give you a ready-made sample prompt, and the assistant works from the myIO documentation, or even from the settings of your own myIO.
- Write to us on the Report a problem form. Tell us which controller you have, what you did, what you expected, what happened instead, and what changed before.
For professionals
- Basic checks for wiring faults: every module has supply voltage; with several power supplies the GNDs are common; the address switches (DIP, jumper) of the expanders do not clash; the connections are free of contact faults.
- Thermometers (DS18B20, 1-Wire): 5 V supply. Shielded Cat5e (FTP) cable is recommended, with the supply on a twisted pair; connect the shield only when justified, because it increases the capacitance of the line. Do not run it next to mains wiring. Star and tree layouts both work, but keep the cable per bus as short as possible. Do not twist the unused cores of the cable onto the used ones: cut them off, or tie them to GND.
- ±127: the thermometer was present earlier but did not answer the query. Mostly the signal shape on the data line is distorted; on a long or noisy line a level shifter helps. ±85: the power-on default value of the thermometer, so it lost its supply before the query: contact fault, voltage drop or a faulty thermometer.
- One faulty thermometer can ruin the data traffic or the supply of the whole bus: find it by disconnecting them one by one. Test: one thermometer wired directly to the controller’s input. If it is not seen even so, the thermometer or the input is faulty. With recurring failures, look for a source of overvoltage.
- Relay working in reverse: the load is on the normally closed (NC) contact instead of the normally open (NO) one, or the relay module is wired inverted. With inverted wiring the common point of the coils gets fixed positive supply, with non-inverted wiring GND; the Invert checkbox must match this.
- Direct connection to a computer: the computer’s fixed address must be in the same range as the controller but different from it. Default address without DHCP: 192.168.1.170; in V4 Wi‑Fi access point mode: 192.168.3.1.
- V4 Opta, USER button: short press = restart; 5 s = network and users back to default. Status light: slow blinking = running and has an IP address; fast blinking = no IP address.
- Port forwarding: direct the controller’s web port (80) to a freely chosen external port, not to 80. The connection is unencrypted, so a strong password is needed. The login lock works per address: if the router passes external requests on from its own address, the lock affects all external devices at once.
- No public address (CGNAT): the provider address range is 100.64.0.0/10. A VPN that builds outwards, to a server with a public address, can be a solution too.
- myIO Cloud: an outgoing, encrypted connection on port 8883. If the network’s firewall blocks this outgoing port, the Cloud does not connect.
- Diagnostics in the web interface: System › Log (in 4.x software with an Error / Info / Debug filter and search; the daily log file can be downloaded from the file manager), Apps › System diagnostics (network connections, memory, cause of the last restart), and on V4 the System › Network page.
- The login lock is available from software 3.12.28 on V3 and 4.16.1 on V4; button monitoring from software 3.12.7 on V3, and on V4.
- AI diagnostics on your own controller (myIO MCP): Support.