Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted
3 minuty temu, jompa68 napisał:

Something changed at their side?

 

Rather not , because I have got location from time to time.

  • Topic Author
  • Posted
    49 minutes ago, jompa68 said:

    Yes it is Apple service problem. Something changed at their side?

     

    Service working again.

    Yes, it seems like it can have some issues. However, iOSLocator will continue and not crash I hope?

    Posted

    how can i include the return from my function to _myNodeRed(data)

     

    Please login or register to see this code.

     

  • Topic Author
  • Posted

    Please login or register to see this code.

    'log' takes the same formatting directives as string.format.

    There is also an instruction 'frm' that is like 'log' but doesn't log to the console.

    • Thanks 1
    Posted
    W dniu 2.03.2019 o 16:20, jgab napisał:

    Yes, it seems like it can have some issues. However, iOSLocator will continue and not crash I hope?

    Yeap, it looks resistant to a handshake :)

    Posted
    On 3/2/2019 at 4:20 PM, jgab said:

    Yes, it seems like it can have some issues. However, iOSLocator will continue and not crash I hope?

    I find that the Supervisor scene stops the iOSLocation scene after a while, right? If I stop Supervisor, iOSLocation will run all the time.

    Posted

    Little update.

    IOSLocator does not have any error when was ran from ZBS, working perfectly all the time, the HC2 causing it somehow

    Please login or register to see this code.

     

    Posted

    Missing Apple Root CA?

    Posted

    Same error when running IOSLocator:

     

    [DEBUG] 19:22:39: Posting {"type":"getIOSdevices","name":"Frank","pwd":"xxxxxxx","user":"[email protected]"} at Mon Mar 04 19:22:39

    [DEBUG] 19:24:09: Posting {"type":"poll","index":114} at Mon Mar 04 19:25:39
    [DEBUG] 19:25:40: 2019-03-04 19:25:40.020642 [ error] Handshake error: certificate verify failed
    [DEBUG] 19:25:40: 2019-03-04 19:25:40.021104 [ error] Handshake error: bad message type
    [DEBUG] 19:25:40: Posting {"type":"error","msg":"Failed calling FindMyiPhone service for [email protected]"} at Mon Mar 04 19:25:40
    [DEBUG] 19:25:40: Error Failed calling FindMyiPhone service for [email protected]

     

  • Topic Author
  • Posted

    Ok, something changed somewhere.

    The iCloud service uses https (which wasn't problem before). 

    However, I have pushed a version of iosLocator ("1.15","fix3") that adds the http request option 'checkCertificate=false'. Try it and see if it works for you.

     

    Posted

    Please login or register to see this code.

     

    Posted (edited)

     

    9 godzin temu, jgab napisał:

    Ok, something changed somewhere.

    The iCloud service uses https (which wasn't problem before). 

    However, I have pushed a version of iosLocator ("1.15","fix3") that adds the http request option 'checkCertificate=false'. Try it and see if it works for you.

     

    Nothing is working now, even earlier versions... 

    Edited by domin12
  • Topic Author
  • Posted (edited)
    14 minutes ago, domin12 said:

     

     

    Nothing is working now, even earlier versions... 

    Yes, I pushed a new fix ("1.15","fix4") and it started to work for me again. 

    (seems like apple reverted a change in the next stage step that they did last year)

     

    Edited by jgab
    Posted
    6 minut temu, jgab napisał:

    Yes, I pushed a new fix ("1.15","fix4") and it started to work for me again. 

    (seems like apple reverted a change in the next stage step that they did last year)

     

    [DEBUG] 07:50:32: Posting {"type":"poll","index":2} at Tue Mar 05 07:51:16

    [DEBUG] 07:50:33: NextStage

    [DEBUG] 07:50:33: 2019-03-05 07:50:33.003150 [ fatal] LUA error: /opt/fibaro/scenes/398.lua:95: attempt to concatenate local 'nextStage' (a nil value)

  • Topic Author
  • Posted
    10 minutes ago, domin12 said:

    [DEBUG] 07:50:32: Posting {"type":"poll","index":2} at Tue Mar 05 07:51:16

    [DEBUG] 07:50:33: NextStage

    [DEBUG] 07:50:33: 2019-03-05 07:50:33.003150 [ fatal] LUA error: /opt/fibaro/scenes/398.lua:95: attempt to concatenate local 'nextStage' (a nil value)

    Ok, so it started to work for me but it seems to vary for different people. 

    Normally Apple gives the url to the "next stage" server in the header ("x-apple-mme-host"), but it seems to be empty for you.

    Now I changed it to 

    Please login or register to see this code.

    so it reverts to the old address if the headers is not available. However that will probably not work from now on either, and you may go into an infinite next stage loop...

    I pushed a version that prints out the whole response when it goes into next stage (330). Can you try that and see what output you get?

    The debug line is on line 216.

    Posted
    4 minuty temu, jgab napisał:

    Ok, so it started to work for me but it seems to vary for different people. 

    Normally Apple gives the url to the "next stage" server in the header ("x-apple-mme-host"), but it seems to be empty for you.

    Now I changed it to 

    Please login or register to see this code.

    so it reverts to the old address if the headers is not available. However that will probably not work from now on either, and you may go into an infinite next stage loop...

    I pushed a version that prints out the whole response when it goes into next stage (330). Can you try that and see what output you get?

    The debug line is on line 216.

    Sure, I'm willing to help...

     

    [DEBUG] 08:10:20: Posting {"type":"poll","index":2} at Tue Mar 05 08:11:50

    [DEBUG] 08:10:21: 330 Resp:{"data":"","headers":{"Connection":"keep-alive","X-Responding-Partition":"p53","X-Apple-MMe-Host":"p53-fmipmobile.icloud.com","access-control-expose-headers":"X-Apple-Request-UUID, Via","Set-Cookie":"NSC_q53-gnjqtfswjdf=0933a3df17a919c0e3803f30d8bab46502071a570d8e9d95167c2b3b3cb510249667422e;path=\/;secure;httponly","X-Responding-Server":"pv43p53ic-zteg05093501_003","X-Responding-Instance":"fmipservice:45300303:pv43p53ic-zteg05093501:8003:1903B41:738abffa","Server":"AppleHttpServer\/70a91026","X-Apple-Request-UUID":"68d3aa12-7398-41c3-b951-cce370b4cf57","Date":"Tue, 05 Mar 2019 07:10:21 GMT","X-Apple-MMe-Scope":"1045830282","via":"icloudedge:br30p01ic-zteu01133001:7401:18RC846:Berlin","Content-Length":"0","Strict-Transport-Security":"max-age=31536000; includeSubDomains"},"status":330}

    [DEBUG] 08:10:21: NextStage

    [DEBUG] 08:10:23: iCloud Response:330

    [DEBUG] 08:10:23: Bad response from NextStage:{"data":"","headers":{"Connection":"keep-alive","X-Responding-Partition":"p53","X-Apple-MMe-Host":"p53-fmipmobile.icloud.com","access-control-expose-headers":"X-Apple-Request-UUID, Via","Set-Cookie":"NSC_q53-gnjqtfswjdf=5e4fa3cf2a7422f8c24817ce291bf49786f316b223080a987f57e8faa8ef8b47633a320a;path=\/;secure;httponly","X-Responding-Server":"pv43p53ic-zteg06083301_003","X-Responding-Instance":"fmipservice:45300403:pv43p53ic-zteg06083301:8003:1903B41:738abffa","Server":"AppleHttpServer\/70a91026","X-Apple-Request-UUID":"c591e9b0-07b5-4338-a84a-cab8464ee5c3","Date":"Tue, 05 Mar 2019 07:10:22 GMT","X-Apple-MMe-Scope":"1045830282","via":"icloudedge:br30p01ic-zteu03010201:7401:18RC846:Berlin","Content-Length":"0","Strict-Transport-Security":"max-age=31536000; includeSubDomains"},"status":330}

  • Topic Author
  • Posted
    1 minute ago, domin12 said:

    Sure, I'm willing to help...

     

    [DEBUG] 08:10:20: Posting {"type":"poll","index":2} at Tue Mar 05 08:11:50

    [DEBUG] 08:10:21: 330 Resp:{"data":"","headers":{"Connection":"keep-alive","X-Responding-Partition":"p53","X-Apple-MMe-Host":"p53-fmipmobile.icloud.com","access-control-expose-headers":"X-Apple-Request-UUID, Via","Set-Cookie":"NSC_q53-gnjqtfswjdf=0933a3df17a919c0e3803f30d8bab46502071a570d8e9d95167c2b3b3cb510249667422e;path=\/;secure;httponly","X-Responding-Server":"pv43p53ic-zteg05093501_003","X-Responding-Instance":"fmipservice:45300303:pv43p53ic-zteg05093501:8003:1903B41:738abffa","Server":"AppleHttpServer\/70a91026","X-Apple-Request-UUID":"68d3aa12-7398-41c3-b951-cce370b4cf57","Date":"Tue, 05 Mar 2019 07:10:21 GMT","X-Apple-MMe-Scope":"1045830282","via":"icloudedge:br30p01ic-zteu01133001:7401:18RC846:Berlin","Content-Length":"0","Strict-Transport-Security":"max-age=31536000; includeSubDomains"},"status":330}

    [DEBUG] 08:10:21: NextStage

    [DEBUG] 08:10:23: iCloud Response:330

    [DEBUG] 08:10:23: Bad response from NextStage:{"data":"","headers":{"Connection":"keep-alive","X-Responding-Partition":"p53","X-Apple-MMe-Host":"p53-fmipmobile.icloud.com","access-control-expose-headers":"X-Apple-Request-UUID, Via","Set-Cookie":"NSC_q53-gnjqtfswjdf=5e4fa3cf2a7422f8c24817ce291bf49786f316b223080a987f57e8faa8ef8b47633a320a;path=\/;secure;httponly","X-Responding-Server":"pv43p53ic-zteg06083301_003","X-Responding-Instance":"fmipservice:45300403:pv43p53ic-zteg06083301:8003:1903B41:738abffa","Server":"AppleHttpServer\/70a91026","X-Apple-Request-UUID":"c591e9b0-07b5-4338-a84a-cab8464ee5c3","Date":"Tue, 05 Mar 2019 07:10:22 GMT","X-Apple-MMe-Scope":"1045830282","via":"icloudedge:br30p01ic-zteu03010201:7401:18RC846:Berlin","Content-Length":"0","Strict-Transport-Security":"max-age=31536000; includeSubDomains"},"status":330}

    Interesting, your header is "X-Apple-MMe-Host"... and for me it is "x-apple-mme-host" -- why do they have different capitalisations ???

    Anyway, I pushed a new version ("1.15","fix6") and added both to the code and hope we don't see more variations :-)

    I commented out the debug line on line 216. If you continue to have problem, uncomment it and post what you get.

    Posted
    2 minuty temu, jgab napisał:

    Interesting, your header is "X-Apple-MMe-Host"... and for me it is "x-apple-mme-host" -- why do they have different capitalisations ???

    Anyway, I pushed a new version ("1.15","fix6") and added both to the code and hope we don't see more variations :-)

    I commented out the debug line on line 216. If you continue to have problem, uncomment it and post what you get.

    O yes, I see it now, strange, different localization, different servers..........

    But now, TADA!!! , is working , thanks for Your help

  • Topic Author
  • Posted
    Quote

    HTTP header names are case-insensitive, according to RFC 2616: 4.2: Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.

    So, it was my fault.

    I pushed yet another version that searches for the header in a case-insensitive way.

     

    Posted
    On ‎2‎/‎21‎/‎2019 at 12:01 PM, jgab said:

     

    @jgab need some help with IOSLocator.

    /F

    Output ZBS,   _deviceTable = "devicemap"

    Program starting as '"C:\Program Files (x86)\ZeroBraneStudio\bin\lua52.exe" -e "io.stdout:setvbuf('no')" "C:\Program Files (x86)\ZeroBraneStudio\myprograms\IOSLocator.lua"'.
    Program 'lua52.exe' started in 'C:\Program Files (x86)\ZeroBraneStudio\myprograms' (pid: 200800).
    C:\Program Files (x86)\ZeroBraneStudio\bin\lua52.exe: cannot open iOScredentials.lua: No such file or directory
    stack traceback:
        [C]: in function 'dofile'
        ...am Files (x86)\ZeroBraneStudio\myprograms\IOSLocator.lua:49: in main chunk
        [C]: in ?
    Program completed in 0.12 seconds (pid: 200800).

     

    Output HC2,   _deviceTable = "HomeTable"

    [DEBUG] 10:48:32: iOSLocator - EventRunner v1.15
    [DEBUG] 10:48:32: Starting iOSLocator service
    [DEBUG] 10:48:32: Fibaro software version: 4.532
    [DEBUG] 10:48:32: HC2 uptime: 90 hours
    [DEBUG] 10:48:32: Sunrise 06:54, Sunset 17:51
    [DEBUG] 10:48:32: 
    [DEBUG] 10:48:32: Loading rules
    [DEBUG] 10:48:32: 
    [DEBUG] 10:48:32: Scene running
    [DEBUG] 10:48:33: fibaro:start(317,["{\"type\":\"%%ANNOUNCE%%\",\"_from\":343}"])
    [DEBUG] 10:48:33: fibaro:start(342,["{\"type\":\"%%ANNOUNCE%%\",\"_from\":343}"])
    [DEBUG] 10:48:33: fibaro:start(345,["{\"type\":\"%%ANNOUNCE%%\",\"_from\":343}"])
    [DEBUG] 10:48:33: Posting {"type":"readConfig"} at Tue Mar 05 10:48:33
    [DEBUG] 10:48:33: Posting {"type":"poll","index":1} at Tue Mar 05 10:48:33
    [DEBUG] 10:48:34: Error in ' Event.event({"type":"readConfig"},...)': /opt/fibaro/scenes/343.lua:136: attempt to index local 'v' (a number value)
    [DEBUG] 10:48:34: Error in ' Event.event({"type":"poll"},...)': /opt/fibaro/scenes/343.lua:287: attempt to index local 'user' (a nil value)
    [DEBUG] 10:48:34: Error in ' Event.event({"type":"error"},...)': /opt/fibaro/scenes/343.lua:294: Bad _Msg:Error %s
     

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...