Bumbershoot

My i3 Dial doesn't send updates to the AC when the state is changed manually, but it does update appropriately when the state is changed in the AC. The release notes indicated "initial support". It's not all the way there yet. EDIT: Nothing appears in the Event Viewer when the device state is manually changed. I choose to understand that "initial support" indicates that it's likely that these switches are now safe to purchase. 🙃

@JP, you can always send an email to support@universal-devices.com

In the last year, the temperature has varied over 100°F (-6°F to 103°F). My Tempest soldiered on through it all.

@vbPhil, here's another choice. I've been using gear from these folks for years, and it's always proven to be accurate and reliable. Below is an example, useful if you want to want to monitor your cook from the party down the block: https://www.thermoworks.com/smoke-x/ This also has a controllable fan: https://www.thermoworks.com/billows/ Here are available software packages for these devices (I'm still stuck in the analog phase of bbq monitoring - I hang around and watch, so I don't use any of these): https://www.thermoworks.com/software/

FWIW, dealing with WeatherFlow has been a very good experience. I had an early Tempest fail, and they shipped me a new unit quickly, free of charge (return shipping for the defective unit was included). They can also run diagnostics on these units remotely, as the hub is connected to the Internet. FWIW, the haptic rain sensor doesn't capture snow at all.

Sorry, I missed your thread about this. I've never seen this behavior, though I'll look for it. I have one where parameter 3 is set to 1 (motion sensor in manual mode), and it shares a junction box with a Homeseer Z-Wave dimmer. I use the seven Homeseer LED's as security sentinels (colors change as external doors open and close), so I'm changing parameters on that switch frequently. I'll look in the logs for motion activation when I write to the Homeseer. I have two other switches in their own junction boxes and they work very reliably. There's new firmware, but it doesn't address the issue you're describing. https://github.com/jascoproducts/firmware/tree/main/zwave/Enbrighten-GE/ZW4006/26931 - In-Wall Motion Switch%2C 500S/5.39

I understand. Mine were so-so as well, until I adjusted the motion sensitivity up to "High". That fixed it for my purposes.

This isn't OpenHab related, but what you're seeing is normal for those devices. See this link:

No, he just said that UDI has samples and documentation, and that they intend on supporting it. Nothing about which UDI platform, but since ISY994i is EOL, I doubt they'll support it there.

Like the i3 Dial, the i3 Paddle can be used as either an on/off switch or a dimmer. I hope light almond will be available...

Ken said that ISY will support the new i3 Paddle, which should be available next week. EDIT: I don't know if this link will work: https://us02web.zoom.us/rec/play/zuI1PTw_DxoCA1r1y097HYR5tkWlneU_PZjitbH2EqpV6ALLpPEb95_c_I1bKiuz9Ob8iBIQs5BNNCmX.P5J_-M_XWF9TSxgQ?startTime=1676663973000&_x_zm_rtaid=OdopTLzVQ4SnCkRoLT9Lnw.1676728532099.b153b0b239f9c5ca527bd3db2549b934&_x_zm_rhtaid=545 Passcode is: VkL0*x?d

They're not the best looking things in the world, but they're fairly configurable and very reliable. I have some in occupancy mode - where they turn on the attached load, and others in manual mode - where they send a motion signal to IoX but don't turn on the load. They respond very quickly to motion, I've found. I wish Insteon would produce something like these. I really prefer Insteon for lighting, and they make a motion sensor...

These use Z-Wave, but in the latest IoX firmware (5.5.6 currently), these switches/dimmers work fine. They aren't the latest/greatest Z-Wave version, however. https://www.amazon.com/GE-Occupancy-Required-SmartThings-26931/dp/B07226MG2T/ref=asc_df_B07226MG2T?tag=bngsmtphsnus-20&linkCode=df0&hvadid=80745502739840&hvnetw=s&hvqmt=e&hvbmt=be&hvdev=c&hvlocint=&hvlocphy=&hvtargid=pla-4584345029627392&psc=1

This is just a guess, but my eisy responds when the URL to look like this: wss://<ip address>:8443/rest/subscribe

Here's what the variable substitution value looks like for an ECOWITT moisture sensor: ${sys.node.n005_wh51_1.ST} You can click on the "Nodes" button on your node server to see the values for each device. Below are the possible values for the moisture sensor:

FWIW, I’ve never seen battery status, on Z-Wave 300, 500, 700 or Zmatter. I change them once a year, same as smoke alarm batteries. No issues so far.

I've run into this a couple of times, and this trick has always worked. Navigate to the Node Server Store, click on your Tesla node server button, then the Install button. A pop-up window will appear, and about midway down, there will be a notice that will tell you that the node server is already installed, and a button that says "Reinstall here" will appear. Use that button, and the new version will be installed over the top of your original installation, with no disruption to your programs, etc.

@Chris Jahn, my GoControl garage door openers are now operating normally and reporting status. All other Z-Wave devices are operating correctly as well, as far as I have tested. I didn't migrate, however. I excluded on my Polisy and included them on my eisy. My Z-Wave network isn't all that extensive.

I'm not trying to be a jerk, but when you start working with libraries, package managers, file layouts, etc., it can be, and some of the solutions in this thread are wandering into that territory. But for the most part, it doesn't practically matter.

FreeBSD gents, not Linux. Lots of similarities, lots of differences.

I don't know what's going on here, but if you start reading at the post linked to below, you might see what has been happening: The solution in my case was to issue the following command at the command line: sudo service udx restart

If you're on a Polisy and know how to ssh into the box, then this worked for me yesterday: sudo service udx restart There's an upstream package associated with MongoDB that breaks things, and that has caused this problem for UDI and Polisy/eisy users. You might start reading at this post for more information:

This is on my eisy: I can't tell you when the updates were released to the repositories, but PG3x was upgraded on my machine to 3.1.22_3 on Feb. 8th in the afternoon. Again, on my machine only, IoX was upgraded from 5.5.5_1 to 5.5.5_2 on the morning of Feb. 6th. I never saw any release notes, so I don't know if anything interesting to the user community was fixed/changes. The updates could simply be due to compatibility reasons with other packages. UDX gets fairly frequent updates, and I've never seen release notes for that. I suspect UDI prefers to keep that secret sauce to itself.

Give restarting udx a try in you're comfortable at the command line: sudo service udx restart

Back up and running on both Polisy and eisy. sudo service udx restart