Repository: Few addons

Installation Home Assistant OS
84

Man … complicated. (edit: I got it working too – posted details in the old component’s thread)

Anybody think there’s any hope of a PS4Waker HASS_IO component being released that auto-authenticates and does all this for us?

Thank you, danrspencer, for the instructions. I wouldn’t have got it working without you.

I have a lead on artwork too. I noticed in the HASSIO\config\custom_components\media_player\ps4.py file, line 48 mentions: MEDIA_IMAGEMAP_JSON = 'https://github.com/hmn/ps4-imagemap/raw/master/games.json'. That link takes me to a site with a list of broken links to jpg’s. Some of the viable links have images with 1024x1024 pixels. I’m assuming those were the art files and that this is why nobody is seeing game art.
Update: I can’t seem to get this working via local .jason and .jpg files nor via uploading the .json to pastebin and using PSN .jpg’s in the same format as the original author. Not sure why… I feel like it should work

1 Like
85

Has anyone worked out how to get the cover art to show?

86

Vkorn, do you have any plans to update your smartthings addon? Stjohnson has done several upgrades since you created your addon.

87

Hi,
I managed to control my ps4 your way. A big thanks for your post. But before following your guide I tried the following:

I changed my Windows PCs MAC address and the hostname to everything of the hassio host. I then installed ps4-waker with the builtin ubuntu core of Win10. Running this setup, I got correct credentials and the correct MAC and hostname shown up in the playstation’s connected devices. But I think it is not only the MAC or the hostname - it looks like Sony is generating correct key stuff here. No way of easy cheating…

after that … step 1 to 6, and I was done in about 3 minutes (so don’t worry to use this way)

88

Did you ever find a solution to the problem of the artwork not showing up?

89

No, I never did: Even after fixing broken links in the python file, the add-on wouldn’t display artwork.

I bet it’s fixable, but I don’t code much.

90

Does this method still work? I’ve read through this entire topic. I’m having an issue navigating to

“http://HA_IP:3031/ps4/PS4_IP/info”

in which it displays: {“status”:“Could not detect any matching PS4 device”}

When I SSH in, however, and do it from there, it works. What gives?

91

I know this is a older thread but…
when I installed the wrapper I then did docker ps and got the ID for the vkorn/aarch64-ps4waker and bash into that… I then tried to install the ps4-waker and it gave some errors… am I doing this wrong now given I am using the wrapper?

➜ ~ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3aaecb847150 vkorn/aarch64-ps4waker “/usr/bin/entry.sh /…” 10 seconds ago Up 9 seconds addon_e5829d31_ps4waker
➜ ~ docker exec -it 3aaecb847150 /bin/bash
bash-4.3# npm install -g ps4-waker
Error: could not get uid/gid
[ ‘nobody’, 0 ]

at /usr/lib/node_modules/npm/node_modules/uid-number/uid-number.js:37:16
at ChildProcess.exithandler (child_process.js:211:5)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:886:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:497:12)
92

Found the answer to my issue… it was because I am running HASS.IO 64bit - needed 32bit only.

93

I am also running the 64bit version and had the same error message. My solution was to run:

npm config set unsafe-perm true

before

npm install -g ps4-waker

94

Adding the repo https://github.com/vkorn/hassio-addons does not work anymore.

19-04-02 14:09:18 INFO (MainThread) [hassio.addons.git] Clone add-on https://github.com/vkorn/hassio-addons repository
19-04-02 14:09:20 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/git/e5829d31/appdaemon/config.json: required key not provided @ data['arch']. Got None
19-04-02 14:09:20 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/git/e5829d31/smartthings/config.json: required key not provided @ data['arch']. Got None
19-04-02 14:09:20 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/git/e5829d31/devicelocator/config.json: required key not provided @ data['arch']. Got None
19-04-02 14:09:20 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/git/e5829d31/configwatcher/config.json: required key not provided @ data['arch']. Got None
19-04-02 14:09:20 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/git/e5829d31/ps4waker/config.json: required key not provided @ data['arch']. Got None
95

It looks like the config.json for each addon within the repository just needs to be updated to the new format that Home Assistant is looking for (this repo broke for me when installing a new 0.91). Updating this is easy to do.

Fork vkorn’s repository, then open the addon you want and add this to config.json right below the startup line.

    "arch": [
        "aarch64",
        "amd64",
        "armhf",
        "i386"
    ],

You can see my updated copy here.

Then add your GitHub forked repository to the hass.io addon store and install your addon.

I only needed the SmartThings MQTT Bridge, so I forked vkorn’s repository and made the changes to the smartthings addon only. The small update should be the same for the others you guys want - just fork it and update it. Pretty simple

1 Like