Hi Guys

Hoping someone smart can assist me. 

I have(had) a perfeclty working ET DC500 gate motor, and then recently purchsed the Sonoff SV 7-32 click Self Locking module. 

I followed the following blog post https://hometechtime.com/how-to-automate-your-gate-with-a-sonoff-wifi-smart-switch/, as i pretty much have the exact setup. 

I wired the ‘Normally Open’ terminal of the Sonoff to the BT connector on the gate motor and the ‘Common’ terminal of the Sonoff to the CM terminal on the gate motor.

Everything seemed fine, the device paired and i was able to turn it on in the app, i set the inching to 0.5 sec.

Then the problem started, when pressing the button in the app, the gate only went forward for a few seconds and then stopped.  So i pressed it again and same thing. Went to my remote to see if that would work but its doing the exact same thing as the app. Its even by passing the limits previosly set and trying to close the gate to far. 

Its so strange as i cant even set the gate motor limits, its just inches closed for a few seconds and then stops. If i keep try inching it forward it eventually stops, beeps like crazy and then the ST led light flashes, at which point i have to manually release the motor to reet it and then start the process again.

What have i done to this thing? And is there a way to completely reset it? I reset all the remotes, and removed the ewelink, but it didnt help. 

Edited January 14, 20251 yr by Walnut

Hallo

Not sure if you used the pedestrian trigger.

Also, I dont know those motors. Can you post photos of how you set it up?

I thought that could have been the issue but i doubled checked and its not. Why though would that have effected all the exisitng remotes to change their programming behaivour? Will post a pic of the board connections. 

The 2 brown wires go to the various corrisponding ports on the Ewelink module. 

I messaged Nice (the gate motor company) and they want me to send the board in to them. Which seems crazy, surely its just a setting or something. 

So the board is going into Nice tomorrow, i spoke to them and they will test it for me. 

Will post back here for the SEO in case anyone else has issues. 

Update:

 

I am an idiot 

 

So i took it to Nice in Observatory, they were super helpful, stuck the board in a dummy motor and it worked fine. They then asked me if i was testing the gate with the board outside the black housing, which i was. This was the cause of all my issues as there is a sensor in the black housing and another on the board. They need to pick each other up so the board knows the gate is connected. If its not it goes into error mode.

 

Came home, screwed the board down, and all is working. Inching mode is set to 1 sec, which seems to work better than 0.5 for me. All works great. 

i was struggling with the exact same issue today and upon searching for answers i came across your post. cant wait to get home in the morning to try it out. keeping fingers crossed that its indeed the fact that i too had the board outside of the casing.