Revision History

[Tuicemen]

I just got some more info on the newest update. This was tested a while ago to fix the issue android users were getting with <unknown SSiD>
Although Authinx was getting mixed results with this fix it looks like the developer went ahead and released it anyways

[Walt2]

Well, after waiting like forever, a new version finally came out, but it didn't fix my problem ( Can't See QR Code (Can't Access Camera) ).     

Just to mention, during this long, long wait, I purchased another hardware device.   Like X10, its app uses the device's camera to read in a unique scan code to connect and register the hardware.   Unlike X10, it has no problem accessing my device's camera.  Plus, they were smart enough to offer an alternative (non-camera) method where the user/customer manual types in the numerical code/value from the scan code.

Ah well, back to waiting.   Waiting for X10 to fix their bug.   

[Walt2]

New bug.   

With the new version of the X10 app...

On my older phone, running Android 8, I can exit the app with using the "back" button from the home screen.   Of course, I get the "are you sure" popup.

On my new phone, running Android 9, I can't exit the app.   The "back" button still works within the app, like to return to the previous screen, but no longer will it exit the app if I am at the home screen.   

[timlight10]

On my new phone, running Android 9, I can't exit the app.   The "back" button still works within the app, like to return to the previous screen, but no longer will it exit the app if I am at the home screen.

I am having the same problem.

[Knightrider]

It also seems the new update broke the device status on my app.  I have WM100 timers turning on lights and the app shows they're off.

I initially thought this was due to miscommunication with my CM15A, but I've since pulled all CM15s out of service and the problem persists.

[Tuicemen]

It also seems the new update broke the device status on my app.  I have WM100 timers turning on lights and the app shows they're off.

I initially thought this was due to miscommunication with my CM15A, but I've since pulled all CM15s out of service and the problem persists.

Authinx was concerned something would break with this update and asked the author for a way to revert. I'll see if this was ever done.

[dave w]

Authinx was concerned something would break with this update and asked the author for a way to revert.

Quote Hans Solo: "Got a bad feeling about this."

[petera]

Authinx was concerned something would break with this update and asked the author for a way to revert.

Quote Hans Solo: "Got a bad feeling about this."

At least a broken clock shows the correct time twice a day 

[timlight10]

Any idea what the firmware version 0.0.27 brings to the table?

[Tuicemen]

A firmware update usually means a app update is coming. I doubt we'll notice anything till then.