Two DFPlayers on one ESP easy?

[crxporter]

I am getting started on a new project and am curious if ESP Easy is the software for me. I believe I have things set up properly but I can't test until I get my new hardware in the mail - I'm looking at connecting two DFPlayer (DFR0299) chips to one Wemos D1 Mini. I don't see any reason this shouldn't work apart from the fact that the commands are just "play,track#" - not seeming to point to one or the other pin the separate players are connected to.

I'll be running this into a two-channel amplifier with a speaker in each of my daughters' rooms. The idea is to play bedtime music but separately in each room.

So the question: is the ESP Easy capable of sending commands separately to two players using just one wemos?

[grovkillen]

What you aim for is not possible at the moment, only one player is recommended. But until (if it's even is considered useful) I would suggest you use two ESP boards instead of trying to do it with one. I can't really see the benefit with one vs two? Please enlighten me on that one

[crxporter]

Well yes of course I could use two boards.

The reason I'd like to run it on just one is because it seems like it should be possible. The Wemos is has something like 7 or 8 usable outputs (depending on function) so why would I want to use two within 3 inches of each other instead of just run both MP3 players with one controller?

I've been digging deeper and I've found that the DFPlayer plugin is "Plugin 065" - I'm considering building myself a custom "Plugin 165" (or whichever number I choose) with "play" "volume" and "stop" functions changed to "playa" "volumea" and "stopa" functions. The 165 would simply be a copy of 065 - modified with new function names and pointed to a different GPIO on the Wemos board.

Unless someone knows a reason this isn't going to work well, I'm off to figure out how to build myself a .bin file!

[TD-er]

Often the problem is in sharing variables when trying to run multiple instances of the same plugin.
If you copy the plugin and change all references of 65 to 165 then I guess it might just work, since you're no longer running the same instance of the object anymore.
Just make sure no function names and global variables share the same name, but the compiler will tell you that when compiling

If that plugin is using some external library, you may run into the same issues, since it has not been tested.