2 Shelly Plus 2PM Unreachable

[ava8c]

Hi. A strange thing is happening to me. I bought 2 Shelly 2PM on Amazon last July (hardware model B0124) to control the shutters. I tried to change the firmware and I think I burned both of them:

• I flashed the first one leaving the script preconfigured, everything went well I was able to put the two switches in home and control them (hearing the switch). At this point I changed the configuration and put the following one (the non OLD one that controls temperature and current). Result: I can't reach it anymore (it's connected to wifi) but I don see it in HAA manager nor Home app

{"c":{"io":[[[12,13,0],2],[[4],6,1],[[5,18],6,0,1],[[35],10,0,3],[[27]]],"l":0,"b":[[4,5]],"ic":[[25,26,100]]},"a":[{"t":45,"o":18.3,"c":14.8,"f":40,"0":{"r":[[13],[12,1]],"m":[[2,-10001],[3,-10001]]},"1":{"r":[[13,1],[12]],"m":[[2,-10001],[3,-10001]]},"2":{"r":[[13],[12]],"m":[[2,-10000],[3,-10000]]},"3":{"r":[[13],[12,0,0.2]],"m":[[2,-10001],[3,-10001]]},"4":{"r":[[13,0,0.2],[12]],"m":[[2,-10001],[3,-10001]]},"8":{"m":[[0,101]]},"f0":[[5,0]],"f1":[[18,0]],"f2":[[5],[18]],"es":[{"t":75,"h":2,"ks":0,"j":2,"cd":0.95,"n":2,"dt":[0,56],"vf":0.0000382602,"vo":-0.068,"cf":0.00000949523,"co":-0.017,"pf":0.006097560976,"y1":[{"v":2,"r":1,"0":{"m":[[1,-1]]}},{"v":2.5}]},{"t":75,"h":2,"ks":0,"j":2,"cd":0.45,"n":3,"dt":[0,56],"vf":0.0000382602,"vo":-0.068,"cf":0.00000949523,"co":-0.017,"pf":0.006097560976,"y1":[{"v":2,"r":1,"0":{"m":[[1,-1]]}},{"v":2.5}]},{"t":22,"h":2,"n":5,"g":35,"j":5,"y0":[{"v":75,"r":1,"0":{"m":[[1,-1]]}}]}]}]}

• The second one, on the other hand, I flashed it directly with the previous script you (copied from GitHub) and here is the real strange thing: on the HAA Manager app the flashing process finished fine.
  0220.954 192.168.1.112-CE05EC: - 900352
  0220.956 192.168.1.112-CE05EC: >>> Verify
  0225.149 192.168.1.112-CE05EC: >>> OK
  0225.149 192.168.1.112-CE05EC: *** FINISHING
  0225.153 192.168.1.112-CE05EC: * HAAMAIN 12.13.1 installed
  0225.153 192.168.1.112-CE05EC: *** REBOOTING
  However adding in the home app the device was detected as two switch and not as a shutter, trying to command I did not hear the switch and after a couple of checks (not hearing the switch) it is no longer detectable in either the home app or the HAA manager app. The router sees it connected but I can't even access the configuration page at 192.168.1.112:4567.

I don't understand how to decide whether to use the scripts indicated with “Old” or not.

Anyone can helm me? Thanks!

[ava8c]

I managed to access the second one and I changed configuration to the "old one"
{"c":{"io":[[[12,13,0],2],[[27],6,1],[[2,18],6,0,1],[[37],10,0,3],[[36]]],"l":0,"b":[[27,5]],"ic":[[25,33,100]]},"a":[{"t":45,"o":18.3,"c":14.8,"f":40,"0":{"r":[[13],[12,1]],"m":[[2,-10001],[3,-10001]]},"1":{"r":[[13,1],[12]],"m":[[2,-10001],[3,-10001]]},"2":{"r":[[13],[12]],"m":[[2,-10000],[3,-10000]]},"3":{"r":[[13],[12,0,0.2]],"m":[[2,-10001],[3,-10001]]},"4":{"r":[[13,0,0.2],[12]],"m":[[2,-10001],[3,-10001]]},"8":{"m":[[0,101]]},"f0":[[2,0]],"f1":[[18,0]],"f2":[[2],[18]],"es":[{"t":75,"h":2,"ks":0,"j":2,"cd":0.95,"n":2,"dt":[0,56],"vf":0.0000382602,"vo":-0.068,"cf":0.00000949523,"co":-0.017,"pf":0.006097560976,"y1":[{"v":2,"r":1,"0":{"m":[[1,-1]]}},{"v":2.5}]},{"t":75,"h":2,"ks":0,"j":2,"cd":0.45,"n":3,"dt":[0,56],"vf":0.0000382602,"vo":-0.068,"cf":0.00000949523,"co":-0.017,"pf":0.006097560976,"y1":[{"v":2,"r":1,"0":{"m":[[1,-1]]}},{"v":2.5}]},{"t":22,"h":2,"n":5,"g":37,"j":5,"y0":[{"v":75,"r":1,"0":{"m":[[1,-1]]}}]}]}]}

now in HAA Manager I see it is a "switch" instead of "window covering"

Is it possible that it is due to the fact that I haven't linked the shelly to the motor yet?

I still can't access the first one even if mDNS Logs see it

Aug 31 15:10:41 [HAA-CD3FB0] Discovered
Aug 31 15:10:41 [HAA-CD3FB0] Resolved to 192.168.1.58:5556

[ava8c]

Okay I was able to solve it.
What I was doing wrong was the process:

• I was setting the json script
• I was updating the wifi list
• I was entering password
• press OK
• I would add the device to Home

The first problem is that updating the wifi list would reset the script so I would always add the default script.
Then adding the device to home and taking it out later would not reset the device type so it was seen as a switch and not windows covering by the HAA manager app.

so the solution to the first problem is always to enter the wifi password first and then the script.

Whereas if you have already added a wrong device, simply do reset HomeKit id on the configuration page.