Is Christmas Coming Soon?

💬 Lounge
22

Honestly, I have been so busy with these classes Ive been taking lately I haven't done much with my hubs, etc since November and forgot what i was running !Good thing is the class has helped me to understand some of this better.

Even now, I have about 7 labs I need to finish up, and Just cant bring my self to focus on them at the moment.

2 Likes
23

My 20 years of being enthusiastic over being involved with Beta were over 20 years ago. Backing off of the bleeding edge has simplified the tech part of my life tremendously. I understand the attraction though. Your efforts enrich our experience. So thanks.

1 Like
24

Love the enthusiasm. Anyone have any thoughts on this "high" level plan.

  1. Take backups of current hubs
  2. Shutdown both hubs
  3. Add 3rd hub to account
  4. Restore backup from main hub to 3rd Lab Hub
  5. Immediately when getting access to 3rd hub:
  • Hardcode new IP
  • Disable ZWave & Zigbee radios
  • Removed hub mesh devices
  • Disable Hub Mesh
  • Bring hubs back up (one at a time)
  1. Does a restore also restore the HUB UID or is that a unique hardware ID (I think)?
  2. WiFi is already off so should be no issues there I don't believe??

Excited. Sometimes my tomorrow can get lined up for me the day before up until about 7pm so not sure what it is looking like. I will certainly let everyone know what progress I make at some point tomorrow :slight_smile:

Thanks,

  • Don
25

That sounds like much more work than required…

What I do (I have 4 production hubs) is:

  1. Install Beta on all hubs
  2. Do stuff on hub
  3. Report issues

If the beta is causing major issues:

  1. Restore to the previous platform version via the :8081 interfaces on all hubs (that part takes a few minutes as it needs to be repeated one hub at a time…)
  2. If necessary, restore the previous night’s backup
  3. Start using the hub as usual
2 Likes
26

Me exactly...just two prodution hubs (because I'm half as cool as you) :wink:

  1. Make sure I have both current local and cloud backups (I just feel better with both)
  2. Update to newest beta, use/observe
  3. Bounce back to previous platform if required
1 Like
27

Wouldn't you want to roll back the platform, not restore a backup?

5 Likes
28

Good morning all,

So my day did not turn out as planned. That made me realize, even if I could participate in the beta program I most likely could not participate to the degree I would like to and days could go by before I could even look at an update. Secondly, as I mentioned earlier; for the same reasons, I need reliability because right now I just don't have the time to address issues that may be introduced during beta code testing. Maybe at some point in the future. Right now is just now the right time in my life.

Don't judge me. It is where I am right now. I have identified issues in the past, took the time to right them up, and they have been corrected. I have made suggestions and some have been implemented. I contribute (or have offered) monetary contributions to those who offer their work-products that I use. I will continue to do this. Again, I always want to contribute where I can.

I absolutely appreciate all of you who take the time to participate in the Beta efforts to make the lives of us who do not. I recognize and absolutely appreciate your time and efforts. Thank you for that.

  • Don
2 Likes
29

Absolutely no judging going on. Circumstances must be right, and if they ever do line up for you, you now know where to click to jump in.

1 Like
30

Yes, absolutely correct! Now that I think of it, the backup restore would be nice in case something got corrupted, but otherwise, rolling back the platform should be all that is needed. I’ll correct my comment above for future reference…

Also, ditto to @thebearmay’s comment! We all have lives that may or may not accommodate time spent doing beta testing. :blush:

31

Good evening all,

I hope everyone’s day went well. I certainly appreciate the understanding and will continue to contribute where I can.

  • Don
2 Likes