Dashboard - Evolutions / Bugs / etc

[Terdious]

Hello,

I started the installation of Gladys v4 only 1 week ago. Over the last 2 days, following the integration of the MQTT service (Home automation entirely in Arduino(s)) and the great help provided by @AlexTrovato, I have created my 50 or so rooms related to my project presented here: https://community.gladysassistant.com/t/interrogation-sur-les-possibilites-et-exposition-dun-projet-en-cours-avec-mqtt/2215. I was therefore able to create 3 of my cameras on the dashboard (they work very well, indeed it is better to limit access, set to 2 seconds: the Rasp Pi 4 crashed several times - I am on debian) as well as a few devices by sending the Arduino in mqtt.

@pierre-gilles, I am turning to you because you had already solved the problem on v3 ^^, I therefore tried to display them on the dashboard, but unfortunately we are in the same situation as on v3 before my request, only the first 20 room are displayed:

Screenshot of the Dashboard rooms

Also, they are displayed in alphabetical order regardless of the houses. Would it therefore be possible to make the modification to have the same listing as in the MQTT service:

Screenshot of the MQTT service rooms

I assume that we will need to call the request « http://adresse-ip/api/v1/house?expand=rooms&order_dir=asc » instead of « http://adresse-ip/api/v1/room »

So:

GET /api/v1/house?expand=rooms&order_dir=asc HTTP/1.1
Host: "adresse-ip"
Connection: keep-alive
Accept: application/json, text/plain, */*
authorization: Bearer "[AUTH Bearer]"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36
Referer: http://adresse-ip/dashboard
Accept-Encoding: gzip, deflate
Accept-Language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7
If-None-Match: W/"[...]"

instead of:

GET /api/v1/room HTTP/1.1
Host: "adresse-ip"
Connection: keep-alive
Accept: application/json, text/plain, */*
authorization: Bearer "AUTH Bearer"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36
Referer: http://adresse-ip/dashboard
Accept-Encoding: gzip, deflate
Accept-Language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7
If-None-Match: W/"[...]"

For the moment the Dashboard looks like this:

I saw on a few topics that some posts might have their place on this topic: in particular the posts around 539 of the topic Parlons de Gladys V4 - #544 par Boimb.

[pierre-gilles]

@Terdious

@pierre-gilles, I’m turning to you because you had already solved the problem on v3 ^^, so I tried to display them on the dashboard, but unfortunately we are in the same situation as on v3 before my request, only the first 20 room are displayed

Oh no, that famous bug again, can you create an issue on the Gladys repo for me? Thanks!

@Terdious

Also, they are displayed in alphabetical order regardless of the houses. Would it be possible to make the modification to have the same listing as in the MQTT service:

Good idea, can you make a GitHub issue for me?

@Terdious

For now the Dashboard looks like this:

The cameras look great on your dashboard!

Thanks for your great feedback by the way, it’s not every day we have large installations and we don’t always test with as many rooms/devices ^^

[Terdious]

@Pierre-gilles

Oh dear, that famous bug again, can you create an issue on the Gladys repo for me? Thanks!

Issue created on Github: Bug view « Edition » of the Dashboard #656

[Terdious]

Hi @pierre-gilles,

@pierre-gilles

Oh no, this famous bug again, can you create an issue on the Gladys repo for me? Thanks!

I replied to you on Slack, but it’s better to save it here as well! Thanks again for this PR, it works perfectly ^^

@pierre-gilles

Good idea, can you make a GitHub issue for me?

Resolved as well! It works perfectly ^^

@pierre-gilles

Thanks for your great feedback by the way, it’s not every day that we have large installations and we don’t always test with as many devices/peripherals ^^

With pleasure, don’t hesitate if needed, I can leave remote maintenance so you can perform some tests if needed ^^

New points:

1. After a complete clean reinstallation following the database bugs encountered after the new MQTT service integration, I realize that the Dashboard has a bug when updating states:

Starting point - Ground floor garage lighting status: off

Action - Turning on the ground floor garage lighting - Visualization for 2 seconds after the action

No Action - Visualization after 2 seconds following the action to turn on the ground floor garage lighting - remains like this

