Next HS4 Beta will include Dashboard support, please submit your requests!

[enigmatheatre]

Not really. Imagine the case where you had to re-import your Z-Wave devices. This would be many devices so a replace feature would not work. It would help if you just had one device to replace. But if it's just one device, recreating one dashboard card would not be that much work.

I think matching the name is the only way to reliably do this. HS would save the original device name when a device is first added and use this as a matching identifier. If multiple devices have the same name, this would be an issue. Z-Wave does set the address property on a device so Z-Wave devices could be replaced reliably. Same for Insteon.

I may be the only one with this situation but I have plug in switch devices that are renamed depending on there use and the time of year. They are mostly used for holiday lighting. This may cause a problem.(I could work round this but just wanted to point out a scenario)
I also have many devices that the patient is named what the device is and the child device is just called "switch" but are in different locations.

I get that changing one dashboard may be easy but if I have multiple dashboards, multiple users and many events for the device then the replace feature solved this. It may not work in its original form and might need to be a re-map devices page instead to cover multiple situations.

Just my thoughts.

[alexbk66]

I think matching the name is the only way to reliably do this. HS would save the original device name when a device is first added and use this as a matching identifier. If multiple devices have the same name, this would be an issue. Z-Wave does set the address property on a device so Z-Wave devices could be replaced reliably. Same for Insteon.

I think better option is to allow only the root (parent) selection, but the children/features select by type. This way if the whole root is re-created - then the user will need to select only the new root. If only features are re-created (what I usually do) - then nothing needs to change at all.

In case of multiple features of the same type - also use the index.

[ksum]

I may be the only one with this situation but I have plug in switch devices that are renamed depending on there use and the time of year. They are mostly used for holiday lighting. This may cause a problem.(I could work round this but just wanted to point out a scenario)
I also have many devices that the patient is named what the device is and the child device is just called "switch" but are in different locations.

I get that changing one dashboard may be easy but if I have multiple dashboards, multiple users and many events for the device then the replace feature solved this. It may not work in its original form and might need to be a re-map devices page instead to cover multiple situations.

Just my thoughts.

My Device Names also change from time to time as many of my devices can change locations and use. For those which do this often, I keep the name generic. I do have a habit of getting a new device to see how/how well it works and then rename it later if put into use. In this last case I would not include it in a custom dashboard until moved.
All this said, I can see changing these Generic Device Names in the Dashboard itself for better WAF. For instance, I have 2 z-wave power strips with each of the 6 outlets being controllable. On a dashboard I may want to label Christmas Tree Lights for one when the tree is up, but the same outlet controls some Halloween display prior to that. I would not need to change these in HomeSeer provided I could change it on the Dashboard. In this example, these are on a Child level. I can see the same happening on a Parent level. Currently I have a 4 button arduino "remote control" box which just sends MQTT commands and currently allow her to manually control these things with that by connecting it with the device via an event. I can see her asking for these on a dashboard, though.

[ksum]

Yes! Dashboards are HTML and responsive. When viewed on a smaller screen the cards stack.

I have a 15" Fire tablet and Amazon made changes so cannot side load apps. I am working on getting HSTouch to work from the App store but you can display web pages on it and there is a trick to force them to stay open. So web dashboards will display nicely there.

There are a few Kiosk apps in the Google Play store. I may be looking at the Fully Kiosk Browser & Lockdown to show this on a tablet as it has the ability to have the screen display turn on based on motion. It would meet most of my needs. If only I could use it on my Google/Nest Hubs.

[rjh]

The problem with this is that some plugins use the same type for all the features. For example, our TUYA plugin names the type as "API Feature", so there is no way to distinguish between them. I really need a unique identifier for each feature. What I am proposing is that when a device is added the name is copied to a new property in the device. This property cannot be changed. This way the user can change the name but if they import the device again, I will know how to match up all the features to the original features. Obviously, this will only work going forward. For Z-Wave devices (or any device with the address populated) I can use the address and if the type is unique, I could use that also. And yes, the index would be the last choice.

I think better option is to allow only the root (parent) selection, but the children/features select by type. This way if the whole root is re-created - then the user will need to select only the new root. If only features are re-created (what I usually do) - then nothing needs to change at all.

In case of multiple features of the same type - also use the index.

[Dewcal]

There are a few Kiosk apps in the Google Play store. I may be looking at the Fully Kiosk Browser & Lockdown to show this on a tablet as it has the ability to have the screen display turn on based on motion. It would meet most of my needs. If only I could use it on my Google/Nest Hubs.

+1 for Fully Kiosk Browser

[kenm]

+1 for Fully Kiosk Browser

Another +1 for Fully Kiosk Browser. ksum The motion control feature is a PLUS feature so it isn't available in the free version. Well technically it is for testing, but they put a watermark across the screen reminding you to buy the PLUS version.

[Dewcal]

Another +1 for Fully Kiosk Browser. ksum The motion control feature is a PLUS feature so it isn't available in the free version. Well technically it is for testing, but they put a watermark across the screen reminding you to buy the PLUS version.

True, you do have to pay for the PLUS version - a little less than 8 Euros if memory is correct. No doubt the price will increase!

[ksum]

You are both correct, kenm and Dewcal regarding a cost for the motion and the need to pay for the PLUS version. That is what the Google Opinion Rewards app is for. Answer occasional questions and build up your Play balance to get apps like this. It is a 1 time fee of 8.99 USD.

[ksum]

Are Widgets for mobile devices being considered either in conjunction with the Dashboard or otherwise?

[mik3]

When does this come out?

Hopefully it’s better then the mobile app, and allows you to customize the square boxes better.

[rmiles7721]

There are a few Kiosk apps in the Google Play store. I may be looking at the Fully Kiosk Browser & Lockdown to show this on a tablet as it has the ability to have the screen display turn on based on motion. It would meet most of my needs. If only I could use it on my Google/Nest Hubs.

That's what I currently use on my fire tablets a couple of places in the house. Works pretty well.

[wimaware]

why reinvent the wheel? Try working together with HSBuddy a mobile app and a dashboard editor all under one roof. Great app.

[rjh]

A quick update here. Work on this is being paused for a bit as I move over to finish the firmware on the PS100 mmwave sensor. That is almost done. I also need to fix a few issues with the new MyHS UI refresh. That should be done in a few days, and we will post for users to test. Then back on the dashboards.

[mik3]

A quick update here. Work on this is being paused for a bit as I move over to finish the firmware on the PS100 mmwave sensor. That is almost done. I also need to fix a few issues with the new MyHS UI refresh. That should be done in a few days, and we will post for users to test. Then back on the dashboards.

Appreciate the update.