InvisOutlet

Will do.

Again, love the communiation and the pace, uf you added an update changelog somewhere, I am sure all would be appreciative as well.

thanks

1 Like

Thank you! Is there a Github page or somewhere we can log bugs? I just noticed these too.

I have been testing this for a couple of days and this morning I deleted the matter instance and switched to MQTT, I like the data that it exposed to HA through MQTT and so far it’s been stable, I did experience the bug on the status being wrong and am glad it will be fixed, The one thing I have noticed is missing from MQTT is the ability to change the default state of the outlets and light, the unit I am testing shipped with the outlets off by default, which I don’t think should be the default I want my smart home things to act like the things they are replacing with extra features in this case I expect the outlet to supply power when power is on, not stop working after a power outage. That being said I understand the desire to have the outlet not automatically turn on after power is restored so that you can automate “dumb” things like fans, lights, space heaters etc and not have them suddenly turn on after a power outage. In matter I could change this behavior now that I switched to MQTT I can’t see anyway to do it the webpage on the device and the Invishome app do not seem to have these settings unless I am missing a menu somerwhere.

I tried deleting matter (from home assistant), and then reste outlet, and I in order to connect, I can only re-connect to HA. So, I am connected again, but MQTT is not working.

Can someone please idiot check my setup?

don’t know but I will say setting the mqqt settings failed for me I had to hit back and then apply settings

but I was using the web interface

I seemed to have better luck with web interface, thanks!

Now, I am still always detecting motion/occupancy, but definitely getting better!

Tried updating my two outlets to .71. One of the went through, the other one is stuck and WILL NOT update. Tried resetting it multiple times, but nothing works.
After resetting it, I cannot do ANY customization without updating the firmware. So I am stuck using it with Matter, which doesn’t work, essentially bricking the device…

I understand this was early access, and I can life with some bugs, but this experience has been very frustrating.

@DAE51D Neat find on the web interface! @lawrence-intecular Glad to see you in this thread post email.

I’m late to the party (Darn lack of email notifications), though this is less HA and overall product feedback. I was so excited for the motion of MMWave sensors. They’re useless to me and they’re nearly consistently on in my living room with no one in there and my cats upstairs sleeping with me. In my environment, this outlet is right next to an air vent in the floor though traditionally mmwave should be affected by moving air like this and it’s still triggering when the HVAC is off.

@wesleykirkland and @lawrence-intecular I also notice the distance is sooo not accurate and slow to update. I tried to make an automation that triggers if 5’ or less and it doesn’t work because by the time someone comes in the hall they’re at like 15’ or 10’ by the time the outlet updates and then they’re gone down the stairs, so the 5’ thresh never gets hit.

Feature request, can you add “inches” to here since that is what HA shows and automatons expect to use.


Also, as you’re experiencing, I have one in my Airbnb I thought would be good for security but the thing ALWAYS thinks someone is in there!! The ONLY thing in that plug is an extension chord.



note the times taken. NOBODY is down there I assure you.



View from the camera angle


Hi @wesleykirkland @DAE51D ,

Thank’s for the detailed feedback. The distance report to HA or to our app isn’t something we designed originally, but more like a feature request from the community which we enabled it. Therefore, we cannot guarantee if it is always accurate or not.

However, I do see a plug that is plugged into your top receptacle, which we don’t recommend doing it as it may interfere the radar to detect the occupancy, and may be the reason why your distance isn’t accurate… You may try to play with it and see if that is the reason or not. We also recommend you to utilize our app to lock the receptacle’s power instead of a power block, since the outlet is already smart :wink:

If your occupancy detection isn’t accurate, we implemented occupancy sensor calibration in the latest firmware (InvisOutlet 0.6.72 and InvisDeco 0.9.7), please try to calibrate when no one or pet is in the area and see if that helps to make the sensor accurate. Note: We only recommend doing the calibration if you think it is not accurate, as this will overwrite the original settings and cannot be reversed.

Side note: MQTT bugs should all be fixed by now!

Sincerely,
Lawrence from Intecular

1 Like

Hi @boneless ,

Can you try to restart your device either via the app or double click the middle button of the InvisOutlet and try to perform software update again?

Thank you.

Sincerely,
Lawrence from Intecular

I have 4 outlets; on 3 of them occupancy seems to be working correctly. The 4th has similar behavior to what @beaulebens reported above – ie occupancy sensor looks broken and was constantly triggering on and off.

I tried the calibration, but it didn’t work for me: At about 8s remaining I see “Calibration successful” but just before the timer elapses the message changes to “Occupancy Detected”, and outlet now seems to (permanently?) report occupancy “Triggered - E100”. This happens for all calibration times I tried (10s up to 80s).