Action - Turning on the upper floor garage lighting - Visualization same as the previous two steps

As a result, I no longer have access to the global garage turn-off command. If I press this, the selector goes to 1 then goes back to 0.
The only way to make it appear as 1 is to refresh the page.
So the same goes for turning off the three commands. If I turn off globally, the command goes to 0 but the other two remain at 1 until a page refresh.
If I turn off one or the other of the lights, everything remains at 1 until manual refresh.

2. I read in another topic, and we discussed it in a conference call about redesigning the visualization of the boxes on the dashboard to switch to device and feature names for better organization. Where are we at on this subject and can we help on this point? How?

Thanks in advance for the feedback!

[pierre-gilles]

@Terdious

So now I no longer have access to the global shutdown command for the Garage. If I press this, the selector goes to 1 and then back to 0.
The only way to make it appear as 1 is to refresh the page.
So same for turning off the 3 commands. If I turn off globally, the command goes to 0 but the other 2 remain at 1 until the page is refreshed. If I turn off one or the other of the lights, everything remains at 1 until the manual refresh.

I created an issue to investigate, as it stands I don’t see.

Dashboard "device in room" bug with on/off switch

@Terdious

I read in another topic, and we discussed it in a conv-call about the redesign of the box visualization present on the dashboard to switch the names of the devices and features for better organization. Where are we on this subject and can we help on this point? How?

We just talked about changing the default names, after that it will remain as customizable as it is now!

Nothing has been done to my knowledge.

[pierre-gilles]

@pierre-gilles

I created an issue to investigate, for now I don’t see anything.

After investigation, I can’t reproduce the bug! You’ll need to investigate what’s actually happening on your end. A device returning information?

[Terdious]

@pierre-gilles

After investigating, I can’t reproduce the bug! You’ll have to investigate what’s really happening on your side. A device sending information?

Well, I can’t reproduce the issue anymore since your update… ^^ That’s great!! Sorry for the trouble then!!

@pierre-gilles

@Terdious

I read in another topic, and we discussed in a conv-call about the redesign of the box visualization on the dashboard to switch the names of the devices and features for better organization. Where are we at on this subject and can we help on this point? How?

We just talked about changing the default names, after that it will remain as customizable as currently!

Nothing has been done to my knowledge.

Details of the Garage Door device features with 2 switches

Representation of the Garage Door features on the Dashboard

By the way, this raises the issue of global lighting shutdown!! So, I suppose that, as we discussed, we need to create feature types for garage doors, or even for barriers (with a stop option to leave them open). But does this mean that on the dashboard, there will be a window per room per feature type?

Would it be possible to consider the possibility of a search bar at the top of the window to quickly access the desired room? Because it’s already complicated to find a room in a Windows navigation with 3 columns. With 20 devices + 4 cameras. But on the Gladys Plus phone Dashboard, it’s even more complicated. For my part, I have to scroll a lot up and down to find what I need ^^
Of course, this is not a priority, but do you think this should be taken into account?

[pierre-gilles]

@Terdious

We need to create feature types for garage doors or barriers

I created the issue →

Create a feature category + types for "garage door"

Do you confirm what I describe in the card?

@Terdious

But does this mean that on the dashboard, there will be a window per room per feature type?

I don’t understand your question ^^

@Terdious

Would it be possible to consider the possibility of a search bar at the top of the window to quickly access the room you want?

I understand, it must not be easy for you who has a lot of boxes

