I have the same issue happen to me yesterday. (Oct 12, 2019) EAF can not be detected any more although it worked the day before. I had reconnected the power and USB several times and no luck. I had tried ASICAP, ASCOM Diagnostics and the SkyX, none of them can "detect" EAF. Since ASCOM can not see it, I guess none of other host applications would not be able to see it.
Yes this is very frustrating if I can not trust it to work reliably.
Here is error from ASCOM:
Create Creating device
Connected Connecting to device
Connected Trying Connected
Connected Trying Link: Object reference not set to an instance of an object.
Error System.NullReferenceException: Object reference not set to an instance of an object.
at System.Dynamic.ExcepInfo.GetException()
at System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)
at CallSite.Target(Closure , CallSite , ComObject , Boolean )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2(CallSite site, T0 arg0, T1 arg1)
at CallSite.Target(Closure , CallSite , Object , Boolean )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2(CallSite site, T0 arg0, T1 arg1)
at ASCOM.DriverConnect.ConnectForm.btnConnect_Click(Object sender, EventArgs e) in C:\ASCOM Build\Export\ASCOM.DriverConnect\ConnectForm.cs 259
Dispose Disposing of device
Dispose Dispose is not implemented inthis driver
ReleaseComObject Releasing COM instance
ReleaseComObject Completed release. Count: 0
GC Collect Starting garbage collection
GC Collect Completed garbage collection