Dev

[cdnninja]

@buzzeddesign starting a discussion to share progress

[cdnninja]

Do you have auth working locally in post man? I saw you had a few auth related URLs in the details. If so we could skip using the 0auth library and just mimic what you have. If not I can keep playing with auth0. I don't have much to go on with that though.

[bushbrother]

Nothing in the logs sadly, I had checked before. How can I run the python from within HA directly?

[cdnninja]

It won't be within HA.

The readme on this repo has the code of how I test. Download the repo, ideally with GitHub desktop. Copy paste that contents into another file somewhere else on the pc.

Correct the path to the api and enter creds and run it.

[bushbrother]

will try this evening if i get a chance. Thanks.

[bushbrother]

OK got round to this. Firstly your code had issues for me. There is a \ before the * on line 8 that is not required and for me logger needed to be as __ name __ not with *.

Anyway, long story short I used the same credentials and it logs in fine and i see all the card data etc.

[cdnninja]

I have made corrections to the docs. Not sure how that happened.

I also made some updates today. Possible fixing what was happening for you but doubtful. I think we move this to an issue in the _HA repo if still an issue. Could you retry?

[cjb0001]

Here are the endpoints I'm aware of:

GET APIs
https://api.yotoplay.com/device-v2/devices/mine
https://api.yotoplay.com/device-v2/$deviceid/status
https://api.yotoplay.com/media/displayIcons/user/me
https://api.yotoplay.com/user/details
https://api.yotoplay.com/user/family/mine?allowStub=true
https://api.yotoplay.com/card/mine
https://api.yotoplay.com/card/mine/user/family/mine?allowStub=true
https://api.yotoplay.com/card/family/library
https://api.yotoplay.com/card/library/free
https://api.yotoplay.com/card/library/club
https://api.yotoplay.com/card/family/library

Please note, as I stated in the HA Integration repo, I feel using MQTT is the MUCH BETTER way to get status instead of hammering the status endpoint.

[cdnninja]

Thanks for providing this. I almost get the impression you work for yoto with the knowledge you have! Greatly appreciated.

In concept agreed on MQTT. However I don't see certain data coming back around the player when I watch MQTT subscribed to the 3 topics. An example is device status data. It appears this only comes from the API above rather than MQTT. MQTT seems to offer just playback related items. Does this align to your understanding?

[cdnninja]

I suspect some post APIs exist for certain config items.

[cdnninja]

Also would love support. Feel free to create PRs on this if you are interested and have time. I am thinking each of the above APIs need to be added to the API file and mapped to any relevant data.

[cjb0001]

I don't see certain data coming back around the player when I watch MQTT subscribed to the 3 topics. An example is device status data.

From the mqtt /status topic I see quite a bit of information. I haven't done a comprehensive cross-reference vs the $deviceid/status API but it looks like all data is present in mqtt.

{
"status": {
"activeCard": "XXXXX",
"aliveTime": 2527630,
"als": 0,
"battery": 4088,
"batteryData": "0:0:0",
"batteryLevel": 100,
"batteryLevelRaw": 99,
"batteryProfile": "JY734352",
"batteryTemp": 0,
"bgDownload": 0,
"bluetoothHp": 0,
"buzzErrors": 0,
"bytesPS": 0,
"cardInserted": 1,
"charging": 0,
"chgStatLevel": 0,
"day": 1,
"dayBright": 100,
"dbatTimeout": 60,
"dnowBrightness": 100,
"errorsLogged": 6,
"failData": 0,
"failReason": 0,
"free": 3831100,
"free32": 66190,
"freeDisk": 6406112,
"freeDMA": 56202,
"fwVersion": "v2.17.6",
"headphones": 0,
"missedLogs": 0,
"nfcErrs": "0.00%-n/a",
"nightBright": 100,
"nightlightMode": "off",
"playingStatus": 0,
"powerCaps": "",
"powerSrc": 0,
"productType": "mini",
"qiOtp": 0,
"sd_info": "0xad, 0x4c53(LS), USD00, 16, 896843272, 11-2022, 1, 0, 1461, 50000000",
"shutDown": "nA",
"shutdownTimeout": 1800,
"ssid": "XXXXXXXX",
"statusVersion": 3,
"temp": "0:0:0",
"timeFormat": "24",
"totalDisk": 15441920,
"twdt": 0,
"upTime": 10,
"userVolume": 50,
"utcOffset": 7200,
"utcTime": 1713872497,
"volume": 55,
"wifiRestarts": 1,
"wifiStrength": -34
}
}

