Announcement

Collapse
No announcement yet.

Jun 19 Insteon HUB update 1016 will break the plugin

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mworsnop
    replied
    if anyone finds out how to downgrade please post. thank you

    Leave a comment:


  • papapitufo
    replied
    I will try to downgrade and then will cancel Hub's access to internet to prevent upgrade again.

    Leave a comment:


  • mnsandler
    replied
    Guys, if we can't get in via a standard browser, i can't get in via the plugin

    i have an email into insteon for specifics on this change

    Leave a comment:


  • drcastro
    replied
    https attempts

    I am getting same results as Charles when I try to connect via https using browsers.

    Leave a comment:


  • charlesmbell
    replied
    Originally posted by charlesmbell View Post
    same errors as before with defaul https port
    mozilla provices the most detail on default 443 port

    An error occurred during a connection to 192.168.1.11. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP

    Leave a comment:


  • charlesmbell
    replied
    Originally posted by mnsandler View Post
    can anyone access the hub via a browser using

    https://x.x.x.x without a port number; this would assume the default 443
    same errors as before with defaul https port

    Leave a comment:


  • mworsnop
    replied

    Leave a comment:


  • mnsandler
    replied
    Originally posted by papapitufo View Post
    How can we downgrade to the Hub's previous firmware version?
    you will need to reach out to insteon for this answer

    please post back what you find

    Leave a comment:


  • mnsandler
    replied
    can anyone access the hub via a browser using

    https://x.x.x.x without a port number; this would assume the default 443

    Leave a comment:


  • papapitufo
    replied
    How can we downgrade to the Hub's previous firmware version?

    Leave a comment:


  • mworsnop
    replied
    I ran a port scan and 25105 and 443 are the only active ports

    Leave a comment:


  • charlesmbell
    replied
    Originally posted by mnsandler View Post
    please see post #9 above and try it and report back

    i wonder if the port number changed

    if so we need to figure that out and change in the plugin config page
    port number is same as before. i used the ios app to check the ip/settings, ect and you can set the port number there. it was still same

    Leave a comment:


  • mworsnop
    replied
    Tried in Chrome from a Mac
    Got this:

    sent an invalid response.
    ERR_SSL_PROTOCOL_ERROR

    Leave a comment:


  • charlesmbell
    replied
    Originally posted by mnsandler View Post
    my hub was offline so i didn't get the update;yet.


    can you check the url via a browser?

    https://x.x.x.x:25105

    replace x.x.x.x with your hub's ip

    you should get a login prompt
    so with https cannot connect.
    http shows:
    403 Forbidden: SSL Required - use HTTPS

    adding https://IP:25105

    on safari:
    safari cannot open page

    on mozilla:
    An error occurred during a connection to 192.168.1.11:25105. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    on chrome:
    192.168.1.11 sent an invalid response.
    ERR_SSL_PROTOCOL_ERROR

    Leave a comment:


  • mnsandler
    replied
    Originally posted by mworsnop View Post

    thanks for the updates Mark.


    I need to find a way to shut off the automatic updates! I added the extra Hub https section to the ini. I assume the ini is the one in the config directory? Still not working:


    Insteon Plug-in Error Log Generated 6/20/2018 07:13:26
    -----------*Error Message*----------------
    Error: Forced error / log generation -- 6/20/2018 07:13:26
    --------*Initialization Log*--------------
    6/20/2018 07:13:03 - Host System: 10.215.81.4 (House) 3.0.0.435
    6/20/2018 07:13:03 - Plugin HSPI_Insteon.exe version: 3.0.6.39
    6/20/2018 07:13:03 - Insteon Support library (Insteon.dll) version: 1.0.6.39
    6/20/2018 07:13:03 - RegisterCallback Completed
    6/20/2018 07:13:03 - Enter InitIO
    6/20/2018 07:13:03 - Enter InitPlugin
    6/20/2018 07:13:03 - Global initialization of plug-in required, starting up.
    6/20/2018 07:13:03 - Initializing Insteon hardware interface...
    6/20/2018 07:13:03 - In ProcessRawReceiveThread
    6/20/2018 07:13:03 - Initializing Interface...
    6/20/2018 07:13:03 - In PLMBuffer_ProcessBufferThread
    6/20/2018 07:13:03 - Sending https://10.215.81.130:25105/1?XB=M=1
    6/20/2018 07:13:03 - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    6/20/2018 07:13:04 - Sending https://10.215.81.130:25105/3?0260=I=3
    6/20/2018 07:13:05 - The underlying connection was closed: An unexpected error occurred on a send.
    6/20/2018 07:13:07 - ..did not receive a response from the Interface
    6/20/2018 07:13:07 - ..Retry #1 required. Pausing 250ms for Interface to clear...
    6/20/2018 07:13:07 - Sending https://10.215.81.130:25105/3?0260=I=3
    6/20/2018 07:13:07 - The underlying connection was closed: An unexpected error occurred on a send.
    6/20/2018 07:13:09 - The underlying connection was closed: An unexpected error occurred on a send.
    6/20/2018 07:13:10 - ..did not receive a response from the Interface
    6/20/2018 07:13:10 - ..Retry #2 required. Pausing 300ms for Interface to clear...
    6/20/2018 07:13:10 - Sending https://10.215.81.130:25105/3?0260=I=3
    6/20/2018 07:13:11 - The underlying connection was closed: An unexpected error occurred on a send.
    6/20/2018 07:13:13 - The underlying connection was closed: An unexpected error occurred on a send.
    6/20/2018 07:13:13 - ..did not receive a response from the Interface
    6/20/2018 07:13:13 - Insteon hardware interface initialization failed.
    6/20/2018 07:13:13 - Exit InitIO
    please see post #9 above and try it and report back

    i wonder if the port number changed

    if so we need to figure that out and change in the plugin config page

    Leave a comment:

Working...
X