Thanks for catching that bug in presets. It should be storing 0-100 for speed (or 99). I actually just changed how they were handled in the last version, and will get that fixed in 0.87.
Infinite thanks to Chuck for pointing that hint out in another thread
No specifics. I think it’s moreso just a general error I have in the scheduling or socket routines. If you haven’t seen any slowness yet, I’d imagine you’ll be ok with one more.
Hey Adam weird issues lost control of led single color dimmer . From HE dashboard no issues . But pico remote lost functional use to control it. Lost group control also.
I'm testing my "wonkiness" and am suspecting it might be the unfortunate coincidence of a couple of unrelated devices going low-battery at the same time. Possibly/probably not 0.86. Willl advise.
Nope weird CW Bulb controller shows up as dimmer not as bulb. I have lost Dimming via pico remotes no matter which way i assign them in HE on CW Bulb or Dimmable controller and regular RGB.
Did this end up being part of your implementation or part of the websockets implementation? Are you still getting slowdowns while using an active websocket client?
The other short answer is that the new version offers telnet OR socket. I’m working with staff to debug what the actual issue is. Telnet doesn’t slow down, but the routine flow is a little different between the two.
Okay, cool. The reason I'm wondering is because I'm trying to pinpoint some slowdown behavior as you've explained and an eventual crash (just one time). I haven't determined for sure what is causing the slowdown but at this point I have only drivers with a websocket implementation disabled and my hub has been fantastically stable.
Please continue to update this thread if you find any fixes or problems.
def setLevel(level) {
// Set the brightness of a device (0-100)
level > 100 ? (level = 100) : null
sendEvent(name: "level", value: level)
logDebug "Level set to ${level}"
Ogiewon's Logitech integration. Again, I don't know for sure if it's websockets or if my hub just hasn't been up long enough since the last slowdown and crash. I'm only at about 36 hours uptime. Or if it's just that these extra devices are pushing the hub to its limit. I don't have any automations with the Logitech or Magic Home devices so they really shouldn't be adding much load especially idle. They are mostly for control and consolidation so that everything is in one place.
I was having slowdowns usually within 24 hours and they would get gradually worse until I had 2 and 3 second response times to any automation. I'm guessing I didn't catch one in time and that's why the hub went down.
Anyway, I'm trying to isolate the cause and the next few days should be very telling hopefully.
I received my development hub today. I’ve got ~20 MagicHome devices with the new driver running on my home hub with over 100 hours of uptime. First reboot was last night with a developer update. I’m gonna keep working on it and aim for a release in the next couple days
Hm? There’s only one call in there. SendEvent(...) is a status write to the database only. I’ll take a look at it and triple check there’s nothing recursive, but that’s the practiced method to write this.
Keep me in the loop.
