Even still I am in Shock. In June I was told I would more likely see SMTP support before my own SSL cert.
Now you have SOLID proof that Hubitat shouldn't discuss their plans.
It always leads to this... someone treats 'weasel words' as some variety of 'truth.' 
2 Likes
Adding my own cert is a huge step in the right direction...and let me rephrase..I was told I would more likely see SMTP as a feature than HTTPS certs!
And what seems to be nagging at me is I was basically being told this would not happen/is at the bottom of the priority list at about the same time that this would have been introduced to the beta team. So what could have been said is "this is a feature in beta that has had some issues we aren't ready to overcome"
But was instead told
All the while a Key part of what I am looking for is a "Secret Feature"
I don't think this is quite fair as it often isn't like that. In the beta I think something else came up that forced their hand. Also as I work with R&D people it usually goes like this. Ask the management can be have this " no we don't have time for that and their time is too valuable", then when talking to R&D about something else connected, I mention it as a possible tag on or fix for another solution. "Probably not but I'm looking at this at this soon" week later " I was doing this and actually it was 5 mins to put that in so do you want to test it?" Sometimes things are easier than first thought and others are harder. Always ask politely and don't be annoyed if it's a no. They have lots going on and if they can do it they will try.
2 Likes
Ah man, there are only about 12 million moving parts. It's a fluid project, always has been, and probably will continue to be. The unexpected is always lurking.... And, the left hand does not always know what the right hand is up to. Nature of the beast.
BTW, the security restructure of Dashboards will be going to beta with the 2.2.4 release (barring the unforeseen)...
9 Likes
It seems as if you're offended that the truth as told on one day isn't the same truth as told on a different day. My point being, BOTH can be true. You did not get lied to. You were told an accurate evaluation and then, something happened and now, that old truth is replaced by a new truth.
6 Likes
I know am probably the “vocal minority” on a lot of these features....but I don’t think I was the first or only one ever ask for them.
I know there is good and bad in having public roadmaps. And it’s not my company so I not going to tell them how to “fix” it.
I appreciate the candor from you Bruce.
Also super stoked to see what holes I can punch in the new dashboard security! 
I think there is more bad than good for a private company in publishing public roadmaps.... But that's MY opinion. Prioritization often includes internal project and strategy needs that can't be made public, so you get into a never ending circle of "why is this before that" which can't be answered by the company.
Open source? Sure publish away. They can always say "if you want it faster, then contribute", or "well you got what you paid for". 
2 Likes
I was blindsided by the HTTPS implementation. It was on the list for a long time to get done, but had gone unaddressed for a long time too. Then one day, it was there. Ironically, we have really beefed up our project management over the past few months, and it slipped past that also.
As for email from the platform, that is not currently in development, afaik.
1 Like
Again thanks for the candor. I know that I have been critical for HE and the security in the past. And will probably continue to due so.
Please keep in mind that I would honestly rather see these things fixed than move platforms.
Yeah, well Dashboard clearly was not thought through well from a security perspective. But, at the time it was done, we badly needed something, and it filled that need. Time goes on, its inadequacies become clear --> it gets fixed. And it gets enhanced. New feature will directly support giving out guest specific Dashboards, with limited and revocable access.
13 Likes
Cats outa the bag now!
@anon81541053 @Hasty1 if memory serves me the reason why the HTTPS didn't get publicized and listed as non-beta was there was a bug where if you put in a bad cert, you could semi-brick your hub (or at least the HTTPS portion, I don't recall exactly because when I heard of the bug I wasn't exactly intending to try it). So now that it's been publicized, keep in mind that risk when you're using something that wasn't released!
1 Like
I would prefer some time to look at it and vouch for it before it's widely used. This feature hasn't even gone through internal testing. For all I know enabling it makes the hub emit invisible sounds that compel your dog to go and eat all the left shoes in the house. I'll give it a priority tomorrow.
16 Likes
This was not exactly my intention to force your hand on this with the other thread. I trust that the people here understand these risks!
I'll take the risk. He has already eaten half of the right shoes in our house..... 
1 Like
Didn't find any issues with HTTPS setup, so fire away. Let's call it an extended beta.
To set up HTTPS, go to http://your.hubs.ip.here/hub/advanced/certificate, copy/paste certificate/private key and save. Once saved, reboot the hub for the setting to take effect.
There's an option of SSL only on the screen. I suggest testing HTTPS connection before turning it on.
If something doesn't work, you can disable SSL by going directly to http://your.hubs.ip.here/hub/advanced/disablessl. You should be able to access the UI using plain HTTP right away.
If that doesn't work for some reason, the next option is soft reset in diagnostics tool, followed by reboot, followed by backup restore. All HTTPS settings are stored in the database.
13 Likes
I am assuming the disablessl url allows both ssl and http to work again?
Does this also reset back to the default cert?
DisableSSL URL turns off the "Hub UI SSL only" setting so that HTTP is enabled again. That's it, the URL doesn't do anything else.
3 Likes
