Closed pvint closed 3 years ago
Original comment by Philippe Van Gastel (Bitbucket: [Philippe Van Gastel](https://bitbucket.org/Philippe Van Gastel), ).
The idea will be to be able to simulate 16 pushbuttons (as commands coming from Alexa and Google Assistant later on), then the NodeMCU will pass them on to 8 GPIO pins as 250ms (simulate short press) and 1500ms (simulate long press) pulses to the home automation that will further take care of the actions.
Cleaning up stale issues - please feel free to reopen if it is still a problem.
Original report by Philippe Van Gastel (Bitbucket: [Philippe Van Gastel](https://bitbucket.org/Philippe Van Gastel), ).
Took the fauxmoESP_External_Server example and installed ESPAsyncTCP ver 1.2.2 and Fauxmoesp ver 3.1.0 and verified that IDE effectively took them during compiling.
The sketch didn’t show any error and displayed correct connection on the serial monitor.
When using the Alexa app on the smartphone, the discovery didn’t find any NodeMCU devices, although the NodeMCU as well as the smartphone are on the same WiFi SSID network.
The app managed to discover other devices, such as the SONOS speakers (after linking the SONOS skill).
Tried to link to the Philips Hue, but it requires a hub which I don’t have.
Tried already 11 other sketches, with only one success by using SINRIC, but I don’t want to move on with SINRIC. The idea is to have a direct NodeMCU to Alexa link without any intermediate party, keeping it as simple as possible with no delays from intermediate items.
Any help would be greatly appreciated.