Constraints Wifi is connected to, not consistant behavior, duplicate SSIDs

[JPM]

Recently I've noticed that constrains where I use "WiFi is connected to..." and then Checked: one (or multiple) my APs - does not consistently work. In looking at the logs the macro does not fire because the constraint was not met.

Curiously, perhaps related to a recent Android 11 update, or Macrodroid update ... seems to have changed the behavior on my phone such that once you connect to an SSID sucesfully, that SSID is duplicated in the list of known networks. This is irregardless of the fact that I may have 1, 2 or 3 physical APs that broadcast the same SSID. Macrodroid also sees this, and now under constraints I have tried checking BOTH of the names, although they are the same.

Already tried the network reset, as well as a full phone reset. Same problem, SSIDs are now duplicated.

Was this a bug introduced by Macrodroid or Google ?

 

[RSF]

I have Android 11 and the most recent MacroDroid release, and haven't seen this behavior on my phone (i.e. duplicate SSID's in my Wifi settings). You might try forgetting one of the duplicates showing in the Android wifi settings, and see if that helps(?)

As a possible clue, even though it's different than what you describe, I'll mention that when I set up my network I used the Comcast/XFinity app, and the SSID got registered in Android as "[My SSID] Connected via Xfi", and that SSID didn't work in Macrodroid. I deleted the XFinity app, forgot the network/SSID, re-connected to the same SSID, and MacroDroid worked fine. So, if your SSID is entangled with an ISP or modem or router app, you might also try re-connecting to the SSID more natively.

 

[JPM]

I have tried removing it manually by doing the "forget this network" - then the duplicate goes away, that's true.... but as soon as I connect, then there are two again. I believe the "network reset" also removed all networks, but as soon as I connect back, boom, duplicate.

I've also tried this with a new SSID, one I've never connected to before - same thing, connect once, then boob, duplicate.

 

[RSF]

Possibly a result of the multiple AP's (which I don't have...)

I've seen mentions that this can occur if the AP's are configured with different passwords or other authentication characteristics, even if the SSID is the same. Any chance the AP's differ in any authentication characteristics?

 

[Abalsam]

I have tried removing it manually by doing the "forget this network" - then the duplicate goes away, that's true.... but as soon as I connect, then there are two again. I believe the "network reset" also removed all networks, but as soon as I connect back, boom, duplicate.

I've also tried this with a new SSID, one I've never connected to before - same thing, connect once, then boob, duplicate.

If you are unable to get this to work, I wonder if you could do something similar with a dhcp reservation to a specific ip address. Ie if the phone gets this ip (192.168.100.200) trigger.....

 

[cwallen19803]

I have three transmitters, all with the same SSID.

Different channels. 1, 11, 48.

Same security, i.e. password, encryption.

I also reserve a specific ip per device so there are no conflicts.

I think the key is different channels, same security.

 

[cwallen19803]

The other thing is that the transmitters need sufficient separation so that the device doesn't thrash trying to pick the best signal. I have one (g) in the NE corner of the basement and one (g) in the SW corner of the second floor. The is also in the basement but separated by a cement wall. It all works out. My phone and tablet figure it out with a minimum of droppage.

 

[Abalsam]

The other thing is that the transmitters need sufficient separation so that the device doesn't thrash trying to pick the best signal. I have one (g) in the NE corner of the basement and one (g) in the SW corner of the second floor. The is also in the basement but separated by a cement wall. It all works out. My phone and tablet figure it out with a minimum of droppage.

This is where mesh comes in handy as the nodes all broadcast on the same channel and the ap boots the client when the signal gets to weak.

 

[MacroDroidDev]

@JPM When the constraint is failing unexpectedly it would be worth using the log event action to log the current SSID (using the ... magic text). It will be interesting to see what the SSID reported here is.

I haven't changed anything in MacroDroid in this area for quite some time so I don't think any recent update should change behaviour here.

 

[JPM]

So the SSID duplication, I have confirmed, is an issue caused by the Android 11 update on specific Motorola phones. I'm obviously not going to hold my breath on when Lenovo will get around to fixing that, so be it.

I am now doing the extra logging using the magic text to see the IP, SSID, and signal strength at the time - that will be interesting.

I very much like the idea of using the current IP instead of the SSID - seems that would be more reliable in any case - I'm already using a DHCP reservation for my, and family member's phones (because our home automation system periodically pings each phone to determine who is home, or not, and that is a basis for other automatons, such as turning off all the lights when the last person has gone, etc.)

I will report back what I find - thanks for the ideas.

 

[JPM]

So, the log states it was connected to the right SSID and with signal -67, but later I get "did not fire because constraint failed:"

This WiFi duplication thing is apparently a problem on both Mororola's "g power (2021)" and "edge (2021)" phones after the Android 11 update push. For others following, this happens regardless of having multiple APs, or not, and regardless of having 2.4Ghz and 5Ghz SSIDs broadcast with exactly the same SSID and WPA properties (as you should for roaming and 5Ghz handoff to happen automatically). The duplication will still occur if you connect to a purely 2.4Ghz network having only a single AP.

Am I correct that I can't do Constraint = when IP address is 192.168.x.x directly, but rather I need to do a macro that sets a variable to the current IP when it changes, and then Constraint = when variable matches 192.168.x.x - this is what I'm doing now, and it's working great so far!

 

[MacroDroidDev]

I'm putting some code into the next update to mitigate the duplicate SSID issue. I'm not sure it will solve your issue specifically but it shouldn't make things worse in any case!

You are correct there is currently no ip address constraint. It's certainly one that I can consider adding so I will add it to my TODO list for some point in the future.

 

[JPM]

I've been relying on the IP variable as the constraint for a few days. It's working great. Curiously I've noticed in the logs for the event that sets the IP to the variable, is that whenever my phone transitions between APs, the IP is also reset to the variable, even if it is the same. Occasionally the log fails to pickup the SSID, although the signal strength and IP (always my intended IP, the DHCP reservation) are logged - this suggests to me roaming is less of a roam, and more of a disconnect from one and re-connect to the other. I suppose I could confirm that if I was logging my DHCP server as well.

In any case, after working with Motorola support, they wanted me to do a full device reset again, and pay attention to what apps I load, one by one, incase the WiFi duplication issue shows up again. I thought that was silly tier 1 troubleshooting hoops to jump through, since I had already done a full reset, and the WiFi duplication issue was happening immediately, even before I loaded any apps. But miraculously, something has happened, because the SSIDs are no longer duplicating. So... yeah... I guess two resets are better than one - still trying to figure that one out.

Thanks for the attention to this, even though I guess it's no longer an issue.

 

[dsnz]

a duplicate reset is the solution