Multiple NRF24L01+ gateways



  • @skywatch can you please email the error log?
    and paste a screenshot of the node page.

    How do I know which GW has id5?

    On the node page gateway, details will be.
    also on the gateway detail page, you can click node count to get all the nodes listed under the gateway



  • @jkandasa Thank you - I have sent log as attachment to email. 🙂



  • @skywatch Thanks for the logs. Can you edit and save again gateway2 and see the behavior?



  • @jkandasa said in Multiple NRF24L01+ gateways:

    @skywatch Thanks for the logs. Can you edit and save again gateway2 and see the behavior?

    I have done as you say. I'll keep an eye on it and see how things go. Thanks! 🙂

    But just to be clear, GW2 is the MQTT GW for McAgent, the errors in the log were all GW5 related though?



  • @skywatch I said gateway2 just like that. Please edit and save the gateway have issue.



  • @jkandasa I'll let it run overnight and see how it is in the morning.



  • @jkandasa Here is the overnight log. It still shows some errors?

    [Tue Apr 07 17:35:26 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake in processing a request from /196.52.43.123:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 19:25:50 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate in processing a request from /192.168.1.64:8443 / sun.security.ssl.SSLSocketImpl
    2020-04-07 19:36:57,955 INFO [mc-th-pool-2] [org.mycontroller.standalone.email.EmailUtils:58] EmailSettings(smtpHost=relay.plus.net, smtpPort=25, fromAddress=skywatch@skywatch.plus.com, enableSsl=true, useStartTLS=false, smtpUsername=skywatch@skywatch.plus.com)
    [Tue Apr 07 19:51:45 BST 2020] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate in processing a request from /192.168.1.64:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:58 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:58 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:58 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:22:59 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:24:47 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:01 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:05 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:06 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:17 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:17 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:25 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:25:47 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    [Tue Apr 07 22:26:17 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown in processing a request from /192.168.1.80:8443 / sun.security.ssl.SSLSocketImpl
    2020-04-07 22:48:09,010 WARN [Quartz_Scheduler_Worker-4] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
    2020-04-08 00:12:14,005 WARN [Quartz_Scheduler_Worker-2] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
    [Wed Apr 08 01:03:02 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? in processing a request from /79.124.62.94:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 02:39:32 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake in processing a request from /162.243.130.175:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 02:42:46 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Received close_notify during handshake in processing a request from /89.40.73.240:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 03:14:30 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? in processing a request from /79.124.62.94:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 03:35:43 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Connection reset in processing a request from /198.108.67.48:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 03:35:43 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? in processing a request from /198.108.67.48:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 03:35:45 BST 2020] IO error: java.net.SocketException: Connection reset in processing a request from /198.108.67.48:8443 / sun.security.ssl.SSLSocketImpl
    [Wed Apr 08 08:22:18 BST 2020] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate in processing a request from /192.168.1.64:8443 / sun.security.ssl.SSLSocketImpl
    


  • @skywatch The error shown here is not related to the issue you are facing. This is error is not harmful.



  • @jkandasa Thank you! - Then all seems well now! - I still get one repeating item in the log, but it doesn't appear to cause an issue so I am not too worried about it!

    Thanks for the help resolving this! 🙂



  • @jkandasa It has happened again. I will post what I see later on toady.....



  • @jkandasa Initially I thought this was the gateway crashing, now I am not so sure about that. Earlier this week MyC was showing all nodes from one GW as down, the other GW was still working as was McA. I replugged the GW into the pi USB port and it all started working again.

    Yesterday I noticed no automation and upon checking again had all nodes down (this time on both GW's). So I edited ALL GW configurations (as you advised above) and still nothing. After a few shutdown/poweron cycles it finally started working again - but only for half an hour when it all broke again.

    From the below photo you can see that MyC sees the GW is 'UP' and running normally......

    gateway.jpg

    Then,clicking on the nodes info we see that all are down....

    nodes.jpg

    This is unexpected as MyC can see and report the messages from the nodes via the GW.

    The log file is similar to the last one I sent you with a lot of garbage messages like this.....

    log.jpg

    So as far as I can see there is an issue, but not with the GW as I thought as it still works as far as MyC is seeing the data. So the question is what is going on here?

    I am puzzled by this situation!

    UPDATE - Even stranger now!!!!

    So this morning all the nodes on GW were showing as 'down' with the GW showing up. Last seen on the nodes was 12 hours ago.
    Just out of curiosity I tried sending a LED lights on and it worked! So did LED lights off and then on again! - Yet only those messages showed up for the node in sensors action and still the node shows as 'down' for 12 hours. I guess that this is due to one way communication of the lights messages.

    NOw I notice that when a IR command is sent it is wotking as expected but no message shows up in 'sensors action' ????



  • @skywatch Sorry for the delayed response.

    It is odd. I could not guess the real issue.
    Can you please change the serial driver from Auto to jSerialComm and check the status?



  • @jkandasa said in Multiple NRF24L01+ gateways:

    @skywatch Sorry for the delayed response.

    Me too! 😉

    Well I have done more on this to see what might be happening and it seems that my last hope (that each gw needed it's own node id) was barking up the wrong tree.

    So how does mycontroller differentiate between gateways if both are having node id 0?

    I also removed that 3.3v 8MHz promini GW and replaced with a 5V one. Now both GW have the same serial speed (115200) in case that was an issue.

    I need to reflash one GW and will make another soon so that both are identical as far as is possible.

    We never stop learning (unless we choose not to and that would be an awful pity)!



  • @skywatch

    So how does mycontroller differentiate between gateways if both are having node id 0?

    Internally it keeps a unique id for each gateway. Quick view:
    alt text

    You have to maintain a unique node id inside a gateway only.
    So each gateway can have the same node id.



  • @jkandasa That clears up my confusion on that, almost.... 😉

    So why do I see both GW in resources->gateways, but only one shows in resources->nodes? I can't figure out what is going on here......



  • @skywatch click on the gateway details page. there check how many nodes available for that gateway.


Log in to reply
 

Suggested Topics

7
Online

562
Users

456
Topics

2.8k
Posts