Integration with Smart Plugs like Shelly Plug

[jo-chemla]

Hi @seriousm4x, first of all thanks for UpSnap! I'm running it through docker-compose with host network mode, and trying to wrap my head around how to use it with shelly-plugs - just spotted some on your dashboard screens, so I'm trying to replicate your setup.

At the moment, I've got several PCs with WoL activated and working through UpSnap, which is great. For each computer I've also edited the BIOS setting set to restore last power state, so when one computer is crashed I can hard-reboot it via the shellyplug webui. I'm trying to reproduce the same by aggregating all on/off toggles for each plug through upsnap, rather than using upsnap ports/links to point to each plug dedicated webui.

To do so, I would like to know if I'm forced to use the below shelly HTTP REST API to make it work, with custom wake and shutdown commands, or if there is a better way to do it.

Thanks in advance and happy to give more feedback!

Timeouts: 2s
Wake http://shelly-plug-ip/relay/0/?turn=on
Shutdown http://shelly-plug-ip/relay/0/?turn=off
Ping: (curl -m 1 -s "http://shelly-plug-ip/relay/0" | jq -e ".ison == true")

[seriousm4x]

To be honest, I just added the Shelly plugs to my dashboard for the screenshot. I only use them to monitor my power draw.
Regarding your question, using custom wake and shutdown commands with curl is the way to go. That's the only way.

[jo-chemla]

Thanks for the quick response. I'm playing with the jq package (installed with the entrypoint add jq command), and managed to edit the ping as summarized in text block above so the on/off UI elements reflect whether the plug is toggled on or off (rather than if it is reachable since it should always be connected to network). It does work, so I just need to go through all the plugs and add them.

curl -m 1 -s "http://192.168.10.160/relay/0" | jq -e ".ison == true"

Maybe a nice way to facilitate this process would be

• to add custom variable that would be parsed, like DEVICE_IP
• and to allow duplicating a device, so its wake/shutdown/ping/group etc would be auto-filled
• also, when adding port, the link text field could be auto-filled

Not related niceties:

• ability to rename groups could be nice
• would it be possible to disable the heartbeat animation of the ping gree/red dots?

Do you want me to add these as feature requests somewhere or are these not generic enough to be shared with other UpSnap users? Again, thanks a lot for your great work!

[seriousm4x]

Glad it's somewhat working out.

Maybe a nice way to facilitate this process would be

* to add custom variable that would be parsed, like `DEVICE_IP`

* and to allow duplicating a device, so its wake/shutdown/ping/group etc would be auto-filled

* also, when adding port, the link text field could be auto-filled

Not related niceties:

* ability to rename groups could be nice

* would it be possible to disable the heartbeat animation of the ping gree/red dots?

I actually like all of these ideas! I think they contribute a lot to ease of use.

I'm not entirely sure about the last one (animation) and whether it's relevant enough to have its own setting. It's probably possible to achieve this by simply adding a class like "animate-none" or something similar. DaisyUI Status Component

If you'd like to implement any of your points yourself, pull requests are always welcome! :)

[jo-chemla]

Thanks for the feedback and interest for these features! Unfortunately I'm not a svelte developper but would have loved to contribute. I can only skim through the codebase and would assume:

• regarding DEVICE_IP variable parsing/substitution, it would probably happen within /src/lib/components/DeviceForm.svelte? Should one do it for each $pocketbase .collection('devices/ports') .create/update calls, updating every device attribute/property keys with values substituted by the device.ip when DEVICE_IP is encountered?
• device duplication button could be placed akin to the edit button around here. Can this use the /device/new route and autofill from selected device properties? Or should that route accept post payload to pass these duplicated device properties?
• For autofilling port IP, I assume one can edit the createEmptyPort() function passing device.ip here
• group renaming could be done via a rename (pencil) icon next to the group name on the front page, which could be placed around here
• I like the animate-none option for the daisyui-component, could these be passed as custom CSS variables appended to the homepage?

Hope I'm not too much mistaken!