PS5-MQTT: Control PlayStation 5 devices using MQTT

FunkeyFlo · October 9, 2022, 4:58am

There’s a link on the main page of the GitHub repo.

As mentioned in the docs adding PSN accounts is optional.

adandu · October 9, 2022, 6:17pm

Hello, thanks for this awesome add-on.
I have a question, if I may.
Is it possible to have an option to manually add the PS5 IP address manually? Currently I use multiple subnets, each with a different purpose, and the Add-On cannot discover my PS5. Obviously, my HA server and PS5 are on different subnets.

Thanks.

FunkeyFlo · October 9, 2022, 7:08pm

I’m afraid it isn’t possible at this time. See this reddit discussion for more info.

edit: I keep forgetting to hit the correct reply button

mhoogenbosch · October 12, 2022, 6:37pm

i’m feeling pretty stupid here, but I’ve got things going. Authenticated and all. It also sees when the device is in a different powerstate (unknown / awake and standby), but it keeps saying idle with activity. Is this a setting somewhere?

FunkeyFlo · October 12, 2022, 6:52pm

You need to supply a PSN acccount.

mhoogenbosch · October 12, 2022, 7:21pm

yeh, basically stopped reading with ‘optional’, but thanks for making me feel more stupid, like rtfm ;-). But it works, thanks a lot!! Too bad it stops working in two months, never the less, again; thanks for your effort!

FunkeyFlo · October 13, 2022, 7:34am

Glad It worked out.
If only Sony would be so kind to officially support 3rd party API’s…

FunkeyFlo · October 13, 2022, 1:19pm

I stand corrected. VLAN support is possible as one of the users has verified. (I don’t have a VLAN setup myself, so I wasn’t able to test it). The only thing not possible is auto-discovery.
I’ve re-openend one of the feature requeststo track progress on this change.

xuonghuynh · October 14, 2022, 8:00am

@FunkeyFlo Hi, I have an issue that it not recognize my PS5, it only show Refresh Devices button. I already installed MQTT and running. In addon no error message:

Starting PS5-MQTT…
2022-10-14T07:51:41.533Z @ha:ps5:webserver Server listening on PORT: 62181

Anyway to debug this issue, or how to check is it connected with MQTT ?

FunkeyFlo · October 14, 2022, 8:44am

This means your PS5 cannot be found. The add-on will only be able to find devices on the same network as the HA host. VLAN support is currently being worked on.

Edit 1:
You could try to use the playactor cli’s browse command to verify availability. But remember to use it in the same network as your HA host. But to be fair. This would be the same as using the add-ons web-ui…

Edit 2:
Your device also has to be on. Devices not in rest or awake states cannot be discovered.

xuonghuynh · October 17, 2022, 4:21am

Thanks for reply, I’m sure it in the same network (HA IP 192.168.31.5 and PS5: 192.168.31.64) and PS5 is on. I can ping my PS5 from my PC but don’t know why it doesn’t work with this integration or playactor cli’s. Is there any setting in PS5 that block the connection ?

edit: oh I install playactor on other PC and it found the PS5, so maybe the HA host has problem, I will check it. Thank you anyway

datlalo · October 18, 2022, 7:52pm

Hi,
I tried installing the add-on on a new setup today and for some reason I can’t get the entities to appear.
The only one that appears is called update.ps5_mqtt_update.
I have installed an MQTT broker and linked my ps5 through the web ui.

Here is a picture of my logs

Any ideas on what I might be doing wrong?

Krieger2690 · October 18, 2022, 8:03pm

I’ve got the exact same problem now, but I am not new. I have been using this addon for a while. Last time it worked correctly for me was around 5 hours ago.

I am getting the exact same error and I though I must have been doing something wrong, so I refreshed my NPSSO token — nothing.
I was about to post a reply here when I noticed your message. I guess we’ve got to wait it out. @FunkeyFlo am I right here?

Krieger2690 · October 18, 2022, 8:29pm

Update: I have just installed a fresh patch for the addon. Now, I am getting this in the logs.