I think what will help you is the multiple dashboards (Multiple dashboards and public dashboards · Issue #723 · GladysAssistant/Gladys · GitHub), but it’s clearly not for now. The search, maybe, but I don’t think that will happen right away either, it’s a development and I have a lot of todos on the fire

[Terdious]

@pierre-gilles

Do you confirm what I describe in the map?

Hi @pierre-gilles
Well, it’s actually more complex than it seems, I think. Based on my experience, my weekly usage is as follows:

For the barrier:

• Commands:
  1. Impulse Opening 2 Leaves then Automatic Closing (from the barrier),
  2. Impulse Opening 1 Leaf if pedestrians then Automatic Closing,
  3. Unlocked Opening 2 Leaves,
  4. Unlocked Opening 1 Leaf,
  5. Closing,
  6. Locked Closing (I use this mode in case of prolonged absence),
  7. Unlocking / Unlocking.
• States:
  1. 1 Leaf Open / Half-Open,
  2. 2 Leaves Open / Open,
  3. Closed,
  4. Locked.

And for the garage door:

• Commands:
  1.1. Impulse Opening,
  1.2. Impulse Closing,
  1.3. Impulse Stop.
  Or
  2.1. Impulse Opening then reset this command to stop it,
  2.2. Impulse Closing then reset this command to stop it.
• States:
  1. Open,
  2. Closed,
  3. Intermediate.

Would it be possible or do you think the idea is not good, to put a status icon in the header, and to put the commands below in the form of a push button?

[Terdious]

@pierre-gilles

I don’t understand your question ^^

^^ Forget it, sorry, I hadn’t tried, I thought that when you turned on the global switch of a room, it would also turn on the feature switches, including the « Garage Door Opening/Closing ». But after trying, I see that it doesn’t. Sorry!!

@Terdious

Details of the Garage Door device features with 2 switches

Representation of the Garage Door features on the Dashboard

On this point, is something planned? Because as you can see, on the switches, only the device name is displayed, not the feature name!!

Thank you for your answers in any case, and indeed:

@pierre-gilles

I understand, it must not be easy for you who has quite a few boxes

I think what will help you is the multiple dashboards (https://github.com/GladysAssistant/Gladys/issues/723)

That’s exactly what will give me more readability. After all, that was also the goal of a graphical dashboard for me!!

@pierre-gilles

but it’s clearly not for now. The search maybe, but I don’t think that will happen right away, it’s a development and I have a lot of todos on the fire

Yes, I know. And it’s already a very good thing that it’s noted ^^

Good luck!!

[pierre-gilles]

@Terdious

For the barrier:

Wow, that’s a complicated setup! I didn’t understand much. Let’s try to simplify it, because right now it’s definitely not user-friendly.

Can you describe your use cases to me, without talking about how you currently do it?

I want us to start with the need, not the technology. I’ll find a simple and user-friendly solution, because right now it feels like the person who designed your barrier wasn’t really a UX designer.

You can tell me things like:

• « In the morning, I go shopping by car, I open the barrier (2 gates) and then it closes automatically. »
• « In the evening, I go out on foot, I open the barrier (1 gate). »

We’ll make sure your use cases are met by Gladys, but we’ll probably find a different modeling than the one used for your current commands.

@Terdious

Regarding this point, is anything planned? Because as you can see, on the switches, only the device name is displayed, not the feature name!!

I understand your problem, but this solution won’t work for everyone. I’ve created a GitHub issue:

Rethink what is displayed in the "Device in Room" label for deviceFeatures

Here’s the problem: your issue comes from the fact that you have devices with many features, including duplicate binary ones.

Most integrations don’t have this problem, and therefore people don’t even have the option to modify the feature names (e.g., Philips Hue).

We’ll need to find a hybrid solution, but one that’s not « mystical » either. Something to think about calmly.

[Terdious]

@pierre-gilles

Can you tell me:

• « In the morning, I go out to do some shopping by car, I open the gate (2 doors) then it closes by itself. »
• « In the evening, I go out on foot, I open the gate (1 door) »

We will make sure that your use cases are fulfilled by Gladys, but we will probably find a different modeling than the one who designed your current commands.

@pierre-gilles

We will make sure that your use cases are fulfilled by Gladys, but we will probably find a different modeling than the one who designed your current commands.

Nothing complicated, and it’s me who customized it according to my needs - All the gates work the same way At the base you have:

• Command to open 1 leaf (or partial for gates on rail),
• Command to open 2 leaves (or complete for gates on rail),
• Close,
• Possible « timeout » to close after x seconds.

Then on the electronic board you have available contacts for the same functions with in addition:

• Stop.

I therefore connected all these contacts to an Arduino for the following need:

• I must receive a package in the morning or afternoon, I make a blocked opening, the Arduino sends the opening command then after x seconds (gate opening time) I activate the « Stop » relay to block it in position. Once the delivery person has passed or after a while, I deactivate the blocked opening or I make a close command to cut the stop and start closing,
• Same when I receive guests, it avoids having to reopen each time ^^
• When my partner works, a scenario « Start Speech Therapy » or « Start Hippotherapy » linked to the modes « Work Speech Therapy » or « Work Hippotherapy » starts the lighting of the rooms used as needed for the brightness as well as the blocked opening of the gate for the arrival of the patients. When she leaves these 2 modes or switches to the « Return home » mode, the gate is unlocked and closed.
• Same for our tenant with the « Work Psychomotor Therapy » mode which in addition allows to raise the separation of the charges for the common rooms.
• For the blocked closing, as I said, it’s an extra « safety » in case of prolonged absence.
• For the rest I use the normal functions Open / Open 1 leaf / Close depending on the case:
  • I have an NFC tag on the dashboard + Tasker. When I leave or come back, I put my phone on the dashboard and the command passes,
  • I receive a surprise guest, I take the first thing I have at hand, either the remote control, or the phone and I open.
  • The gate has remained open following a bug or other, I use either the remote control, or the phone and I close.
    I do not manage the gate automatically

That’s about it. So as you can see nothing complex in the end, I just detailed the possibilities of use which are counted in this number. After clearly, I use all these points permanently.

@pierre-gilles

I explain the problem: your problem comes from the fact that you have devices with many features, including duplicate binary ones.

Most integrations do not have this problem and therefore people do not even have the possibility to modify the feature names (case of Philips Hue for example)

We will have to find a hybrid solution, but not « mystical » for that matter. To think about with a clear head

On this point I do not understand. Just as we take the example of Philips Hue, on the dashboard for the moment only the lamp lighting is taken up. But we are well agreed that later we will also have the possibility to manage the color, the brightness and the temperature. Will this be directly in the same box as the lighting? If so, we will indeed take its feature name and not the device name.
Another example: currently I have a device to save the « Average Voltage and Total Intensity of the house » with 1 feature « Average House Voltage » and another « Total House Intensity ». Also 1 device for each phase (Three-phase) of the power/energy data with each 3 features: « Power Phase 2 House », « Energy Phase 2 House », « Total Energy Phase 2 House »

In image

And on the Dashboard we indeed retrieve the names of the features and not the device.

In image

It is the same for a socket or for 1 device that would contain several actions and therefore several features. For example a socket with consumption measurement. Whatever happens, if a device is configured with 1 single switch, it will not change the fact that we retrieve its device name, or that the feature name is the same as its device name. After I may have a truncated vision because I only use mainly the Arduino for my home automation. But I try to equip myself with all types of devices currently to have a more global vision.

@pierre-gilles

We will have to find a hybrid solution, but not « mystical » for that matter. To think about with a clear head

Indeed ^^ Maybe the simplest thing for everyone to find their way around and to have the most openness would be to add a button on the device card to choose whether you want to use the device name or the feature name for the disturbing cases?

[pierre-gilles]

@Terdious

I therefore connected all these contacts to an Arduino for the following need:

I added a link to your message to the GitHub card:

Create a feature category + types for "garage door"

After that, we agree, for now you can do without any problem in the MQTT service this functionality without having a native « garage door » type?

@Terdious

On this point I do not understand. Just as with the example of Philips Hue, on the dashboard for the moment only the lamp’s lighting is displayed.

What I meant is that the Philips Hue has only one feature of each type per device. A lamp has only one « binary », only one « color », only one « intensity ».

@Terdious

But we agree that later we will also have the possibility to manage the color, brightness and temperature. Will this be directly in the same box as the lighting?

It’s not said!

For example, here’s how the Philips Hue app works:

I have the list of bulbs, then when I click I see a color picker that I can modify.

• Is the Philips Hue app clear and easy to use? Yes.
• Did the developer of the Philips Hue app decide to name each feature of each Hue? No.

We need to think about the user experience.

Naming each feature doesn’t make sense everywhere, the simpler the better. There is a real high-level reflection that we will realize with each implementation, a reflection that we must do without thinking for a single second about the technique: how it works under the hood, the user doesn’t care

@Terdious

And on the Dashboard we get the names of the features and not the device.

The « binary » type is managed differently from other types of features, due to the Philips Hue integration.

In fact, as it stands, the binary type was not designed to be used multiple times in a device, but it’s not set in stone.

@Terdious

Perhaps the simplest way for everyone to find their way and to have the most openness would be to add a button on the device card to choose whether you want to use the device name or the feature name for the disturbing cases?

To be seen, I think a special case for MQTT devices is not « disturbing ». I think making a case by case by integration is the best way to have a fine integration.

I created a card:

MQTT service: In the "devices in rooms" dashboard box, display the feature name of a binary device, not the device name

[Terdious]

Hello @pierre-gilles and thanks for your feedback,

@pierre-gilles

After all, we agree, for now you manage to do without any problem in the MQTT service this operation without having a native « garage door » type?

Indeed, I did that this morning, but I took back the code and the create to create a device per command (switch) so on the Integration/MQTT/Device/Feature side, it is not practical and readable (but in the end with the search bar we find our way), but on the Dashboard side it is much better.

Integration/MQTT/Device

Dashboard

@pierre-gilles

What I meant is that Philips Hue has only one feature of each type per device. A lamp has only one « binary », only one « color », only one « intensity ».

It’s not said!

For example, here’s how the Philips Hue application works:

I have the list of bulbs, then when I click I see a color picker that I can modify.

• Is the Philips Hue application clear and easy to use? Yes.
• Has the developer of the Philips Hue application decided to name each feature of each Hue? No.

We need to think about user experience.

Indeed, I totally agree with you. In the end, it’s not the same use at all, and indeed, at least for the moment, we will only have this « issue » which is not one on the MQTT side, or at least in the « homemade » devices or those that have a particular operation.

@pierre-gilles

@Terdious

Perhaps the simplest way for everyone to find their way and to have the most openness would be to add a button on the device card to choose whether you want to use the device name or the feature name for the disturbing cases?

To be seen, I think a special case for MQTT devices is not « disturbing ». I think making a case by case by integration is the best way to have a fine integration.

Exactly !! And indeed I was talking exclusively about the MQTT integration.

@pierre-gilles

I created a card:

Top !! Thanks !!

[pierre-gilles]

@Terdious You had some issues with Gladys Plus, I investigated and found the problem: there was a cache issue with a key file of Gladys Plus (the serviceWorker, sw.js), and thus some files were not updating correctly. (The file in question: https://plus.gladysassistant.com/sw.js)

Gladys Plus is a progressive web app that works entirely locally offline, and is thus very fast to start. To update, the sw.js file intentionally has no unique ID and should not be cached by the browser.

However, by default, on Netlify, this file has a 10-day cache directive.

I fixed this, this file is no longer cached and normally the front-end update system should work again.

To test, could you clear your browser cache on the page « plus.gladysassistant.com », then reload the page? Normally this should eliminate some « mystical » bugs you had that were just due to this problem

[Terdious]

Hi @pierre-gilles,

Thank you very much for this investigation. I hope it wasn’t just time wasted for you and that it will be useful overall.

I just restarted the browser properly, it works well. I will come back here to let you know if I see things reappear, but you have clearly identified the problem, so no reason ^^

[pierre-gilles]

It took me some time, but you weren’t the only one in my opinion, so don’t worry it will be useful for everyone

[JPL]

Hello everyone
I don’t know if I’m in the right place, but Gladys 4 disconnects on its own from time to time
Then it tells me that my dashboard is not configured:

The problem is that the only solution I found is to restart the installation…
There must be a simpler way, right?
Thanks for your advice

[JPL]

It’s rather this screenshot that appears:

Thanks

[pierre-gilles]

Mmm it could be a network or Pi stability issue.

When you say:

@JPL

The problem is that the only solution I found is to reinstall…

What do you mean by that?

When you access Gladys locally (via your Pi’s IP address), does everything work?

It might be a silly question, but had you configured any boxes on your dashboard?