Use a Loupedeck as a controlpanel/dashboard for home assistant!🎉

Good morning,

to be honest I hope to make yours obsolete, currently mine is not there yet.

Sensors are definetly on the list. I think supporting these - including templating for formatting - will result in a mixture of Websocket API to listen for changes and REST to then get the template formatted.
Currently working on the climate controls, displaying measured temperature, set temperature …

Just now I’m mostly fighting with that stupid undocumented piece of SDK from Loupedeck. We can just hope that after Logitech bought them there will be some progress on that.

Keep going, I like that.

This was the reason why i didn’t publish my plugin on the Loupedeck site. Their support for developers wasn’t as good as expected.

During vacation, I will take a more in-depth look at your code!!

I just published v0.2.0 with basic support for sensors. Friendly name with value and unit of measurement gets displayed, no template support yet.

Currently looks like that:

2 Likes

v0.5 just got published.

Connections issues have been sorted, lots more entities supported now. Check release notes for details.

Please report any issues on Github.

2 Likes

v0.6 just got published.

Support added for lock and water_heater entities.

I also sent the plugin to the official Loupedeck marketplace but I don’t expect it to be published before christmas.

Edit: the plugin is now available in the Loupedeck Marketplace

2 Likes

I am trying to use your plugin. But unfortunately I’m failing a bit. What do I have to enter in these fields? I send the picture with what I mean.

and this is the json

From the json you are showing only the “token” and “url” entries are relevant to this plugin. Everything else is left-over from lubedas plugin.

Concerning your question, what do you want to do? Simply said you have to put the name of the script you want to call in HA into the middle field and give the action a name for Loupedeck …

Thank you very much for your answer.
I now only have the token and the URL in the homeassistant.json.

Do I now have to create a new json file and add my script for the entities to it? Is there somewhere where I can read about this? I would like to implement this, but I realize that I am doing something a bit stupid.

What do you want to achive?

I would like to use it to switch two lamps on and off.

After configuring your token and url in the json file you would have to restart the Loupedeck software once. If you did everything right you will find all your existing entities in the Loupedeck software. You can just drag and drop them like with everything else.

If there are no entities or you get an error message please check your configuration. There is also a logfile (ha.log) in the plugins_log folder of the Loupedeck software.

The logs can be found here: C:\Users<YourUsername>\AppData\Local\Loupedeck

PS: you dont need a script to toggle a lamp or a switch!

So, this is my log file. Unfortunately, the Loupdeck software does not allow me to select the entities.

It seems that the plugin is not able to connect to HA.

I saw that the URL in the log is different to your configuration file posted earlier, do you still have the port configured for the url in your .json file? http://…:8123/api ?

I tried a little bit. I tried the IP with 8123 and without. It does not work. The path is as follows:

C:\Users<username>.loupedeck\homeassistant\homeassistant.json

The path to the file is correct but I cant tell you whats your correct url. Basically its the one you use in your browser to access HA, then use /api as the path …

My IP address for Home Assistant is 192.168.1.70:8123
Is it important to mention that it is over http?

I have the same problem as @DavDav after updating Loupdeck software to the latest 6.0 version. This version deleted some of my plugins and after reinstalling HA plugin, I can’t do anything with it.

The 6.0 update broke the plugin, yes.
As the SDK is not yet released I’m sorry but I can’t do anything about it.

I’ll post here and on Github as soon as the plugin is ready.

It’s remarkable though, that the listed the plugin as working somewhere on their website.