apnar

I’ll also throw in a me too here, neither vm-public or tap interfaces are UP on boot. Disabling udx and isy “fixes” the issue. Took a look at the udx start up scripts and didn’t see anything obvious (although I did see some stuff that rewrites rc.conf which could potentially be problematic down the line, although I didn’t trace back what calls it).

I suspect that this will be an issue for anyone with a zpool beyond the default eisy one(zudi). So folks that still boot from eMMC and add a drive, folks that mirror or boot from NVME and added an extra pool. Basically anyone that has an extra zpool (most likely called /storage). Easy enough to test, just reboot and see if /storage is there (or visible is in “zpool status”). Should be no harm in creating the directory: “sudo mkdir /etc/zfs” You may need to do a “sudo zpool export storage” then “sudo zpool import storage” to then get the correct cache file created once the directory is there.

FYI, to get out of "ha" prompt and down to real OS you can run "login". That will drop you to a proper linux prompt in the HA OS.

@Michel Kohanim Ran into another small issue. On reboots my zfs pool /storage wasn't mounting automatically. It worked fine if I did a "zpool import storage" after boot. I tracked down the issue to a missing /etc/zfs directory which stopped the creation of the normal zpool.cache file. It's possible that it's something I missed in my manual steps recovering from the issue above but I don't see it created in any of the scripts. So I'd suggest adding a line to the scripts somewhere to creates /etc/zfs.

I don’t know about hot swapping but I’ve used the Zwave half with HA before and see no reason why the Zigbee half would t work as well.

@Michel Kohanim Just ran through the new easy way. Ran into an error which I tracked down. Sort of my own fault but I think you could improve the script a bit to avoid it. The prompt reads: Would you like to add an extra ZFS partition for your own purposes? (Y/n) As a regular *nix user I read this to be there are two choices yes or no and that yes is the default since it is capitalized. As such I just hit Enter to accept the default since that is what I wanted to do. This resulted in the following error: [: =: unexpected operator Checking the code is because the check on the result isn't properly in quotes. It also ended up giving a result opposite to what I wanted. Luckily the rest of the script continues on smoothly, just without creating the extra partition. I was able to go back, manually remove the partitions and recreate them as the script would have, just a bit of annoyance and likely outside the skill set of many. TLDR; I suggest changing line 352 in /usr/local/etc/udx.d/static/fl.ops from: if [ $answer = "Y" ] to something like: if [ "$answer" = "Y" ] || [ "$answer" = "y" ] || [ "$answer" = "" ] and while all the other questions in the script do properly quote $answer I'd be worth updating them to handle both cases as well as enter for accepting the default.

Micheal, Love that we now have a supported way to use NVME, thank you! I’d like to see an intermediate option between the mirror and no-mirror options, as I want the speed of the later with the protections of the former. I think this could be accomplished well with an asynchronous “mirror” that syncs a couple times a day. If my drive does fail I’d much rather have a backup from some time in the last 24 hours as opposed to nothing, especially since there aren’t a lot of changes happening on my eisy. Since you’re using ZFS this should be reasonably easy to accomplish using ZFS send/receive. At whatever scheduled time you take a snapshot of the NVME drive and send it to the eMMC, then delete the snapshot from the previous run. Could be a simple script you guys whip up or leverage something like zrepl or sanoid. Thanks for considering!

I’d love to be able to firmware update all my devices to ignore “all-on”. There are also a couple bugs with how KPLs turn off scene buttons when pressed that I have to work around with programs. I’d even pay money to buy an Insteon specific flasher and manually flash all my devices by hand. I suspect it’s possible but likely a customer service nightmare.

I saw the email. I take it his concern is folks running "sudo pkg update && sudo pkg upgrade -y". If instead we were told we could run something like "sudo update-polisy" which did all the correct things in the correct order I think everyone would be happy.

@Michel Kohanim can you give us the SSH command that corresponds to clicking the Upgrade Packages button in the console? I've got to imagine it's calling a script in the OS that we could just call directly. It's so much of a better user experience running an upgrade via the console, it allows us too see what's going on, if there are any errors, and when it's completed. The UX experience of clicking a button only for the UI to entirely disappear and then have us sit around next to our devices hoping to hear a series of beeps is not user friendly at all (as noted many have their devices in places that aren't physically accessible or have issues hearing the beeps).

Pretty sure my Insteon lamp dimmers do this too.

I moved over to ISY on Polisy a few months back and it's been great so far. Today I had to replace an Insteon dimmer switch and it didn't go as planned. Added the new switch in the console then did the usual replace in console. I don't recall the exact wording but it said something along the lines of needing to open a new window. I exited the console and restarted it. The new device had taken the old ones place as it was supposed to have, showed proper new ID and such but the new device wasn't responding to any scenes that the old device was in. Tried a restore on the device but still wasn't reacting in scenes. I queried the devices link table and it only had 1 record in it. The ISY table for the device showed the same. Luckily the device was only in a few scenes so I removed it and readded it to each in the console which got everything back to the way it was supposed to be. Has anyone else had success replacing a device in IoP? Is there a step I missed somewhere (I recall the 994 used to reboot on a replace)?