[cdnninja]

Interesting. I had put my status MQTT response here:

yoto_api/yoto_api/YotoPlayer.py

Lines 39 to 57 in 41312ac

	{
	"status": {
	"battery": 4174,
	"powerCaps": "0x02",
	"batteryLevel": 100,
	"batteryTemp": 0,
	"batteryData": "0:0:0",
	"batteryLevelRaw": 100,
	"free": 3875896,
	"freeDMA": 100298,
	"free32": 100638,
	"upTime": 130228,
	"utcTime": 1713713466,
	"aliveTime": 4103240,
	"qiOtp": 0,
	"nightlightMode": "0x194a55",
	"temp": "notSupported",
	}
	}

Maybe it changes based on what is happening.

[cjb0001]

Yes, it seems to update when things are happening. I turned it on and off, played, paused, took cards in and out, and the topic fills up nicely with information.

[cdnninja]

@cjb0001 I have mqtt working with HA now. Need to dial it in for update speed but data is flowing.

I don't have the endpoint though for setting light status on the yoto. Any chance you could sniff the control and status API endpoint? it doesn't seem to go across MQTT.

[cdnninja]

I also would love to know how you are collecting these endpoints.

[cjb0001]

Nice work getting MQTT going!! I'll take a look at it soon.

I only have a mini so can't confirm any of this color stuff, but here's some info I was able to glean for you:

hex	color
#40bfd9	sky_blue
#41c0f0	sky_blue
#9eff00	apple_green
#e6ff00	apple_green
#f57399	lilac
#f72a69	lilac
#ff0000	tambourine_red
#ff3900	orange_peel
#ff8500	bumblebee_yellow
#ff8c00	orange_peel
#ffb800	bumblebee_yellow
#ffffff"	white
#0	black ambient_light_off

For setting the light, it looks to be:
METHOD: GET
URL: https://api.yotoplay.com/device-v2/xxDEVICEIDxx/config

METHOD: PUT
URL: https://api.yotoplay.com/device-v2/xxDEVICEIDxx/config
REQUEST BODY:
{
"deviceId": "xxDEVICEIDxx",
"name": "WXYZ’s Yoto Player",
"fwVersion": "v2.17.7",
"popCode": "XXXXXX",
"releaseChannelId": "beta",
"activationPopCode": "XXXXXXXX",
"deviceType": "mini",
"deviceFamily": "mini",
"deviceGroup": "",
"mac": "xx:xx:xx:xx:xx:xx",
"online": false,
"geoTimezone": "My/Loc",
"config": {
"bluetoothEnabled": "1",
"showDiagnostics": true,
"displayDimTimeout": "60",
"shutdownTimeout": "1800",
"headphonesVolumeLimited": true,
"repeatAll": false,
"dayTime": "07:15",
"maxVolumeLimit": "13",
"ambientColour": "#ff0000",
"dayDisplayBrightness": "99",
"dayYotoDaily": "xxxxx/daily/",
"dayYotoRadio": "xxxxx/radio-day/01",
"daySoundsOff": "0",
"nightTime": "20:00",
"nightMaxVolumeLimit": "12",
"nightAmbientColour": "#ff0000",
"nightDisplayBrightness": "100",
"nightYotoDaily": "xxxxx/daily/",
"nightYotoRadio": "xxxxx/radio-night/01",
"nightSoundsOff": "1",
"hourFormat": "24",
"timezone": "",
"displayDimBrightness": "0",
"systemVolume": "100",
"volumeLevel": "safe",
"clockFace": "digital-sun",
"logLevel": "none",
"alarms": []
}
}

[cdnninja]

Those colors looks to be a different format than I get back. I have the larger v3 player though.

[cjb0001]

I also would love to know how you are collecting these endpoints.

On the API side, Android Studio, the Yoto APK, and HTTP Toolkit. Bit of Node-Red for various digging too. On the mqtt side, MQTT Explorer.