Goose66

@JBalog Was this resolved? Also, did you delete and rediscover your devices after installing the update?

Does the Bond Home app show more commands than just Open or Close? Also, what is the device type up at the top of the node details in the Admin Console? A Shade should never show “On” or “Off,” but “Open” and “Close” (at a minimum). Adding a screen grab from the Admin Console would be helpful.

The docs suggest it may be a Pro only thing, but you can try deleting and re-discovering your shades to see if they show up as having position support.

I’ll take care of this in the patch. Let’s see what else shakes out this week.

Do you have a Bond Bridge Pro?

Look here:

Look here:

A new version v3.3.15 of the Bond plugin has been uploaded. This version adds enhanced support for shades (see below) and adds the ability to restart the BPUP listener thread and connection to the bridge if it fails for some reason, e.g., network troubles or power loss affecting the Bond bridge but not IoX/PG3. I have no real way to test these changes since I don't have any shades, so before I update all the documentation for this plugin, if a few of you (e.g., @tlightne and @JBalog) can bang on it for a few days and let me know what isn't work, that would be great. I can roll out a patch to fix any issues before updating the Release Notes. This version adds several commands to basic Shade nodes: Start Opening, Start Closing, Stop (Hold), Toggle Opening, and Preset Opening. The "Stop (Hold)" command stops the shade when in motion from an open or close command. Because most if not all shades have no way to report position back to the bridge, then status generally changes to "Open" when the "Stop (Hold)" command is used. "Toggle Opening" is pretty straight forward. "Preset Opening" opens the shade to a preset level (set by the shade remote) and is referred to in bond as "My" for some shades. These commands may or may not work for different shades, and if one doesn't work, a Warning may show up in your plugin log. On some shades, if the "Stop (Hold)" command is issued when the shade is not in motion, the "Preset" functionality is invoked (the likely case when the remote only has one button to perform both functions). "Start Opening" and "Start Closing" just call open and close, respectively. However, "Start Opening," "Start Closing," and "Stop (Hold)" map to FDUP, FDDOWN, and FDSTOP IoX commands, respectively. So the theory is you can drop a shade into a IoX scene with a Insteon SwitchLinc, and get easy control: tap top of switch to open; tap bottom of switch to close, press and hold top of switch to start opening, release switch to stop opening, etc., all without programming. If anybody can test this, that would be great. For shades that support positioning, there is a new Shade node that adds a "Set Position" command along with "Increase Opening" and "Decrease Opening" commands that increase or decrease opening by 10%. This node also reports the position as a percentage if not fully "Open" or "Closed." Several Notes: The Bond Home app and Bond API report position as a percentage of "closed," i.e., 0% is open and 100% is closed. IoX "Barrier Status" UOM reports position as a percentage of "open," i.e., 0% is closed and 100% is open. The conversion is done in the plugin so you should keep this in mind. If you have a shade that supports "Set Position" commands, either because it's native to the shade or you've set the "Course Time" in the Bond Home app for the shade and the Bond Bridge Pro is tracking it's position, then you will need to delete the existing shade nodes and the re-discover nodes from the bridge to get them to load with the right node definition. Let me know what works and what doesn't.

Coming in next release.

Ok. Anything else? Anyone? Bueller?

Here are a couple things to try right off the bat: 1. Try navigating to http://isy in a browser. If the version of IoX (the OS/firmware on the ISY994) is older, you might get lucky! 2. Login to your network's router or other device providing DHCP on your LAN and look for a device with a name such as "isy..." or a MAC address matching the MAC address on the bottom of your ISY. Try using that IP address to navigate to http://<ipaddress> or http://<ipaddress>:8080. If either of those work, you can try to login with admin/admin credentials. If you have Java installed, you can launch the Admin Console from those webpages.

What plugin?

I can't speak for MyQ doors, but it is very stable for my dry-contact Genie doors. Never had an accidental opening or anything like that.

No that’s what I meant. At least on the Martin Jerry Tasmota devices, if you use %topic% in a rule, it is replaced with whatever is specified for “Topic” in the MQTT configuration.

Does "tasmota/stat/%topic%/STATE" work instead of having the actual name of the device in there? If that works, and you post back the exact rules that you used, I can make the Tasmota Plugin configure the HPSensor devices with those rules upon discovery. I need to roll out a new version to fix the failure on bad MQTT data that we found while debugging this.