Announcement

Collapse
No announcement yet.

ZEE 1 and ZEE S2 doesn't Shutdown with a Script or Command

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    ZEE 1 and ZEE S2 doesn't Shutdown with a Script or Command

    Hi, I would like to understand why the Shutdown command is not working, neither on ZEE 1, nor in ZEE S2. Using in a Script or executing the Command immediately. Here is the log, indicating that a Shutdown was requested, but nothing happened, neither in the HS Log nor in the ZEE command screen (an HDMI screen connected to my ZEEs).

    Jun-01 12:50:27 PM System Application shutdown request from external interface. Source: Script.NET_01-Jun-2015 12:50:27.31288336_K1.vb
    Jun-01 12:50:21 PM Info Running immediate script: /tmp/K1.vb
    Jun-01 12:50:21 PM Event Running script statement immediately: &hs.Shutdown

    I do need this command working please.

    #2
    I cannot get it to work on the RPi2 running S2 HS3 OS.

    I also tried the external shutdown controller script. Works fine from the buttons on top though.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #3
      So Pete, it seems to be a bug... I will report it to the Help Desk

      Comment


        #4
        Please include me on the bugzilla ticket.

        I have gone to mostly external stuff for my Homeseer 3 Pro box running on Ubuntu 14.04 64 bit as I am also running a lite W2003 VM for my speaker dot exe sapi stuff and embedded Wintel touchscreens and it does work fine except for the audio files stuff.

        I have also see straggler plugins keep running after I shut down Homeseer.

        There is a script in the Homeseer directory which checks the mono stuff while shutting down Homeseer.

        I would run it manually external to Homeseer and tweak it to suit your needs. It is difficult to try to do this within Homeseer which runs in Mono.

        Code:
        #!/bin/bash
        
        # check is a process is running, mono should be the HomeSeer process
        check_process() {
        # echo "$ts:  checking $1"
         [ "$1" = "" ] && return 0
         [ `pgrep -n $1` ] && return 1 || return 0
        }
        
        # wait for the mono process to exit, HomeSeer will then be shut down
        while [ 1 ]; do
         check_process "mono"
        # echo "$?"
         if [ $? == 0 ]; then
          break 
         fi
         sleep 2
        done
        
        # now power off the system
        poweroff
        Last edited by Pete; June 2, 2015, 08:19 AM.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

        Comment

        Working...
        X