Starting PS5-MQTT...
2022-10-18T20:20:33.587Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:20:33.681Z @ha:ps5:mqtt MQTT Message received ps5-mqtt/78C881A4815F
2022-10-18T20:20:33.751Z @ha:ps5:webserver Server listening on PORT: 63163
2022-10-18T20:24:26.322Z @ha:ps5:mqtt MQTT Message received ps5-mqtt/78C881A4815F/set/power
2022-10-18T20:24:27.894Z @ha:ps5:mqtt MQTT Message received ps5-mqtt/78C881A4815F/set/power
2022-10-18T20:25:24.714Z @ha:ps5:mqtt MQTT Message received ps5-mqtt/78C881A4815F/set/power
2022-10-18T20:25:36.864Z @ha:ps5:mqtt MQTT Message received ps5-mqtt/78C881A4815F
2022-10-18T20:25:40.660Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:25:44.102Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:25:49.104Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:25:54.095Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:00.015Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:06.450Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:12.908Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:19.283Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:25.788Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:32.185Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:38.607Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:45.075Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:51.565Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:26:57.966Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:27:04.414Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:27:11.047Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:27:17.499Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"
2022-10-18T20:27:23.924Z @ha:ps5:psn-api Unable to retrieve PSN information. API response: "403:Forbidden"

It appears as if I was banned, or there is really a problem on Sony’s side. Taking this into consideration, there should be multiple people affected.

LE:

Putting the console in standby and waking it up works.
It only recognizes the “idle” state. Once I start a game, I am expecting to see its name as an entity. Instead, the console remains idle, game running or not, and it is constantly spamming the log.

The only change I made was refresh and update the NPSSO token. It was working just fine this afternoon and it has been working fine since the very beginning.

sammyke007 · October 18, 2022, 9:33pm

Sony changed something at their side. FunkeyFlo already fixed it the same evening! Update will be available soon.

Edit: voila… 1.2.2 already released

FunkeyFlo · October 18, 2022, 10:05pm

Hi guys, sony decided to change the TLD of one of their websites from .net to .com which caused a lot of projects, this one among them, to break. But rejoice, 1.2.2 was released and everything should be back to the way it was.

P.s. the new 403 error messages were added to keep the app from crashing but still informing you that something’s going wrong with the PSN communication. So don’t worry, you’re not banned!

adamjthompson · October 18, 2022, 11:53pm

I just installed this Add-On and it perfectly replaces one that I was previously using in HomeBridge. Thanks for your hard work on this!

In the future, would it be possible to change the authorization process so that it does not require a new NPSSO token every two months?

Also, I noticed that you cannot use the same browser for multiple accounts (or at least it didn’t work for me). I could only get one working at a time unless I used a different browser for both. This might be a limitation worth mentioning in the documentation.

FunkeyFlo · October 19, 2022, 6:38am

In the future, would it be possible to change the authorization process so that it does not require a new NPSSO token every two months?

No, not as far as I know.

Also, I noticed that you cannot use the same browser for multiple accounts (or at least it didn’t work for me). I could only get one working at a time unless I used a different browser for both. This might be a limitation worth mentioning in the documentation.

I felt like that was to be expected. These non-essential bits of documentation have really low priority for me ATM. If you feel like it you could add it yourself.

FunkeyFlo · November 5, 2022, 5:45pm

This week I made an attempt to fix VLAN support. However, I’m looking for people to verify whether the fix actually works (as I don’t have a VLAN setup myself).

If you want to help:

Install the edge version of the addon.
Enter the broadcast IP of the network your PS devices by filling out the new config option: device_discovery_broadcast_address.
Let me know if it worked

QNimbus · November 8, 2022, 7:45pm

Using the edge version and the device_discovery_broadcast_address worked for me. That is, I was able to discover my PS5 which is on a different VLAN and I was also able to authenticate.

However, the MQTT topic for PS5-power (ps5-mqtt/78C8XXXXXXXX) shows the correct status at first:

{"power":"STANDBY","device_status":"online","activity":"none"}

but after about ~20 seconds it goes to:

{"power":"UNKNOWN","device_status":"offline","activity":"none"}

The result is that the PS5 MQTT entities in HomeAssistant become disabled.

Edit: I believe it has to do with a JSON parsing problem, I will try to update this post with a log excerpt when I get around to it!