Firmware versions: 0.6.72/0.9.8

Hi @ardrahan ,

Can you leave the area and make sure no moving objects in the zone before you begin calibration?

We recommend 60 seconds to perform the calibration.

Also, can you kindly check if it is facing blinds or curtains or any glass or metal objects that may cause reflection?

Sincerely,
Lawrence from Intecular

Hi @lawrence-intecular thanks for the quick reply. Room was empty and door was closed during calibration. My first calibration attempt was 60s but this didn’t work (it said it was successful but then occupancy was detected even though room was empty). After that I tried different calibration times, but still didn’t work.

Outlet is not facing blinds or glass – I’ll send you a picture.

1 Like

@lawrence-intecular removing the plastic plug does seem to make a difference (I also did re-calibrate again since I had tried that the other day so I already screwed myself from defaults. And I did a reboot of the deco.) So far the motion/occupancy bubbles are clear as expected.

I have to say that seems a very strange solution as wouldn’t anything plugged into the receptacle cause the same problem or more being actual metal and solid vs some thin plastic cap?

Soooooo now that things are stabilizing for the most part, the whole reason I bought these were for the in-wall motion detection in the first place :slight_smile: Especially in my Airbnb where cameras and other devices are forbidden (with guests). And for my security since it’s 3 floors below.

I took a stab at making a Home Assistant automation that simply notified me of motion, but it’s not as simple as one would think. You have to have delays or something otherwise I was getting like 3-5 rapid notifications within a short period b/c the person is walking by. Also, I only want them at night when we’ve gone to bed (in my main hallway, not all day). Ideally I only want them if the movement is within 5’ because otherwise it’s someone walking by their bedroom door 15’ away and not actually IN the hallway… Things like this are beyond my newb HA skills at the moment to write from scratch. I think it would be incredibly helpful if you guys could create some template examples (or blueprints) of how to leverage some of the sensors/features of your outlet… Then we can tweek and hobble the rest together…

So with the help of Claude, I was able to hobble together a notification that doesn’t bombard me (only re-triggers after 120s) and only triggers during certain hours (7:30p-5:00a)…

Create a “helper” and name it Last Hallway Motion Notification


Then create your automation…and use a blank one (top option) and replace the YAML with this. Adjust as needed obvi…

alias: Hallway Motion InvisOutlet
description: Motion detection with cooldown period for notifications
triggers:
  - entity_id:
      - binary_sensor.invisoutlet_hallway_motion
    from: "off"
    to: "on"
    trigger: state
conditions: []
actions:
  - if:
      - condition: time
        after: "19:30:00"
        before: "05:00:00"
        weekday:
          - sun
          - sat
          - fri
          - thu
          - wed
          - tue
          - mon
      - condition: template
        value_template: >
          {% set last =
          states('input_datetime.last_hallway_motion_notification') %} {% if
          last != 'unavailable' and last != 'unknown' %}
            {% set last_dt = strptime(last, '%Y-%m-%d %H:%M:%S') %}
            {% set now = now() %}
            {% set diff = (now.timestamp() - last_dt.timestamp()) %}
            {{ diff > 120 }}
          {% else %}
            {{ true }}
          {% endif %}
    then:
      - target:
          entity_id: input_datetime.last_hallway_motion_notification
        data:
          datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
        action: input_datetime.set_datetime
      - continue_on_error: true
        data:
          title: Motion
          message: Hallway Upstairs detected motion on InvisOutlet
        action: notify.notify
  - wait_for_trigger:
      entity_id: binary_sensor.invisoutlet_hallway_motion
      from: "on"
      to: "off"
      trigger: state
variables:
  last_notification: "{{ states('input_datetime.last_hallway_motion_notification') }}"
mode: restart
max_exceeded: silent

please to enjoy… :slight_smile:

The trigger is really fast which I appreciate. I can’t get a distance to be reliable unfortunately as per my earlier posts :frowning:

@lawrence-intecular feel free to post on your website or whatever as maybe the start of some useful automations/blueprints you guys might start a library for people to contribute… :crossed_fingers:

Hello,

I got my invisoutlet installed and hooked up to HA through MQTT and all sensors are showing. Only issue I am having is the motion and occupancy are randomly triggering in a closed room. I have the outlet installed in a walk in closet and used the motion to trigger light automations, but it is currently turning them on at random. Is there anything I can try to resolve this? Occupancy calibration did not help. Thanks.

Edit to add that I have tried both of the InvisDeco that I received and both have the same false motion triggers in this room. Using a Hue motion sensor in the same room I do not get any false triggers. Will there be any update to be able to control the sensitivity of the InvisDeco motion sensor @lawrence-intecular ?