Announcement

Collapse
No announcement yet.

HS4 Beta 4.1.100.0 (4.2 Beta) is available

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

    #91
    Originally posted by MattL0 View Post

    Compiled the check_passwd program on linux with a 2700x amd cpu
    Hi Matt,

    Thanks, much appreciated. This resolved the issue.

    rjh Can you make this part of the setup or add it to the Linux installation instruction?

    ----
    John

    Comment


      #92
      Originally posted by spud View Post

      I reproduced the problem using your plugin, and there are 2 issues:

      (1) you need to add "/" to your url post requests so that they are posted to http://xx../Sonos4/sonos-init.html

      (2) it seems that you call UnregisterFeaturePage just after the user clicks the accept button in the first step, so that all the subsequent posts fail because the page is no longer registered. The page needs to stay registered as long as it is used

      It was working with v.18 because this version was more forgiving and all posts were passed to plugins even if the pages were not registered, this is no longer the case.
      Ah excellent, I'll check the code, I know I unregister but wasn't aware I do it too early.
      Thanks!

      Comment


        #93
        spud
        Thanks for the pointer on unregistering, that was the mistake.

        rjh

        I see we have moved the html for grid view in a separate html file (devices_grid_media.html). Did we lose the fixes we had in v.18?

        code in v100 (note the wrong device_sub_type should be 1 instead of 14. 14 = art)

        <div class="row">
        <div class="col">
        <!--by default the primary device is set to the albumart feature device-->
        <div id='stimgprim_{{d.primary_ref}}'><img src='{{ status_image_file d.primary_ref }}' width='80' height='80'></div>
        </div>
        <div class="col">
        <!--playerstatus feature device holds what is playing-->
        {{ for c in d.children }}
        {{if c.device_sub_type==14}}
        <!--playerstatus-->
        {{c.status_short}}
        {{end}}
        {{end}}
        </div>
        </div>

        code in v.18
        <!--media device-->
        <div class="row">
        <div class="col">
        <!--by default the primary device is set to the albumart feature device-->
        <div id='stimgprim_{{d.primary_ref}}'><img src='{{ status_image_file d.primary_ref }}' width='80' height='80'></div>
        </div>
        <div class="col">
        <!--playerstatus feature device holds what is playing-->
        {{ for c in d.children }}
        {{if c.device_sub_type==1}}
        <!--playerstatus-->
        <div id='media_status_{{c.ref}}'>
        {{c.status_short}}
        </div>
        {{end}}
        {{end}}
        </div>
        </div>

        Moreover, it seems that the primary reference in v100 is ???? while it was showing art in v.18. I did make art the primary feature but seems to make no difference.

        Last but not least, the volume control doesn't seem to (ajax) update when changed outside the UI.

        Thoughts? What about the layout improvements we conversed about once a year ?

        edit: another issue: if you have a _MuteToggle control, the UI does not update the graphic from mute to unmute

        Comment


          #94
          spud

          Next problem with GET & POST in v100.

          For each player the PI discovers, it registers a weblink pointing to the same html file (sonos-player.html) but the link is registered with an additional parameter, indicating which player it applies to.

          example weblink url: Sonos4/sonos-player.html?deviceudn=RINCON_48A6B8B4D8A101400. The parameter deviceudn is different for each weblink associate with its respective player.

          In v18 an Ajax (Post) was done to Sonos4/sonos-player.html and all was OK. In V100 this results again in a 404 error. When I add the parameter to the POST (ie /Sonos4/sonos-player.html?deviceudn=RINCON_48A6B8B4D8A101400) I still get an error 404.

          Advice?

          Comment


            #95
            In v100 it seems not possible hiding only the root device from views. When un-checking it, all of the child devices are also hidden. The child devices can not be shown separate.
            When looking in the feature tab all the devices have the display type marked as 'normal' still they do not show up on the list.


            Click image for larger version

