Announcement

Collapse
No announcement yet.

Looking for a way to make more than one connection

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Looking for a way to make more than one connection

    Hi Spud,
    Your plugin work beautifully since a several month now. Great work.

    Like every human it's never enough...

    I looking for a way to add an Android client. I guess that you already know DSC server android apps.
    https://play.google.com/store/apps/d...d.server&hl=fr

    There is a server and a standalone client which is free on local network.
    Documentation on DSC server said;
    The envisalink card only supports one connection at a time. To support multiple phone/tablet connections simultaneously you need the DscServer android app to work as a proxy for the envisalink card. See DscServer for more details.

    Only one connection at a time. No choice. So...
    Did you try your plugin via this kind of setup?
    Personally I prefer your installation but if I can get both to work I'll be happy.
    Also if I go to this way I'll be in the obligation to have an android unit online all the time. Not a really welcome situation since I already have a window server for homeseer.

    What I'm trying to do is to make the DSC keypad for Android to work again like before;
    https://play.google.com/store/apps/d....android&hl=fr

    I know I can make something similar with HSTouch but I'll have to put time on an interface.
    Thanks for reading.

  • #2
    I didn't know about the DscServer app
    Have you tried it? If it works as advertised, my plugin should be able to work using this DscServer as a proxy.

    There is a standalone java version that you could probably run on your HS machine: https://sites.google.com/site/mppsui...ds/dscserver-2
    I will give it a try later.

    But as you said the best solution may be to build a screen for HSTouch

    Comment


    • #3
      Thank for your advice,
      I'll go with the HS touch solution on spare time.
      Winter is coming and with it... spare time.
      The idea will be to create a virtual keyboard.
      I already tried the java version of DSC server without success.

      Your plugin work so good that I want to do anything possible to keep it.

      Comment


      • #4
        Just a little update,

        Right now I'm running your plugin with the DSC server java app on the same machine.
        Using it as a proxy to plug more than one connection on envisalink.
        Look OK
        127.0.0.1 is the IP address in the config setup for your plugin. I didn't use localhost to eliminate more problem. It's the only thing I change from before.
        Only a warning;
        EnvisaLink WARNING Wrong command size detected. Data = 9082.1.7 B7
        But even with this warning it's working great for now. Probably not important.
        Port use 49168 on 127.0.0.1 for your plugin
        The Android DscKeypad app is working also now, port use 48749 on a wifi connection over a local network.
        Event are still working OK and status also.
        I don't think I'll keep the solution for ever but for testing and learning it's interesting.
        The Java app doesn't seem reliable like your plugin alone. Maybe more a question of feeling from my part. Always scary when I don't understand completely my setup.
        So let's see my humble conclusion in the next weeks.
        Amazing right now.
        Have a good day

        Comment


        • #5
          thanks for the update.

          if you want me to look into this warning, I would need the full debug logs to know exactly when it happens.

          Comment


          • #6
            Dear Spud
            It's up to you.
            Here, everything is working fine.
            If I look on the DscServer java website they said in the history;
            DscServer 2.1.7
            - some Events/Actions were not being saved properly (please check your event settings to make sure all you need is still there)

            So it maybe related to something else and not your plugin.
            Don't put to much time on that. As I wrote it work.
            Here the debug;
            8/13/2014
            Aug-13 11:29:44 EnvisaLink INFO EnvisaLink version 3.0.0.14
            Aug-13 11:29:45 EnvisaLink DEBUG Partition Device Found: P:1
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:3
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:4
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:5
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:6
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:7
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:8
            Aug-13 11:29:45 EnvisaLink DEBUG Zone Device Found: Z:9
            Aug-13 11:29:46 EnvisaLink DEBUG Zone Device Found: Z:1
            Aug-13 11:29:46 EnvisaLink DEBUG Zone Device Found: Z:2
            Aug-13 11:29:46 EnvisaLink DEBUG Request: NetworkLogin XXXXX
            Aug-13 11:29:46 EnvisaLink DEBUG Request: TimeStampControl 1
            Aug-13 11:29:46 EnvisaLink DEBUG Request: StatusReport
            Aug-13 11:29:46 EnvisaLink DEBUG Request: Poll
            Aug-13 11:29:46 EnvisaLink DEBUG LoginInteraction 3
            Aug-13 11:29:46 EnvisaLink DEBUG LoginInteraction 1
            Aug-13 11:29:46 EnvisaLink DEBUG CommandAcknowledge 055
            Aug-13 11:29:46 EnvisaLink DEBUG CommandAcknowledge 001
            Aug-13 11:29:46 EnvisaLink WARNING Wrong command size detected. Data = 9082.1.7 B7
            Aug-13 11:29:46 EnvisaLink DEBUG CommandUnknown
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 001
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 002
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 003
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 004
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 005
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 006
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 007
            Aug-13 11:29:46 EnvisaLink DEBUG ZoneRestored 008
            Aug-13 11:29:46 EnvisaLink DEBUG PartitionReady 1
            Aug-13 11:29:46 EnvisaLink DEBUG TroubleLedoff 1
            Aug-13 11:29:46 EnvisaLink DEBUG VerboseTroubleStatus 00
            Aug-13 11:29:46 EnvisaLink DEBUG ChimeEnabled 1
            Aug-13 11:29:46 EnvisaLink DEBUG KeypadLedStatePartition1Only 81
            Aug-13 11:29:46 EnvisaLink DEBUG CommandAcknowledge 000
            Aug-13 11:30:12 EnvisaLink DEBUG Could not parse time from data = 550113208131492
            Aug-13 11:30:12 EnvisaLink DEBUG TimeDateBroadcast 1132081314
            Aug-13 11:31:46 EnvisaLink DEBUG Request: Poll
            Aug-13 11:31:46 EnvisaLink DEBUG CommandAcknowledge 000
            Aug-13 11:33:46 EnvisaLink DEBUG Request: Poll
            Aug-13 11:33:46 EnvisaLink DEBUG CommandAcknowledge 000

            Comment


            • #7
              Just a little update to tell you that after nearly a week the system is stable and all events works good.
              So for me this is a reliable solution so far.
              Android plugin, multiple connection and homeseer all at the same time with a free java script.
              Working good
              The only thing I change from my original home seer setup was the IP address in the Spud envisalink plugin.
              Now it's 127.0.0.1
              That's it nothing more

              Comment


              • #8
                good to know
                thank you for reporting

                Comment


                • #9
                  Hi Spud,
                  System is quite reliable for my last post (2 month). Nothing to complaint.
                  I'm still on the java server. Great. Android device via this kind of gateway.
                  Really great. Wifi access for my DSC system.
                  2 android device with secure access. Can be configure for Internet access via router port.
                  Everything work great.
                  Cool.

                  I test the PGM output new feature. Working good as it's supposed to be but not for my purpose.

                  A warning at boot. If you can just point what's that mean for a mortal like me.
                  Mostly curiosity, here. ;-)
                  EnvisaLink WARNING Wrong command size detected. Data = 9082.1.7 B7


                  I put the whole debug here;

                  10/5/2014
                  Oct-05 11:08:38 EnvisaLink INFO EnvisaLink version 3.0.0.14
                  Oct-05 11:08:40 EnvisaLink DEBUG Partition Device Found: P:1
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:3
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:4
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:5
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:6
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:7
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:8
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:9
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:1
                  Oct-05 11:08:40 EnvisaLink DEBUG Zone Device Found: Z:2
                  Oct-05 11:08:40 EnvisaLink DEBUG Request: NetworkLogin xxxxx
                  Oct-05 11:08:40 EnvisaLink DEBUG Request: TimeStampControl 1
                  Oct-05 11:08:40 EnvisaLink DEBUG Request: StatusReport
                  Oct-05 11:08:40 EnvisaLink DEBUG LoginInteraction 3
                  Oct-05 11:08:40 EnvisaLink DEBUG Request: Poll
                  Oct-05 11:08:41 EnvisaLink DEBUG LoginInteraction 1
                  Oct-05 11:08:41 EnvisaLink DEBUG CommandAcknowledge 055
                  Oct-05 11:08:41 EnvisaLink DEBUG CommandAcknowledge 001

                  Oct-05 11:08:41 EnvisaLink WARNING Wrong command size detected. Data = 9082.1.7 B7

                  Oct-05 11:08:41 EnvisaLink DEBUG CommandUnknown
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 001
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 002
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 003
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 004
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 005
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 006
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 007
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 008
                  Oct-05 11:08:41 EnvisaLink DEBUG ZoneRestored 009
                  Oct-05 11:08:41 EnvisaLink DEBUG PartitionReady 1
                  Oct-05 11:08:41 EnvisaLink DEBUG TroubleLedoff 1
                  Oct-05 11:08:41 EnvisaLink DEBUG VerboseTroubleStatus 00
                  Oct-05 11:08:41 EnvisaLink DEBUG ChimeEnabled 1
                  Oct-05 11:08:41 EnvisaLink DEBUG KeypadLedStatePartition1Only 81
                  Oct-05 11:08:41 EnvisaLink DEBUG CommandAcknowledge 000
                  Oct-05 11:10:41 EnvisaLink DEBUG Request: Poll
                  Oct-05 11:10:41 EnvisaLink DEBUG CommandAcknowledge 000
                  Oct-05 11:12:12 EnvisaLink DEBUG Could not parse time from data = 55011121005148A
                  Oct-05 11:12:12 EnvisaLink DEBUG TimeDateBroadcast 1112100514
                  Oct-05 11:12:41 EnvisaLink DEBUG Request: Poll
                  Oct-05 11:12:41 EnvisaLink DEBUG CommandAcknowledge 000
                  42 log entries, displaying entries from 0

                  Comment


                  • #10
                    it looks like the java server sends a non standard command (908) which I guess is the version number of the server 2.1.7.

                    as it is a non standard command the plugin doesn't understand it and try to parse it as something else, hence the warning

                    Comment


                    • #11

                      Comment


                      • #12
                        another user tested the java server version 2.1.12 with this plugin and could not make it work, see this thread: http://board.homeseer.com/showthread.php?t=170652

                        so I made a fix for his problem in version 3.0.0.16, that might interest you

                        Comment


                        • #13
                          Hi Spud,
                          I personally rollback to the version 2.1.7 B7 of the java server because it's really really really reliable.
                          Since I got a strange warning with the new version 2.1.12 I prefer to stay with a working configuration.
                          Like I wrote before it's reliable like a rock.
                          Everything works great.
                          I can test stuff for you if you want to help you but on my side it's a hit, more an home run.
                          Personally I got no problem with the 908 warning as long as it's not important for a workable configuration. Never got a connection problem.
                          "I put my old java server version 2.1.7 as an attachment for future use. Maybe somebody can find it useful." Mike P ask me to remove it. Sorry
                          Configuration;

                          DSC alarm control panel PC1832 with envisalink card
                          Windows 7 32 bits
                          Homeseer v3
                          DSC java server v 2.1.7
                          DSC Spud Plugin v 3.0.0.14

                          because of some reliability problem with my CM11a X10 interface I switch to the CM15a USB controller. Seems a bit better. I'll see with more time.

                          This is solid and reliable.

                          I never had big issue with this configuration but with the other java server version 2.1.12 I got several unidentified issue. So i rollback really fast instead of digging.
                          Last edited by tomtomtom; February 14th, 2015, 09:02 AM. Reason: Asked by MikeP

                          Comment


                          • #14
                            Hi, I'm the author of the java DscServer, and I've just come across this thread. Sorry for being late to the party.

                            I'm happy that it's working here, and yes, event 908 is an extension I've added to the envisalink protocol to report the server version to the DscKeypad android client. There are a few more extra events that I'd be glad to help get sorted if you need - most notable is the label event that will report the zone and partition labels that have been set on the DscServer.

                            I would ask that you delete the copy of the DscServer file in the previous post and instead point anyone interested to my web site https://sites.google.com/site/mppsui...ds/dscserver-2 to get the latest version.

                            If there are any feature requests I would be happy to consider them (with the caveat that the DscServer is part of a paid android application from https://play.google.com/store/apps/d...android.server, so in general my focus is there).

                            Mike

                            Comment


                            • #15
                              Hi reader,
                              I don't want to revive this old topic but for those who try to make this work.
                              Still working great with my configuration.
                              I upgraded to DSC Security, version: 3.0.0.34 and everything is stable. Better handling of the intermittent warning problem. Very rare but no problem now.
                              Test are good with Java server 2.1.7 and new Homeseer version.
                              As wrote in the previous post you can add label for zone in the menu, system, zone and the DSC plugin can read them easily and it's upgraded during installation of the plugin. Partition and zone name work also perfectly.
                              Have a good day everybody.
                              For me, homeseer is useless without the spud plugin.
                              Great work.

                              Comment

                              Working...
                              X