Z-Wave Join V2: The hub will now attempt to complete secure inclusion (if necessary) and collect all necessary info about a Z-Wave device before sending it up to the cloud. This prevents device configuration problems caused by this activity interfering with the configuration commands that the device handler sends.
Partially fixed an issue causing the Z-Wave module to fail on startup when it has a problematic device record
LAN
Fixed a race case in LAN handling where bytes would not always be read before closing the connection resulting in truncated messages to the cloud
Video
Improvements to local video processing engine
Improved reliability of video clip generation with Smart Home Monitor
Join v2 collects manufacturer, model, and version info before creating the device record in the cloud. The cloud changes necessary to make this information available to device handlers ā including for fingerprinting ā is complete but still in testing. Iāll be letting you guys know more about how to use that when itās ready.
You can tell a Z-Wave device was joined with the new join v2 by looking at its device details in graph ā the Raw Description field will look like something like this:
For the zw: part, S means sleepy, L means repeater, and F means beamable battery-powered device. There will be a small āsā after if the device is using Z-Wave Security.
Lots of those changes would seem to apply for v1 hubs as well. It has been previously stated that v1 are still supported and will receive FW updates as well.
Any guess on when all those old and faithful customers/early adapters can expect fixes for their hub?
Ok, received hub update, and ALL IS WELLā¦ kinda.
So after the update all my z-wave motion sensors were stuck in motion and wouldnāt refresh. A network repair also wouldnāt fix it. I randomly opened one of the doors with a z-wave door sensor and lo and behold, all the motion sensors refreshed and updated their status properly.
Very weird but no other issues and everything is normal.
i seems to be ok. things look to be working so farā¦so this wont help the sonos affecting zwave issue. but on a plus side it does fix the Issues i was seeing with the @pstuartās Genric Camera stuff. pictures just now work
How was sonos affecting zwave devices? Upon leaving our home (based on presence sensors) I have our 4 Schlage locks lock the doors but there have been issues since day one. Many times, it fails to lock at least one of the doors. Iāve been dealing with support for close to 2 years now and they cannot figure out the issue. Wondering if itās interference with Sonos. How do I test this?
I tried with just 1 and was still having issue there. All though not as frequently. But I also wanted notifications on all my Sonos devices. Which I now have achieved via another method . But would love to go back to the integrated solution
Any easy way to rejoin all these to update that info? Alll mine still show the old raw data. Be neat to explicitly see the sleepy, repeater, beamable status, like that.
DLNA stands for āDigital Living Network Alliance.ā This trade group, created by Sony, certifies networked media devices as āDLNA compliant.ā Networked media devices include game consoles, home theater systems, speakers, storage devices, and smartphones. Software can also be DLNA-certified ā Windows Media Player can use DLNA to communicate with other networked media devicesā¦[/quote]
There isnāt yet, sorry. Weāre planning to add that, not sure when.
Basically, if it runs on a battery itās sleepy unless it needs to respond to commands (like a lock or siren), then itās beamable. If itās plugged in, itās a repeater.
One of those things we just have to learn to live with I guess. I forgot about the update and tried to use my system as per usual during the upgrade. I normally leave it alone. Probably broke because I was in the middle of updating some apps at the same time.
My one camera lone camera no longer works, it doesnāt stream in the app, and doesnāt appear to record video. Everything worked until the update. A ticket is open.
Edit: No response to the ticket but the camera is working again, and connects much faster than before. Nice job!