Hm it starts on 0.0.0.0:5557, this is different from my setup where it starts on localhost (192.168.0.x:5557) it might be the problem. But I am not at home now so I can not check it atm.
Thanks for this addon, it’s just what I needed.
I’ve set it up with my Google Assistant and it works well, although there’s one annoying issue.
After I give the command (‘Turn on xbox’, for instance), the xbox will switch on, but the assistant will say that ‘Sorry, there was an error with xbox’. Is there a way to workaround this? It’s pretty annoying :]
Sensor seems to work fine, but if I want to run an automation task based on the state of the XBOX (value is on), it does not work.
This is what the log shows at the add-on.
ERROR in app: {'success': False, 'message': 'Connecting failed! Result: ConnectionResult.Pending'}
What I also noticed is that when I want to put my live credentials in the config of the add-on, I can add values, but if I save it, the config is empty again
What I also noticed is that when I want to authenticate (and enter my credentials) here:
Have you checked if the xbox live service is up? It had some problems recently with many users unable to log in to xbox. Check on your xbox if you can log in.
I also found in my case that it wouldn’t connect due to a version mismatch (hassio addon looks for an older version of the xbox-rest-server, I believe it was 0.9.6) you could change this line in the xboxone.py to the current version number (0.9.8). This had fixed the problem for me, but yours seem like you don’t have access to the live servers.
Np, was just browsing the forums anyways. Maybe a reinstall could help. But tbh I wouldn’t really know. Only thing I can think of is that there went something wrong either at the install or maybe the version number which I mentioned.
What you should see after logging in via the addon is a blank page with a long url in the address bar. You will need that url to connect.
Yeah, I had that error too. My question is, does it work? Try turning the xbox off via Hass. And then try turning it back on again (btw it could take a minute before the xbox-rest-server finds your newly connected xbox) don’t forget to add the things that should be added in your configuration.
If you have the same problem as I had, then it will only work once or twice before becoming unresponsive again.
That is working. Now the strange part is that I have a automation task which should notify slack when XBOX is on or off. That doesn’t seem to work at all anymore and I do not know why that is.
It did worked and the states are configured fine and also do work at other components
Well in my case it only worked once or twice (because the version numbers mismatched). After changing that line it worked fine for me. However I use the TV app most of the times on my xbox and will update the state to Unknown when in that state. So I made my automations trigger on unknown instead of being ON. Maybe that helps.
The odd thing is that if I create an entry on a card which checks the state before viewed, it works. it validates the ‘on’ state:
card:
show_header_toggle: false
title: Media
entities:
- entity: media_player.xbox_one
show_empty: false
state_filter:
- 'on'
title: Media
type: entity-filter
If i use the same state check in an automation task, it does not work. That would point to the direction of the automation trigger which is not picked up properly
I’m not at home atm, though I’m not a 100% sure I still use that automation. I know for sure that I used the Unknown state for my button card for example. Or it will keep the icon color as if it were off.
Maybe you could find something on my git page, though I’m not sure if it is in there