Jump to content

pablohoney

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pablohoney's Achievements

New

New (2/6)

1

Reputation

  1. Thanks for the insight on the image used in the script. I've done 3-4 updates and the error just now displayed.
  2. I'm running 2024.4.2 and have the error. Did a restart of HA and error remains.
  3. Setup Home assistant VM a few weeks ago following these instructions: https://developer.isy.io/blog/Home Assistant Did updates yesterday to Home Assistant and am now getting an "Unsupported system - virtualization_image" error. Screen capture below and HA information on this error here: https://www.home-assistant.io/more-info/unsupported/virtualization_image HA state solution is to reinstall Home Assistant OS using an image which supports being run on a virtualized system. Will this be supported on the eisy?
  4. I'm in Ohio. If shipping is an option, I'm interested.
  5. Perfect, rebooting the ISY resolved it. Thanks for the quick reply!
  6. Migrating from the ELK module to PG3 ELK NS with the Notification NS. Can the Zone Logical Status be mapped for Notifications with the ELK NS? Previously with the ELK module using ${elk.zone.3.status} provided Logical Status (Normal and Violated) in the notification. With the ELK NS using ${sys.node.n013_zone_3.status} as shown in the READE.md it only returns a value of "status" for the value in the notification. Changing to ${sys.node.n013_zone_3.ST} returns the raw value of 0 for Normal and 2 for Violated in the notification. For outputs using ${sys.node.n013_output_8.ST} returns the status with a value of Off or On in the notification.
  7. I'm experiencing the same issue with release 3.3.4 and a 2486D v.41. Any updates on this?
×
×
  • Create New...