Summary of this thread:
1.
I , as the OP have a problem with cloud access. I am not sure if it is reproducable or intermittent. I will check if a reboot of router reproduces the problem when I am back from vacation.
2.
There are other people with clod access issues. One user says it is reproducable by a router reboot. These issues might be same issue, or not. Even if I can't reproduce with a router reboot, it does not mean my issue is different or same. Maybe my router reboot does not trigger but a WAN link down triggers. We don't know.
3.
In any case there is a problem affecting at least 3 people (maybe more if they would use/check frequently) about cloud access. And in my case this started after several years of use, all of a sudden but certainly after a hub update.
4.
In any case, it needs to be analyzed by Hubitat staff. As users, we can not know how Hubitat cloud works and we can not provide our own solutions. Even if it is a network/router issue on user side, the root cause must be identified by Hubitat staff and then maybe we can find individual solutions on our side. But considering this probably started after a hub update, solution must also come from Hubitat.
5.
We still see that Hubitat staff is not interested in this as much as they should be.
6.
We see that some group of users with a forum rank of "ambassador" blindly defends Hubitat staff as if they are Hubitat staff. (maybe they are ?)
7.
I, as the OP, was suggested to open a ticket. I asked how to open a ticket. (because I know I can't)
The suggested way is clicking "warranty" on the web site. But there I read :
A claim can only be made if the hub was purchased within the past 90 days from hubitat.com or on amazon.com.
When I write this back here, I get no more suggestions.
I, as the OP have a separate issue that I am trying to follow up with Hubitat staff. The problem is accepted by Hubitat staff and I am not able to make use of a C8 hub that I had purchased 8 months ago. I can't receive updates about this issue for the last 2 months.
There is a certain solution of replacing my C8 hub with a C7 hub (because I know C7 is working with my devices) , this is being avoided by Hubitat staff for the last 2-3 months.
This issue was referred to here and I was accused by an "ambassador" with ridiculous statements.
This post may be hidden by "ambassadors" because they won't like it.
How would Hubitat staff have identified and fixed an issue related to a single userās networking equipment configuration?
You seem convinced that there is an underlying issue with the hub itself and that you have no responsibility to continue troubleshooting your own environment til youāve ruled out the more likely possibility that itās something specific that hasnāt been identified yet.
That seems like an approach destined for failure, or waiting a really long time for someone else to figure out a solution for you.
Based on what? Do have info of behind the scenes activities and discussions that we aren't aware of?
Nope. We harp on staff as much as anyone else. We're simply here to try and help people. Once they become belligerent and combative and insulting we tend to just lay off the original subject and start shrugging our shoulders because people like that tend to only want to be insulting and combative.
And you can still do it outside of the 90 day period and someone would contact you. That said, the primary support person is going on vacation this week so responses now since you didn't turn in a ticket may be more delayed if you do turn in one.
They are only hidden when name calling or insults are involved. Anyone who is polite doesn't get their post hidden. Though it's getting close to this thread running it's course.
As a side note there is an old saying. "Tatlı dil yılanı deliÄinden Ƨıkarır." which translates to "Turneth away wrath" or more colloquially You can catch more flies with honey than with vinegar". More people need to understand this. Everyone is here to help eachother.
we can't be sure if that really solved the issue until the user monitors his hub for a while and confirms it resolved.
In any case, I don't have that setting on my router. And I'm saying that I did not have this issue for several years until an update. Even if could be resolved with a setting on my router, somebody should explain why I need that setting after several "good working" years.
they could have checked the logs.
they could analyze what has been changed on Hubitat side (hub and/or cloud) recenntly.
"At least" they could respond ???
I donāt think youāre following what Iām saying.
Iām not suggesting @bob20ās problem and your problem have the same solution.
Iām suggesting the opposite. Because they are probably totally unrelated issues.
@bob20ās issue appears to have had nothing to do with Hubitat cloud services. It was a setting on his Cisco switch and thereās no good reason why Hubitat could have offered up that diagnosis or solution for him. He figured it out by troubleshooting.
The underlying cause for your issues have yet to be worked out. You (and you alone) may still have the key to answering it.
I never said there is an issue with the hub. All I'm saying is that I started having issues. Maybe hub, maybe update, maybe cloud...
And I never said that I won't continue trobleshooting. If someone from Hubitat had accepted to work on this, I could provide whatever is requested from me.
I am just on vacation so I can't contribute for a few weeks. But of course I would try my best to troubleshoot if someone works on this with me.
there is no way to open a ticket. There is no response from staff here. What can I do ?
well now you accuse me with being insulting and combative ?
how's that ?
You are saying "insulting" because of what I said to you as response to your accusation of me with 2 things that I did not do. You wrote those without even deeply reading what I wrote.
Combative ? Because I am looking for help through a company which does not really offer help.
You are really interesting people.
Look, Hubitat is a commercial company with resources. They have a technical staff (at least I assume so)
I am an individual user. I am looking for help. But I can't get help from Hubitat.
I am being ignored. As in the other case that I am trying to get a solution.
that case is being ignored as you see.
We took it here. then @bobbyD (some real person from Hubitat staff) jumped in to correct me.
And then when I said the reality, it is again ignored.
If you put yourself in my shoes , you would understand how frustrated I am. But that is impossible for you...
Ok, then just leave it as it is. I am not seeking your help.
how are you so certain about that ?
AFAIK, @bob20 did not tell when his problem started. (maybe he did, and I missed it)
maybe it was working fine with that setting a few months ago. And after an update he had the problem and that setting saved his situation. I don't have that setting. Now do I have to get a Cisco router ?
hah now it is a tirade. this is really getting interesting. I thought this was a community forum which users help eachother. But no, every user is a competitor to the other...
interesting really.
You seem to be having more trouble fostering a sense of community than anyone else in this thread.
Since this is a problem that occurred about 20 days ago and apparently hasnāt recurred since, plus you arenāt even at home to continue troubleshooting from your end, I think you should consider letting this go til you get back home.
for some time, I don't observe this issue with cloud access.
Now I can call "this is resolved for me".
But we don't know the root cause and we don't know how it was resolved.
Should we leave it as it is ?
I mean, even if it is resolved , nobody (including Hubitat staff) wonders why this happened ?
well in fact seeing the problem is gone for me I had not written anything to this thread for a long time until other users (@peterbransche , @user6041 , @kahn-hubitat and @bob20) started reporting issues.
Then I wrote again because even if the problem is gone for me, I would like to understand why it started , what has changed.
In fact, I suspect that the problem started with an update and it was resolved with another update. Maybe they (hubitat staff) are aware and they resolved it consciously, maybe they didn't even notice and was resolved on luck.
In both cases, I still believe we need an explanation.
But Hubitat (as a company) does not like acknowledging issues.
So we will never know. And since nobody is on my side, I will not get anywhere with this. I give up.
Also my other issue, as ignored, can't do anything about it.
Nonsense. They acknowledge and resolve issues all the time. Sometimes users report problems in a way that is impossible to replicate. Those are harder to acknowledge, because the āissueā has not yet been defined.
Maybe itās time to close this thread then. If you run into recurrent problems with your hubās cloud connectivity, please send a PM to the @moderators group and one of them can consider unlocking this thread.
