Let's Control It

Hello everybody,

I have installed a Wemos D1 two RFID Wiegand Reader.

open gpio-0 and gpio-2
closed gpio-5 and gpio-6

If I activate it individually the RFID tag correctly assigned to open or closed,

But if both are activated the RFID tag always over open assigned, even if I disconnect gpio-0 and gpio-2.
219755: RFID: tag: 1419114678 bits: 34
219776: EVENT: open # tag = 1419114678
241154: RFID: tag: 1419114678 bits: 34
241155: EVENT: open # tag = 1419114678

The version used is release v2.0.0-dev12

is this a bug?

greetings frank

Hello
same problem at home.
can not configure two RFID devices on a wemos?

The version used is release v2.0.0-dev12
the RFID tag is connected on gpio 12/13 and it is the other one that works ?
the device 4 does not work anymore.

I'm no programmer and didn't look into the code but i assume it's same effect
as with two LCD or OLED displays.

It might be a problem that two devices use the same plugin.

The plugin can not differ between the devices.
Can any of the dev's look into the plugin and confirm?

Push

Hey, I have the same problem with two RFID Reader

Seems a bug indeed, issue on github is here: https://github.com/letscontrolit/ESPEasy/issues/641

maybe its all solved,
but this thread gave me the right hint for trying something new.

this solution-thread pushed me to tell my story:

i have a new 13.67 MHR reader "dc-9" with wiegand output.
as i wired it to me wemos d1 on gpio D3+D4 it got no reading result.
only some misterious message in the log: "bits reset 7/13/24"....
(i looked up the source, message means discarding readings with bit-count less than wiegand 24/36. i guess.
the error message could be clearer..."

i found this thread and wired the reader to D6/D7 (=gpio12/13).
i works.

mabe one has to avoid gpio 0/2 (D3/D4) on espeasy?
or only in Release mega-20181002 from 2018-10-02 ?

i did this 2 years before and it worked with different reader on different espeasy-version. but on gpio0/2 (D3/D4)...
some new feature or bug?

GPIO3 is normally used for the serial port.
Maybe this pin is also connected to a USB => serial adapter?
Or logging enabled?

yes, seems you are right:
i activated serial logging with this new device,
as far as i remember i did this not in the past.
i will check this..

i had i working today at the lab,
now i mounted all at the front-door,
now i get lots of "reset bits messages",
the wiegand is not properly read in..
i am clueless at the moment, how to fix or debug this,
appreciate some ideas..

i asumed noise on the power-supply and used my stable lab-power-source.
still "reset-bits", no stable reading.

last minute i installed a wiegand library from the arduino-IDE (this one: https://github.com/paulo-raca/YetAnothe ... andLibrary)
and used a simple test-sketch from there on the same power-source, same reader, wemos-d1 and ports on which espeasy had no stable readings:
rock-solid readings with the sample-sketch.

maybe the timings in the espeasy-wiegand source needs improvement? or the task-timing interfere?
i dont know yet how to debug further...

next idea: i try downgrading espeasy
from: ESPEasy_mega-20181002 (normal, 4mb)
to: ESPEasy_mega-20180815 (normal, 4mb)

(i have one esp succesfull running for more than a year with espeasy build 145)

I have the same problame. On R147, the RFID reading is stable. If I use newer versions of espeasy the "reset-bits" are not maches.