Can not use camera (for scanning QR codes when doing inclusion)

[larhedse]

Strange thing: I can not use the Camera for scanning QR codes for S2 Inclusion into Z-Wave, on my Samsung Fold 3 or Samsung TAB S7 (both on Samsung UI 6.1 = absolute latest and greatest firmware for Android). Now I am new to using Z-Wave JS UI (with Home Assistant) however I expect the process to kind of straight forward, so it should not be an issue. Yes I do allow "Camera" in the app (both devices). However one thing I kind of expected was that is also should use storage?

Anyway, so when I could not scan with the "Camera" (no picture, and a button labeled "Retry" to no good - just nothing happens, no picture no nothing), I decided for a workaround: Take a picture and use the file input. Nope - that does not work either. I could select the file, but it could not process it. Could it be a storage security thing like the what I think above?

Anyway, there is no way for me to include a Fibaro S2 security product (since Fibaro seems to not like to print the 5-digit code on there products...).

So what am I doing wrong here? Why no camera?

[larhedse]

More info:

Above was with the Android App - So I thought I change to web browser, and well circumvent what ever.

No luck:

• Firefox on my Android Samsung Tab 7 - can not read the QR file, can not use the camera.
• Firefox on Windows 10 (MS Surface Book 2, yes a bit old but it works) - can not read the QR file, and can not find the camera.

Now the camera on my Surface Book 2 works just fine, just like the camera on my mobile Samsung Fold 3, and the camera on my Samsung Tab 7.

From my perspective, it does not matter what kind of QR solution I try to use - they all fail. And it is not related to OS (tested Android and Win10), nor the Android app (Fold/TAB) or Firefox browser (Fold/TAB/Win10). I have also tested Chrome on my Win10 (MS Surface Book 2) - same story.

The QR Code inclusion does not work. Not over camera, not over file input.

[larhedse]

This is the QR Code I have tested (I also, just in case and all that, have another QR code - both Fibaro units if it matters).

[cornellrwilliams]

1. In order to use the camera you need to have https setup. I believe in older versions of Z-Wave JS UI it would give you an error if you tried to scan a qr code without having https setup. I have it setup and it works great.
2. Smart Start and S2 Security are two separate things. This means your device can support S2 security but not smart start.
3. I don't think your device supports smart start. There are 3 reasons I believe this.
   • First your QR code is not a valid smart start QR Code. It should look like this.
   • Second when scanning the QR Code it should return a 52 character number that starts with 90. Once you have this 52 digit number you could then take that and input it into the text field on the smart start page. Scanning your QR Code returns an 9 digit code.
   • Lastly only 2 Fibaro products support smart start https://products.z-wavealliance.org/Search/DoAdvancedSearch?productName=&productIdentifier=&productDescription=&category=-1&brand=171&regionId=2&supportsS2=on&supportsSmartStart=on&order=.

[kpine]

That's definitely not a SmartStart QR code, and not even a QR code. It's a Data Matrix.

If you use something like Binary Eye it will tell you the type of code and the decoded value. It tells me it decodes to the ASCII characters 000604075.

[larhedse]

Right!

Thanks for your help - both of you, and since I am not going to change all my Fibaro stuff, there is just no reason to try to go to S2 security - it is simply put not supported (by Fibaro, which is of course very bad and typically Fibaro...) - and not to turn on SSL either (my Home Assistant is a "closed box system"). Why bother when it is not needed....

[larhedse]

No need for any more information.

Although I have to request that there is better error control for the camera - when SSL is not installed, it should say so, not just "Retry".

[robertsLando]

@larhedse most times ssl errors are just shown in chrome console but not accessible from js side, I should check if I'm able to reproduce this and fix