Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devices without multizone/groups (i.e. 1st generation devices) don't work properly [fixed in version 2.2.2] #44

Closed
sn0skier opened this issue Jun 1, 2019 · 14 comments

Comments

@sn0skier
Copy link

sn0skier commented Jun 1, 2019

I added a device in the config file:

I don't get any errors in the log file, but no device appears in the Devices section of the GUI.

@SamDel
Copy link
Owner

SamDel commented Jun 1, 2019

The device is only added when the call to get the device information is successful.

Can you try if you can get the device information with the next url (replace 192.168.0.1 with your ip address):
http://192.168.0.1:8008/setup/eureka_info

Errors are not logged when that call isn't successful.

@sn0skier
Copy link
Author

sn0skier commented Jun 2, 2019

I can get the device information at that address. Would you like me to post it here? I'm not sure if any of that information could compromise my privacy, but if you say it won't I trust you. Or I could email you the information? Thanks for your help.

@SamDel
Copy link
Owner

SamDel commented Jun 2, 2019

There's no need to post the information, it was a check to make sure the IP address is right.
Can you try 2.2.1? (I found a bug in 2.2. Only devices that are part of a group were added.)

@sn0skier
Copy link
Author

sn0skier commented Jun 3, 2019 via email

@SamDel
Copy link
Owner

SamDel commented Jun 3, 2019

Great! Thanks for testing.

You probably never used groups on your device?
Is there a multizone/groups element (in the eureka_info configuration from the device returns) for your setup?

image

@sn0skier
Copy link
Author

sn0skier commented Jun 3, 2019 via email

@SamDel
Copy link
Owner

SamDel commented Jun 3, 2019

I think the multizone configuration is only available in the newer versions of the device (not sure).
The code was looking for it and skipped the device when it isn't there.

Thanks! I'll create a new 2.3 release later with support for devices that don't have the multizone element.

@sn0skier
Copy link
Author

sn0skier commented Jun 3, 2019 via email

@SamDel
Copy link
Owner

SamDel commented Jun 3, 2019

Confirmed multizone is only for Chromecast 2nd Gen, Chromecast 3rd Gen, or Chromecast Ultra.

@sn0skier
Copy link
Author

sn0skier commented Jun 3, 2019 via email

@SamDel
Copy link
Owner

SamDel commented Jun 4, 2019

Sorry, multizone is used on multiple places, should have checked. Can you try 2.2.2?

Thanks again.

@sn0skier
Copy link
Author

sn0skier commented Jun 4, 2019 via email

@sn0skier sn0skier changed the title custom devices in config don't appear in Devices in GUI Devices without multizone/groups (i.e. 1st generation devices) don't work properly [fixed in version 2.2.2] Jun 4, 2019
@SamDel
Copy link
Owner

SamDel commented Jun 12, 2019

Thanks for changing the title. No further issues?

I've published a 2.3 release with the fix.

@SamDel SamDel closed this as completed Jun 12, 2019
@sn0skier
Copy link
Author

No further issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants