Closed CNC-Maniac closed 10 months ago
That's not good!
If you can share the configuration file I can try replicating your setup and issuing a fix.
If you don't use the web UI, the MQTT-side alone should be fairly stable and you shouldn't need a recurring reset.
Thank you for the feedback!
@CNC-Maniac et al.
We had a similar issue a number of years back on an early verion of the software. The issue could well be the choice of GPIO pin you have used for the relay. Some of the GPIO pins have special functions and can be either active high, active low or cycle during boot up and is an unavoidable feature of the ESP. we reconfigured our hardware and moved the relay to a safe alternative GPIO pin that doesn't act this way during boot up.
For anyone else that thinks they can tolerate such a thing because it happens once during power up and you do not do timed resets be warned... we developed an instability on one of the really early versions of the software that manifested in continuous boot loops which then left the system always open.
Which gpio pin have you selected for your relay? ooo-xxx
Thank you very much @Divyastra ! That's a good point.
@CNC-Maniac when you can share your config file let me know, I'll have a go :)
Sorry for the delay. Here is my config (I am using the original hardware):
{ "command": "configfile", "network": { "bssid": "DC:39:6F:0D:18:6D", "ssid": "XXXXXXXXX", "wmode": 0, "hide": 0, "pswd": "XXXXXXXXX", "offtime": 0, "dhcp": 1, "ip": "", "subnet": "", "gateway": "", "dns": "", "apip": "192.168.4.1", "apsubnet": "255.255.255.0" }, "hardware": { "readerType": 1, "wgd0pin": 5, "wgd1pin": 4, "sspin": 15, "rfidgain": 32, "wifipin": 2, "rtype": 1, "rpin": 13, "rtime": 1500, "ltype": 0, "buttonpin": 255, "doorstatpin": 255, "maxOpenDoorTime": 0, "doorbellpin": 255, "accessdeniedpin": 255, "openlockpin": 255, "beeperpin": 255, "ledwaitingpin": 255, "useridstoragemode": "decimal", "removeparitybits": true, "numrelays": 1, "relay2": { "rtype": 1, "ltype": 0, "rpin": 4, "rtime": 400 }, "relay3": { "rtype": 1, "ltype": 0, "rpin": 4, "rtime": 400 }, "relay4": { "rtype": 1, "ltype": 0, "rpin": 4, "rtime": 400 }, "readertype": 1, "requirepincodeafterrfid": false, "allowpincodeonly": false, "doorname": "Garage" }, "general": { "hostnm": "esp-rfid-Garage", "restart": 0, "pswd": "Anke1974!", "openinghours": [ "111111111111111111111111", "111111111111111111111111", "111111111111111111111111", "111111111111111111111111", "111111111111111111111111", "111111111111111111111111", "111111111111111111111111" ] }, "mqtt": { "enabled": 1, "host": "192.168.178.246", "port": 1883, "topic": "rfid/Garage", "user": "", "pswd": "", "syncrate": "60", "mqttlog": 1, "autotopic": true, "mqttha": 1 }, "ntp": { "server": "fritz.box", "interval": 30, "timezone": 1, "tzinfo": "CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00" } **}
**
I tooked the autoreboot off right now, but anyway this is also a problem after a power failure
Hello @CNC-Maniac I've finally manged to try your configuration and with my ESP the relay is not triggered on reboot. I'm using GPIO-13 on a NodeMCU v3 (an ESP8266 dev board).
If anyone else can reproduce please let me know, meanwhile try using other GPIO pins as Divyastra suggested.
I'm closing for now, but please reopen if the problem is with the software.
Hello, I have now updated from v1.2 to v2RC. Everything looks good so far and MQTT has become much more convenient. But since I had stability problems with Wifi, I set "auto restart" to 7200sec under general settings. Every time the controller restarts, the relay switches on briefly and my front door is no longer locked.