Announcement

Collapse
No announcement yet.

Feature Requests

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

  • shill
    replied
    Thanks!!

    Leave a comment:


  • spud
    replied
    I added a few features in version 3.0.0.30

    4. New devices - another great option would be "enable new devices by default?" If turned off, a new row would be in the list, but no devices would be created unless I intentionally checked the "Enable" box.
    edit the Chromecast.ini file and add the following line in the [GENERAL] section
    Code:
    disable_new_chromecasts=True
    then restart the plugin

    I did not add it to the config page as I don't see this as something a lot of people want to mess with.

    It should also resolve your feature #2, because if a chromecast is disabled, it won't receive any TTS.



    5. Make the device name in the config page linkable to the root device properties screen.
    done


    6. Use the "address" property of the root device to store the "ID" from the config page to confirm the device is in fact that specific one (especially useful if a user renames their devices manually).
    done, now the "Technology Address" of all HS devices associated with a chromecast is the ID of the chromecast. It is only set when the device is created, so you will have to delete your current devices if you want this to be set.

    Leave a comment:


  • shill
    replied
    Originally posted by jvm View Post
    Then, on the plugin config page, I un-check the "TTS" box on all devices except that group (you could also un-check the "Enable" box and the plugin then won't create devices for each Chromecast).
    Yes, I get that, but the point of my feature request is because if I get a new GH device (or factory reset one), it automatically turns on the TTS checkbox. And if you're using a group and only want that group to do the announcements, you want that feature too

    Leave a comment:


  • jvm
    replied
    shill. Consider whether you can bypass all the mess of dealing with individual Chromecast devices within the HomeSeer environment by using the Google Home app to group devices. Then, in HomeSeer, you only need to interact with the Group. That's a method I've been using.

    More particularly, for my setup, I have all of my Google Mini Hubs in a group called "Group - Announcements" which I created as a speaker group in the Google Home application. "Group - Announcements" will then appear in the Chromecast plugin "config" page as if it were just any other Chromecast device (note - you may have to re-start the plugin for it to appear). Then, on the plugin config page, I un-check the "TTS" box on all devices except that group (you could also un-check the "Enable" box and the plugin then won't create devices for each Chromecast). Any announcement (i.e., any "speak" action) within HomeSeer then gets sent to all devices in "Group - Announcements" and I can edit and update that group from Google Home on my phone if I want to change where announcements are played -- I find that much simpler than re-writing HomeSeer events and, to me, provides a more "natural" way of working with Chromecast devices.

    Leave a comment:


  • shill
    replied
    Originally posted by spud View Post
    For all chromecast devices the name is set as the "Location", so you can distinguish them using this field, can't you?
    That's true out of the box, but that's not how I use the "Location" field in my setup (since it's configurable), so it doesn't make sense to leave the name of the device there in my case (and possibly others since those are customizable).

    Originally posted by spud View Post
    I could add such an option, but I'm not sure I'm following what you say: if you use a group, and if your Speak actions target only this group, then your announcements shouldn't go to a new chromecast you have just added (even if TTS is enabled) because it is not part of the speaking group.
    That's true if you use targets. My setup goes back a LONG time, so my announcements are just using "speak" (and some areas of my house use other speakers). So I just want to "speak" and have it come out my TuneBlade-driven speakers AND whichever HS device(s) I choose (whether it's a group or just individual ones or a combination). So it's annoying to me if I don't want it to come out newly added speakers by default. And, IMHO, just using "Speak" is the basic case that should be the easiest for new users.

    Leave a comment:


  • spud
    replied
    Originally posted by shill View Post
    1. Device Name - the root devices are all named "Root", making them impossible to distinguish. Since you already know what the name of each device is (it's the "Name" column on the config page!), could you change the root device creation process to use the Google device name instead?
    For all chromecast devices the name is set as the "Location", so you can distinguish them using this field, can't you?

    Originally posted by shill View Post
    2. TTS checkbox - how about an option to "add new devices to TTS by default?" We have about 16 devices in our house, but in order to have synchronized announcements I use a group with just the ones that should do the speaking. Unfortunately, adding a new device gets the TTS checkbox turned on by default and suddenly we have announcements that we don't want, and the WAF takes a hit until I figure out (again, since it's infrequent) why that's happening.
    I could add such an option, but I'm not sure I'm following what you say: if you use a group, and if your Speak actions target only this group, then your announcements shouldn't go to a new chromecast you have just added (even if TTS is enabled) because it is not part of the speaking group.

    thanks for the suggestions, I will implement most of them.

    Leave a comment:


  • shill
    started a topic Feature Requests

    Feature Requests

    I'm restarting my efforts to switch my whole-house TTS to cast devices, so I'm diving back into using the plugin. A few things have come up that I'd love to see in the plugin:

    1. Device Name - the root devices are all named "Root", making them impossible to distinguish. Since you already know what the name of each device is (it's the "Name" column on the config page!), could you change the root device creation process to use the Google device name instead?

    2. TTS checkbox - how about an option to "add new devices to TTS by default?" We have about 16 devices in our house, but in order to have synchronized announcements I use a group with just the ones that should do the speaking. Unfortunately, adding a new device gets the TTS checkbox turned on by default and suddenly we have announcements that we don't want, and the WAF takes a hit until I figure out (again, since it's infrequent) why that's happening.

    3. Removing devices - it would be better if "Enable" controlled creating and deleting new devices.

    4. New devices - another great option would be "enable new devices by default?" If turned off, a new row would be in the list, but no devices would be created unless I intentionally checked the "Enable" box.

    5. Make the device name in the config page linkable to the root device properties screen.

    6. Use the "address" property of the root device to store the "ID" from the config page to confirm the device is in fact that specific one (especially useful if a user renames their devices manually).

    Thanks for your work on this plugin - I took a look at it once upon a time and decided not to tackle figuring out the cast protocol, so I'm very grateful you did!
Working...
X