I’ve been diving into the world of Z-Wave devices lately and came across an interesting observation regarding firmware version reporting. It seems like the firmware version structure has changed, with values now appearing in firmware0Version and firmware0SubVersion instead of the previously used applicationVersion and applicationSubVersion. I’m curious if this is intentional or if it might be a bug that needs addressing in our drivers. Has anyone else noticed this change or have insights on how to handle it moving forward?
Speaking of devices, I’ve been trying to pair an Iris leak sensor from an older hub to a newer one. It consistently hangs at the ‘Initializing’ stage, which is quite frustrating. I’ve attempted multiple resets and reboots, but no luck so far. If anyone has successfully paired an Iris sensor to a newer hub, I’d love to hear about any tricks or workarounds you might have discovered!
On a more positive note, I recently set up a routine on my Amazon Echo Show 5 to turn off both the audio and the screen in one go. While the audio part works seamlessly, the screen only dims to show the clock instead of turning off completely. It’s a minor inconvenience, but I’m hopeful there’s a tweak or a workaround to make it fully functional. I’ve reached out to the community for suggestions and am eager to see if we can crack this together.
Lastly, I wanted to share a success story. After some trial and error, I managed to integrate my VERA2 with my SquareConnect Remote+Blaster, allowing me to control my home theater system wirelessly. It required setting up a static IP and configuring the network settings, but the end result has been worth the effort. If anyone else is looking to do something similar, I’m happy to walk through the steps I took!
Let’s keep the discussions flowing and help each other tackle these smart home challenges. Happy tinkering everyone!