Randomly losing Wifi-Connection

[xudabit]

Hi there,

I have a problem with all of my 6 faikin-modules. Sometimes they just lose the connection for several hours before they reconnect without any changes. They don't show up as AP in that time. After disconnecting the plug and reconnecting it they connect directly to the existing WiFi without any problems.

Is there anybode else with a similar problem? Is there any option to get some kind of logfile to diagnose what happend? I would love some kind of logfile which I could look at after it reconnects again.

I'm using these as primary heating-solution so I rely on them. I think they do work in the meantime, but with the wrong temperature.

Thanks in regards

[revk]

WiFi is always fun - are they inside a metal case ? How far away is access point ?

May be worth setting up a 2.4GHz only SSID for them.

[xudabit]

Having one unit disconnected at the moment, checked the router and saw that the mac-address is still connected to the wifi of my AP in the garage. Then I disconnected it via the router-webinterface and it reconnected automatically to one of the APs in the house, which is fine (it is in the range of booth). Webinterface tells me it gave the device the correct IP-Address, but it's not accessible. Is there any option in the webinterface to give the faikin a static-ip? I can't see any option.

I disconnected it again via router-webinterface and took a tcpdump. Looks fine to me. Regular DHCP-Traffic (Discover, Offer, Request, Acknowledge). So the device should have an IP-address, but is still not reachable. At least this means, that the device itself isn't dead, so I don't think it's some hardware-problem. But it's also not reachable via ping. The firewall allows every traffic to the iot-vlan.

[revk]

There are fixed IP options somewhere in the settings (Library) such as wifiip.

This does sound strange - I'd consider rebooting your network switches even in cache some weird MAC cache issue.

You can also lock the bssid to stop any AP roaming, in case that helps.

[xudabit]

I rebooted my APs. Will also reboot the switch. So far the module is not reconnecting.

Will "replug" it now and let it reconnect. I disabled Fast-roaming for the iot-wifi, because they normally don't move. And I raised the lease-time from 5 minutes to 7 days for the faikin-devices. Hopefully this helps.

Thanks so far for your effort.

[xudabit]

I think I found so problem. My automations (NodeRed) use the status from the faikin-module as trigger, so they calculate the new value for "demand" and other things. Normally this seems to work just fine, but there seem to be constellations where there are just too many MQTT-messages (maybe it creates some kind of loop) so the module is overloaded and does not react anymore.

I changed my automation to start every 5 seconds and send a message if anything changed. So far no problems for a week.

Thanks for your help and sorry for the effort.

[revk]

It could be that too many messages are an issue I guess. Glad you found it.