Announcement

Collapse
No announcement yet.

Bump - Sort of - Had asked this prior

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

    Bump - Sort of - Had asked this prior

    The current version of UltraRussound in the updater does not work with my system. I have reason to believe that the last update posted (before the current one) would work.
    Russound cannot read keypads.
    HSPI_ULTRARUSSOUNDAUDIO3_DEBUG.zip
    Assistance, hints?
    3.0.6140.33174
    Gracias!
    Last edited by Monk; May 8, 2017, 05:26 PM.

    #2
    HS3 ready for prime time - maybe? hard to tell cause things already do not work.

    So hope I get some assistance soon.
    This is my first venture into HS3 from a perfectly working HS2 and there isn't too many weeks to get it done.
    Starting with the biggest deal breakers, one at a time, moving off HS2 and get stopped before I can even start.
    Not that the entire HS3 ecosystem depends on my $ but I've waited this long and was really really hoping everything was just going to work!

    No one successfully using this plugin? If I can just get past this!!

    Comment


      #3
      Sorry, I have been unable to respond sooner. You're starting you have an issue with your keypad presses not being reflected in HomeSeer? Can you provide a brief summary of how you have your Russound connected (if more than 2) and provide the keypad number (and which Russound it's connected to) along with what button press is not working so I can try to duplicate here.

      Regards,
      Ultrajones
      Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

      Comment


        #4
        Thanks Ultra.
        Single CAV6.6 Keypad 2, (or Any)
        Power on is not reflected, nor any other keypress.

        Connecting to the CAV via Edgeport USB / Serial converter.
        OK - So I just reset power & moved the russound to the HS3 system.
        At first, it looked like it worked. Physical Zone one power on - HS device power shows on.

        Then the zone shut down by itself. UltraRussound thinks it is still on.
        this is in the log.

        Warning <table class="log_table_row" cellspacing="0"><tbody><tr><td class="LogType0" colspan="3" align="left">
        </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr></tbody></table>

        Comment


          #5
          Now, testing - Keypads 3 & 5.
          Physical keypads on, plugin is not aware.
          Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	95.5 KB
ID:	1190874

          Comment


            #6
            This is the same behavior if switch over to a Quatech network converter.

            I can send commands just fine but it cannot read the status.

            Comment


              #7
              Debug log is attached in first message
              Note - Configuration was way different during the debug log but really same symptom.
              Last edited by Monk; May 13, 2017, 03:34 PM.

              Comment


                #8
                Bump

                Comment


                  #9
                  Please assist

                  I have built a new HS machine for HS3.
                  Fresh HS3 install & register.
                  Yours is the only plug-in installed.
                  One CAV6.6, freshly factory reset.
                  Connect via Quatech, or EdgePort serial converter.
                  It has the same issues.
                  Please Assist.

                  Comment


                    #10
                    Broken - direct to MB serial port

                    So - I went and bought a Serial extender and plugged it into the header on my motherboard. Now I have a local old-school serial port mounted in the rear of the newly built PC.

                    Plugging the Russound directly into the built-in serial port has the exact same problem as using the Edgeport, etc.

                    As noted in post 1 - I think the last update broke this.

                    Comment


                      #11
                      I blew the dust off of my keypad today and tested this Every key press was properly registered in the HomeSeer devices. In addition, when my tuner was turned to an FM station, the keypad display device displayed the station Id. What is the address of the controller you have connected to your HomeSeer system? Can you confirm it's set to 01?

                      Regards,
                      Ultrajones
                      Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                      Comment


                        #12
                        Originally posted by Ultrajones View Post
                        I blew the dust off of my keypad today and tested this Every key press was properly registered in the HomeSeer devices. In addition, when my tuner was turned to an FM station, the keypad display device displayed the station Id. What is the address of the controller you have connected to your HomeSeer system? Can you confirm it's set to 01?

                        Regards,
                        Ultrajones
                        Yes, factory reset and # 1.

                        Comment


                          #13
                          Note that I do not have all devices set as Homeseer devices. To keep it simple, just Power for each zone.

                          Comment


                            #14
                            Just turned on zone 6 via Keypad.
                            Homeseer reflects correctly that the power turned on.
                            Next, Turned on Zone 1 via Keypad.
                            Homeseer reflects Zone 1 is on.
                            Next - Power off zone 1 via Keypad.
                            Homeseer still thinks it is powered on. The change is not recognized.

                            These appear in log. -
                            May-25 7:28:54 PM <table class="log_table_row" cellspacing="0"><tbody><tr><td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left">
                            </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime0" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:28:30 PM </td><td class="LogPri0" colspan="1" align="left">
                            </td><td class="LogType0" colspan="3" align="left"> Warning </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:28:21 PM </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime0" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:28:21 PM </td><td class="LogPri0" colspan="1" align="left">
                            </td><td class="LogType0" colspan="3" align="left"> Warning </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:28:21 PM </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime0" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:28:20 PM </td><td class="LogPri0" colspan="1" align="left">
                            </td><td class="LogType0" colspan="3" align="left"> Warning </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:26:50 PM </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime0" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:26:41 PM </td><td class="LogPri0" colspan="1" align="left">
                            </td><td class="LogType0" colspan="3" align="left"> Warning </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:26:41 PM </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime0" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:26:40 PM </td><td class="LogPri0" colspan="1" align="left">
                            </td><td class="LogType0" colspan="3" align="left"> Warning </td><td class="LogEntry0" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr> </tbody></table> <table class="log_table_row" cellspacing="0"><tbody><tr> <td class="LogDateLong LogDateTime1" colspan="1" style=" white-space: nowrap;" align="left"> May-25 7:26:40 PM </td><td class="LogPri1" colspan="1" align="left">
                            </td><td class="LogType1" colspan="3" align="left"> Warning </td><td class="LogEntry1" colspan="8" align="left"> Device address Russound1.0.0-audiozone-keypad-display cannot be found. </td></tr></tbody></table>

                            Comment


                              #15
                              Serial

                              I have never considered serial # - I recall it might have been enforced early on - but starting new, nothing seemed to care - here is my setup in settings -
                              Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	14.1 KB
ID:	1190965

                              Comment

                              Working...
                              X