Name:	Snag_603a664.png
Views:	284
Size:	163.8 KB
ID:	1488307


            Comment


              #96
              For the standard Linux build I will include an x86 executable. This will work for most. However, if someone tries to run this on an ARM version of Linux it will not work. I will just have to note that for now.

              Originally posted by John245 View Post

              Hi Matt,

              Thanks, much appreciated. This resolved the issue.

              rjh Can you make this part of the setup or add it to the Linux installation instruction?

              ----
              John
              💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

              Comment


                #97
                It looks like maybe some changes may have been lost when we split out the grid display to separate files. I will check. I did notice that the updates were not working properly, looking into that.

                Originally posted by dcorsus View Post
                spud
                Thanks for the pointer on unregistering, that was the mistake.

                rjh

                I see we have moved the html for grid view in a separate html file (devices_grid_media.html). Did we lose the fixes we had in v.18?

                code in v100 (note the wrong device_sub_type should be 1 instead of 14. 14 = art)

                <div class="row">
                <div class="col">
                <!--by default the primary device is set to the albumart feature device-->
                <div id='stimgprim_{{d.primary_ref}}'><img src='{{ status_image_file d.primary_ref }}' width='80' height='80'></div>
                </div>
                <div class="col">
                <!--playerstatus feature device holds what is playing-->
                {{ for c in d.children }}
                {{if c.device_sub_type==14}}
                <!--playerstatus-->
                {{c.status_short}}
                {{end}}
                {{end}}
                </div>
                </div>

                code in v.18
                <!--media device-->
                <div class="row">
                <div class="col">
                <!--by default the primary device is set to the albumart feature device-->
                <div id='stimgprim_{{d.primary_ref}}'><img src='{{ status_image_file d.primary_ref }}' width='80' height='80'></div>
                </div>
                <div class="col">
                <!--playerstatus feature device holds what is playing-->
                {{ for c in d.children }}
                {{if c.device_sub_type==1}}
                <!--playerstatus-->
                <div id='media_status_{{c.ref}}'>
                {{c.status_short}}
                </div>
                {{end}}
                {{end}}
                </div>
                </div>

                Moreover, it seems that the primary reference in v100 is ???? while it was showing art in v.18. I did make art the primary feature but seems to make no difference.

                Last but not least, the volume control doesn't seem to (ajax) update when changed outside the UI.

                Thoughts? What about the layout improvements we conversed about once a year ?

                edit: another issue: if you have a _MuteToggle control, the UI does not update the graphic from mute to unmute
                💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                Comment


                  #98
                  Originally posted by zwolfpack View Post

                  In the past, this setting was effective only with myhs disabled as well.

                  I have a script to test the purge time (insert ten bogus entries into the table, then poll every 60 seconds until all he added entries disappear). Just now, all ten entries disappeared right about the twenty minute mark.
                  rjh
                  It is working as zwolfpack desribes. This means that the MyHS Service should also be disabled. If this is the intention please add the explanation.

                  In case it was the intention that the system will not be discoverable by enabling the checkbox for " Prevent the find.homeseer.com service from finding your system" please fix the bug.

                  ---
                  John
                  ​​​​​​​

                  Comment


                    #99
                    I checked the code, and yes, you need to have MyHS disabled also. The reason is that both find and MyHS need to know your WAN IP address. So if you disable find, that disables the check for your WAN IP and MyHS will not work. I will just combine those settings into one.

                    Originally posted by John245 View Post

                    rjh
                    It is working as zwolfpack desribes. This means that the MyHS Service should also be disabled. If this is the intention please add the explanation.

                    In case it was the intention that the system will not be discoverable by enabling the checkbox for " Prevent the find.homeseer.com service from finding your system" please fix the bug.

                    ---
                    John
                    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                    Comment


                      Originally posted by rjh View Post
                      For the standard Linux build I will include an x86 executable. This will work for most. However, if someone tries to run this on an ARM version of Linux it will not work. I will just have to note that for now.
                      How about making check_passwd a redirecting script, then include both executables as check_passwd_arm and check_passwd_x86?

                      check_passwd (redirecting script)
                      Code:
                      #!/bin/sh
                      
                      d=$(dirname $0)
                      case $(uname -m) in
                        arm* )
                          exec $d/check_passwd_arm $@
                          ;;
                        * )
                          exec $d/check_passwd_x86 $@
                          ;;
                      esac
                      Alternately, this perl script does the whole thing for either architecture.
                      Code:
                      #!/usr/bin/perl
                      # check_passwd - HS-linux tool script
                      # supports: TOOLS->System->Linux Tools, TOOLS->System->Change System Password
                      # login password validation
                      # usage: check_passwd username password
                      # returns 0 if valid username/password provided; 1 otherwise
                      
                      use strict;
                      use warnings;
                      use English;
                      
                      die "$0: must be superuser!\n" if $UID;
                      
                      my $username = shift;
                      my $passwd = shift;
                      die "usage: $0 username password\n" unless defined $passwd;
                      
                      my (undef, $crypt) = getpwnam($username);
                      die "$0: invalid username '$username'\n" unless $crypt;
                      exit not crypt($passwd, $crypt) eq $crypt;

                      Comment


                        +1 for the Perl script !!

                        Comment


                          Originally posted by dcorsus View Post
                          spud

                          Next problem with GET & POST in v100.

                          For each player the PI discovers, it registers a weblink pointing to the same html file (sonos-player.html) but the link is registered with an additional parameter, indicating which player it applies to.

                          example weblink url: Sonos4/sonos-player.html?deviceudn=RINCON_48A6B8B4D8A101400. The parameter deviceudn is different for each weblink associate with its respective player.

                          In v18 an Ajax (Post) was done to Sonos4/sonos-player.html and all was OK. In V100 this results again in a 404 error. When I add the parameter to the POST (ie /Sonos4/sonos-player.html?deviceudn=RINCON_48A6B8B4D8A101400) I still get an error 404.

                          Advice?
                          I see the problem, we will discuss this internally and get back to you.

                          Comment


                            I am running 4.1.100.0 and was trying to edit a device graphic icon and in the past versions HS allowed me to select a folder that contained the icons. Now when I go to edit the icons, a long rectangular box appears with icons to be selected. There is now way to select icons from another folder. Also does anyone know what folder these icons are in? I guess I could copy the icon to this folder.

                            Thanks in advance,

                            Ronnie

                            Comment


                              Originally posted by spud View Post

                              I see the problem, we will discuss this internally and get back to you.
                              I found a solution, ie register a "hidden" link (register with no name so it doesn't show on the menu) ie Sonos4/sonos-player.html and all is fine and POSTS will work. I thought to raise the issue though, to have you guys come up with a recommendation for other PI authors who may need something similar.

                              Comment


                                Originally posted by Ronnie View Post
                                I am running 4.1.100.0 and was trying to edit a device graphic icon and in the past versions HS allowed me to select a folder that contained the icons. Now when I go to edit the icons, a long rectangular box appears with icons to be selected. There is now way to select icons from another folder. Also does anyone know what folder these icons are in? I guess I could copy the icon to this folder.

                                Thanks in advance,

                                Ronnie
                                rjh
                                As the 4.2 release is to improve the UI I second this.

                                ---
                                John

                                Comment

                                Working...
                                X