In Cali an “ABC” company like this one stands for “Assignment for the Benefit of Creditors”, fancy name for liquidation company.

In case anyone is interested this is an example of the config I use in HA for one of my fans (with HA talking to my ISY). In this case the real fanlinc is "fan.guest_room_fan" and I'm creating a new virtual fan called "v_guest_room_fan". I also have 4 scenes guest_room_fan_med (and off, high, low) which do what you expect and include the KPL buttons. I have it set so a "on" turns it on at medium: fan: - platform: template fans: v_guest_room_fan: unique_id: v_guest_room_fan_id friendly_name: "Guest Room Fan" value_template: "{{ states('fan.guest_room_fan') }}" percentage_template: "{{ states.fan.guest_room_fan.attributes.percentage | float }}" turn_on: service: switch.turn_on entity_id: switch.guest_room_fan_med turn_off: service: switch.turn_on entity_id: switch.guest_room_fan_off set_percentage: service: switch.turn_on data_template: entity_id: > {% if percentage > 90 %} switch.guest_room_fan_high {% elif percentage > 50 %} switch.guest_room_fan_med {% elif percentage > 10 %} switch.guest_room_fan_low {% else %} switch.guest_room_fan_off {% endif %} speed_count: 3 I do this for every fan in my house, then I expose just the virtual fan to Alexa (via HA instead of ISY). It'd be cool if this sort of thing was built into ISY Portal. It might be possible to do something like this with a Node server as well, but I don't know of any today that'd do it.

What are exposing to Alexa though? Wouldn’t you need to expose all 4 scenes, each as their own device for this to work. I’d think on the Alexa side it’d look like 4 on/off switches.

The problem with this is then you can’t tell Alexa to set the fan to a level or have the right level displayed. You end up with 3-4 different devices as you need one for each scene.

I solved this with Home Assistant and their template feature. I used the template to create a virtual fan for each of my fans. Its status is pulled from the fan linc but each action to set the speed calls one of 4 Insteon scenes which include the KPL buttons. That way I have a single device I can control that sets everything the way I want. I then expose that virtual fan to Alexa.

Not a full fix but you should also be able to change the button mode so in the event you are in the “bad” state (kpl show off but fan is on) you can just hit off again as opposed to having to turn it on and off again.

Concur. The only “light” in your Alexa kitchen group should be the ISY scene for the kitchen. I don’t usually even bother exposing individual devices to Alexa in areas with multiple devices.

Just posted in that linked thread an approach to do room aware commands using NodeRed as an intermediary.

Having failed to get this to work for my fans for years, let alone other device types I ended up using a different solution. Using NodeRed I was able to create room aware commands for everything I wanted to (fans, TVs, blinds). Here is the post that got me going and I posted there with my updated config: https://community.home-assistant.io/t/approaches-to-room-aware-voice-commands-for-alexa-with-node-red/165399

I recall in other threads that there has been mention of keeping the current ISY platform going in parallel for a significant amount of time even after it was running on the new platform. I’d think you’re still going to have to deal with INSTEON silliness for years anyway supporting the old platform and that with a common code base the incremental effort to also support INSTEON on the new would be very low while enabling the sale of many more new units to majority INSTEON existing users. As an owner of both, I for one would love to reduce the number of boxes running

You can use a local Plex Media Server and the Plex Skill to play local music on an echo.

I doubt it will make a difference for this effort, but yes you can control the device directly (assuming it’s the load). It won’t activate the scene so some switches may show the wrong dim value but it will control the load. I do most of mine this way as it gives more direct control of dimming levels. If having the rest of the scene out-of-sync bothers you you can have a program detect the device change and clean up the scene.

I have everything going Alexa -> ISY Portal. I have Alexa Groups created for every room. I have 3 things in each group, the light, the fan, and the Echo for that room. For example: Alexa Group: Kids Room Devices: Kids Echo Kids Light (ISY Portal catagory: Device\Light) Kids Fan (ISY Portal catagory: Device\Fan, so I get high/med/low control) If I'm in that room and say "Alexa, turn on the light" it works. If I say, "Alexa, turn on the fan" I get the "a few things share the name fan" response. If instead I say "Alexa, turn on kids fan" it works as expected. What I'd like to know (and it's hinted by the responses above but not completely clear) is does anyone have it working where you can say "Alexa turn on the fan"? And if so how are you doing it exactly? Do you have every fan in the house just called "fan" and in a room group? If so how to you tell it to turn on a fan that's in another room?