Giter Club home page Giter Club logo

homebridge-dummy's Introduction

"Dummy Switches" Plugin

Example config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Switch 1",
          "disableLogging": false
        }   
    ]

With this plugin, you can create any number of fake switches that will do nothing when turned on (and will automatically turn off right afterward, simulating a stateless switch). This can be very useful for advanced automation with HomeKit scenes.

For instance, the Philips Hue app will automatically create HomeKit scenes for you based on Hue Scenes you create. But what if you want to create a scene that contains both Philips Hue actions and other actions (like turning on the coffee maker with a WeMo outlet)? You are forced to either modify the Hue-created scene (which can be a HUGE list of actions if you have lots of lights) or build your own HomeKit lighting scenes.

Instead, you can link scenes using these dummy switches. Let's say you have a Hue Scene called "Rise and Shine" that you want to activate in the morning. And you have also setup the system HomeKit scene "Good Morning" to turn on your coffee maker and disarm your security system. You can add a single dummy switch to your Good Morning scene, then create a Trigger based on the switching-on of the dummy switch that also activates Rise And Shine.

If the disableLogging option is true, state changes (On/Off) will not be logged. The disableLogging option is per switch, so you can choose which ones will get log entries. If not supplied, the default value is false and state changes will be logged.

Stateful Switches

The default behavior of a dummy switch is to turn itself off one second after being turned on. However you may want to create a dummy switch that remains on and must be manually turned off. You can do this by passing an argument in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Switch 1",
          "stateful": true
        }   
    ]

Dimmer Switches

By default, switches are toggle switches (on/off). You can configure your switch to be a dimmer switch, instead, storing a brightness value between 0 and 100. This can be done by passing the 'dimmer' argument in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Switch 1",
          "dimmer": true
        }
    ]

Reverse Switches

You may also want to create a dummy switch that turns itself on one second after being turned off. This can be done by passing the 'reverse' argument in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Switch 1",
          "reverse": true
        }   
    ]

Timed Switches

You may also want to create a timed switch that turns itself off after being on for a given time (for example, five seconds). This can be done by passing the 'time' argument in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Switch 1",
          "time": 5000
        }   
    ]

Resettable Timed Switches

You may also want to create a timed switch that is reset each time it is activated. This way, the original timer is reset instead of creating a new timer. This can be done by passing the 'resettable' argument in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Switch 1",
          "time": 5000,
          "resettable": true
        }   
    ]

Random Timed Switches

You might want to create a switch that given a random time turns itself off. This can be achieved by enabling 'random'. Each time a non-stateful, random timed switch is triggered, the time is set to a random value between 0 and 'time' milliseconds. A random period within one hour is defined as follows in your config.json:

    "accessories": [
        {
          "accessory": "DummySwitch",
          "name": "My Stateful Random Switch 1",
          "time": 3600000,
          "random": true
        }
    ]

homebridge-dummy's People

Contributors

dhayab avatar jaguaza avatar justinmm2 avatar mikehhhhhhh avatar nano9g avatar nfarina avatar rmcob avatar toddgreenfield avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

homebridge-dummy's Issues

Switches "not responding" after reboot until homebridge is manually restarted

Pre Steps

Homebridge installed on Catalina VM following the standard install instructions

Expected Behavior

When machine boots with auto login enabled, Homebridge will automatically start, dummy plug-in will load, and switches will become active in Hone

Current Behavior

Homebridge starts but switches show as “Not Responding” until Homebridge is restarted either through the web gui or with the “sudo hb-service restart” command

Steps to Reproduce (for bugs)

Boot machine
Check accessories in Home app and see “Not Responding”
open terminal and run “sudo hb-service restart”
Check accessories in Home app and see they are working normally

Versions

  • Homebridge: homebridge --version 1.1.0
  • Node: node --version v12.16.2
  • OS: 10.15.5

Configuration

{
"bridge": {
"name": "Homebridge A6FE",
"username": “xx:xx:xx:xx:xx:xx”,
"port": 51764,
"pin": “xxx-xx-xxx"
},
"accessories": [
{
"name": "Bill Occupancy 1",
"stateful": true,
"reverse": false,
"time": 1000,
"accessory": "DummySwitch"
},
{
"name": "Chris Occupancy 1",
"stateful": true,
"reverse": false,
"time": 1000,
"accessory": "DummySwitch"
},
{
"name": "Joint Occupancy 1",
"stateful": true,
"reverse": false,
"time": 1000,
"accessory": "DummySwitch"
},
{
"name": "Laundry Room Kittens",
"stateful": true,
"reverse": false,
"time": 600000,
"accessory": "DummySwitch"
},
{
"name": "Patio Motion Timer",
"stateful": false,
"reverse": false,
"time": 360000,
"accessory": "DummySwitch"
},
{
"name": "Garage Door Open Timer",
"stateful": true,
"reverse": false,
"time": 1000,
"accessory": "DummySwitch"
},
{
"name": "Garage Door Left Open Timer",
"stateful": true,
"reverse": false,
"time": 1000,
"accessory": "DummySwitch"
}
],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
}
]
}

******* com.homebridge.server.plist ******

RunAtLoad KeepAlive Label com.homebridge.server ProgramArguments /usr/local/bin/node /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js run -I -U /Users//.homebridge WorkingDirectory /Users//.homebridge StandardOutPath /Users//.homebridge/homebridge.log StandardErrorPath /Users//.homebridge/homebridge.log UserName EnvironmentVariables PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin HOME /Users/ UIX_STORAGE_PATH /Users//.homebridge

Homebridge Log / Command Output

***** restart machine *******
[6/6/2020, 1:59:58 AM] [HB Supervisor] Homebridge Storage Path: /Users//.homebridge
[6/6/2020, 1:59:58 AM] [HB Supervisor] Homebridge Config Path: /Users//.homebridge/config.json
[6/6/2020, 1:59:58 AM] [HB Supervisor] Logging to /Users//.homebridge/homebridge.log
[6/6/2020, 1:59:58 AM] [HB Supervisor] OS: Darwin 19.5.0 x64
[6/6/2020, 1:59:58 AM] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[6/6/2020, 1:59:58 AM] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[6/6/2020, 1:59:58 AM] [HB Supervisor] Starting Homebridge with extra flags: -I
[6/6/2020, 1:59:58 AM] [HB Supervisor] Started Homebridge v1.1.0 with PID: 259
[6/6/2020, 1:59:58 AM] Loaded config.json with 7 accessories and 1 platforms.
[6/6/2020, 1:59:58 AM] ---
[6/6/2020, 1:59:59 AM] Loaded plugin: [email protected]
[6/6/2020, 1:59:59 AM] Registering platform 'homebridge-config-ui-x.config'
[6/6/2020, 1:59:59 AM] ---
[6/6/2020, 1:59:59 AM] Loaded plugin: [email protected]
[6/6/2020, 1:59:59 AM] Registering accessory 'homebridge-dummy.DummySwitch'
[6/6/2020, 1:59:59 AM] ---
[6/6/2020, 1:59:59 AM] Loading 1 platforms...
[6/6/2020, 1:59:59 AM] [Config] Initializing config platform...
[6/6/2020, 1:59:59 AM] [Config] Running in Service Mode
[6/6/2020, 1:59:59 AM] Loading 7 accessories...
[6/6/2020, 1:59:59 AM] [Bill Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Bill Occupancy 1] Setting switch to true
[6/6/2020, 1:59:59 AM] [Chris Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Chris Occupancy 1] Setting switch to true
[6/6/2020, 1:59:59 AM] [Joint Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Joint Occupancy 1] Setting switch to true
[6/6/2020, 1:59:59 AM] [Laundry Room Kittens] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Laundry Room Kittens] Setting switch to true
[6/6/2020, 1:59:59 AM] [Patio Motion Timer] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Garage Door Open Timer] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Garage Door Open Timer] Setting switch to false
[6/6/2020, 1:59:59 AM] [Garage Door Left Open Timer] Initializing DummySwitch accessory...
[6/6/2020, 1:59:59 AM] [Garage Door Left Open Timer] Setting switch to false
Setup Payload:
X-HM://0024J1OBOH2PA
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ xxx-xx-xxx │     
└────────────┘     

[6/6/2020, 1:59:59 AM] Homebridge is running on port 51764.
[6/6/2020, 1:59:59 AM] [Config] Homebridge Config UI X v4.21.0 is listening on :: port 8581

**** Accessories are not responding so I manually restart ******

[6/6/2020, 2:00:41 AM] [HB Supervisor] Stopping services...
[6/6/2020, 2:00:41 AM] Got SIGTERM, shutting down Homebridge...
[6/6/2020, 2:00:48 AM] [HB Supervisor] Homebridge Storage Path: /Users//.homebridge
[6/6/2020, 2:00:48 AM] [HB Supervisor] Homebridge Config Path: /Users//.homebridge/config.json
[6/6/2020, 2:00:48 AM] [HB Supervisor] Logging to /Users//.homebridge/homebridge.log
[6/6/2020, 2:00:48 AM] [HB Supervisor] OS: Darwin 19.5.0 x64
[6/6/2020, 2:00:48 AM] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[6/6/2020, 2:00:48 AM] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[6/6/2020, 2:00:48 AM] [HB Supervisor] Starting Homebridge with extra flags: -I
[6/6/2020, 2:00:48 AM] [HB Supervisor] Started Homebridge v1.1.0 with PID: 565
[6/6/2020, 2:00:49 AM] Loaded config.json with 7 accessories and 1 platforms.
[6/6/2020, 2:00:49 AM] ---
[6/6/2020, 2:00:49 AM] Loaded plugin: [email protected]
[6/6/2020, 2:00:49 AM] Registering platform 'homebridge-config-ui-x.config'
[6/6/2020, 2:00:49 AM] ---
[6/6/2020, 2:00:49 AM] Loaded plugin: [email protected]
[6/6/2020, 2:00:49 AM] Registering accessory 'homebridge-dummy.DummySwitch'
[6/6/2020, 2:00:49 AM] ---
[6/6/2020, 2:00:49 AM] Loading 1 platforms...
[6/6/2020, 2:00:49 AM] [Config] Initializing config platform...
[6/6/2020, 2:00:49 AM] [Config] Running in Service Mode
[6/6/2020, 2:00:49 AM] Loading 7 accessories...
[6/6/2020, 2:00:49 AM] [Bill Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Bill Occupancy 1] Setting switch to true
[6/6/2020, 2:00:49 AM] [Chris Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Chris Occupancy 1] Setting switch to true
[6/6/2020, 2:00:49 AM] [Joint Occupancy 1] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Joint Occupancy 1] Setting switch to true
[6/6/2020, 2:00:49 AM] [Laundry Room Kittens] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Laundry Room Kittens] Setting switch to true
[6/6/2020, 2:00:49 AM] [Patio Motion Timer] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Garage Door Open Timer] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Garage Door Open Timer] Setting switch to false
[6/6/2020, 2:00:49 AM] [Garage Door Left Open Timer] Initializing DummySwitch accessory...
[6/6/2020, 2:00:49 AM] [Garage Door Left Open Timer] Setting switch to false
Setup Payload:
X-HM://0024J1OBOH2PA
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ xxx-xx-xxx │     
└────────────┘     

[6/6/2020, 2:00:49 AM] Homebridge is running on port 51764.
[6/6/2020, 2:00:49 AM] [Config] Homebridge Config UI X v4.21.0 is listening on :: port 8581
******* Accessories Responding **********

Adding multiple dummy switches

Can I just aff multiple dummy switches by :

"accessories": [
{
"accessory": "DummySwitch",
"name": "My Switch 1"
},
{
"accessory": "DummySwitch",
"name": "My Switch 2"
}
]

or should I do it this way ?

"accessories": [
{
"accessory": "DummySwitch",
"name": "My Switch 1"
"name": "My Switch 2"
}
]

I'm afraid to try either without knowing the confirmed answer, for fear of breaking the entire Homebridge. Used to install a plugin previously using the first script but it broke the whole Homebridge ...

Thank you to anyone that can help .

Repeat Timer

{Edited}
It would be useful to have a switch that goes on & off by itself. I currently have 20 entries in Home to every hour make sure certain devices are off. I sometimes find a device has not gone off; Most important to me is a pump plug.
{
"name": "Backyard Dummy",
"stateful": true,
"repeat_on_off": 20,10, // Stays ON for 20s, OFF for 10s. If either value is 0 then disabled.
"reverse": false,
"time": 0,
"accessory": "DummySwitch"
},
OR
{
"name": "Backyard Dummy",
"stateful": true,
"reverse": false,
"time": 20000,10000, // Stays ON for 20s, OFF for 10s. A missing or 0 second number disables the repeat. Backward compatible.
"accessory": "DummySwitch"
},
OR
{
"name": "Backyard Dummy",
"stateful": true,
"reverse": false,
"time": 20000,
"repeat_after":10000, // Stays ON for 20s, OFF for 10s. A missing attribute or 0 disables the repeat. Backward compatible.

"accessory": "DummySwitch"
},

Maybe add
"repeat_number": 12, // Repeat number of times/number of laps. A missing attribute or 0 lets the repeat on of going indefinitely.

"repeat_end_on": true, // End with the ON state. A missing attribute or FALSE lets the repeat on of going indefinitely.

Example
"time": 20000,
"repeat_after":10000"
"repeat_number": 3
"repeat_end_on": true,
Button press > on off on off on (Ends at ON, three ON states, two OFF states)
"repeat_end_on": false,
Button press > on off on off on off (Ends at OFF, three ON states, three OFF states)

Dummy switch not discovered

I'm a n00b so I apologize if this is too simple of a request. I've created a dummy switch which appears in homekit but doesn't get discovered by Alexa - is there some magic that I'm missing?

Is there a dummy switch with persisted state?

Hi @nfarina,

Are you aware of a similar dummy switch that can persist state? It could be used to predicate triggers. For example, I'd create a dummy switch for "watching tv in living room" and then disable nearby motion sensors if the switch is on.

I'm sure I've said it elsewhere but thank you ever so much for homebridge.

Auto turn off after X seconds

Thanks for this very helpful plugin, I'm already using it for many connected scenes. Now I have a case where I want some kind of delay. How about adding a parameter e.g. seconds to specify the time before the switch turns off again?

Room attribute

Is there a way to add the room attribute?
{
"name": "Living Room Pot Lights",
"room":"Living Room",
"stateful": true,
"reverse": false,
"time": 0,
"accessory": "DummySwitch"
},

[Bug] Stateful Switch Becomes Stateless Until Homebridge Reboot

Hi! I'm running into a pretty frustrating issue with my timer dummy switch.
About every 24 hours or so, it stops behaving as expected. It turns itself on and will not turn off again.
Attached is a video of the bug and a screenshot of my configuration. I've tried all different combinations of config settings to no avail. As far as I can tell, this should be working just fine.

It's also worth noting that for some reason this issue has gotten more prevalent in the past week or so- it used to only be a few times a month and now it occurs daily.

https://user-images.githubusercontent.com/1732093/136672753-6e5305f1-d7b1-4997-b621-2503d1720c93.mov
Screenshot at Oct 09 13-11-49

Dummy contact sensor

It would be great if not only switches but also sensors such as contact sensors were possible.

Power strip characteristic

Would be great to add an ability to display multiple switches as a power strip, because it has way better UI compared to manually grouped switches.

If you group switches, the main tile turns on/off all switches at the same time, otherwise you have to long press on it, then go to accessories submenu and then click the exact switch you want.

In case of power strip, you click on the main tile and it displays round power buttons for individual switches (sockets) right away.

Toggle State of a selected accessory or scene?

I’m not sire if this is something to add to this plugin or to have as a separate plugin. I want to have an automation where if I press a button and the accessory is on, turn its off, if its off, turn it on. But since automations are lacking in that area, I through the that would be a great option for this accessory.

config.json:

"accessories": [
      {
        "accessory": "DummySwitch",
        "name": "My Toggle Switch 1",
        "toggle": true
      }   
  ]

In Homekit allow it to select an accessory(ies)/Scene.

adjustable switch-on delay or timer

Hello, I need a switch-on delay of one minute because I would like to receive a notification when my washing machine is ready, the automation notifies me as soon as the consumption falls below 1 watt, unfortunately our washing machine does this a good 20 times per wash cycle, so I would like to have an adjustable switch-on timer.
Please please
col

After update to 6.0, node red connection to dummy switches has been flakey

Hello, I recently updated to 6.0. I'm on a pi 4b w/8gb running raspbian using an SSD. My dummy switches have always been rock solid. Recently, however, they've been really flakey and node red has been having trouble randomly connecting to some of them. It seems that one or two will randomly just not be available to node red. Maybe I've hit some kind of hard limit on the number of switches? I have a TON, so that might also be it. I just downgraded to 5.0 and we'll need to see what happens, but wanted to flag this and see if you've heard of that.

Dummy Window and Blind

Hello,

thank you for creating this amazing plugin.

I was wondering if it would be possible to expose a virtual switch as a window, as well as exposing one as a blind.
We currently have some motorised windows and blinds automated via some switchbot bots and I am using a virtual switch to trigger the bots and thus having a simplified UI for less tech savvy family members and guests, but some still get confused because it shows as the window being on or off instead of reading open or closed. This would also be a better way of isolating the windows and blinds form the other virtual switches in the status of the Home app.

If you aren‘t interesting in implementing this, maybe someone has come across something similar to what I am describing.

Cheers

Using stateless dummy switch sends 2 commands

I'm using a stateless dummy switch to send a command to my sonos speaker (via Node-Red) to skip to next track. Unfortunately, a stateless dummy switvh appears to send 2 commands (On and then Off), causing the speaker to skip 2 tracks. I'm not sure if this is intentional or not?

Stateless switch turns on by itself

Hi, I have a stateless switch which i use for a very simple automation (so simple that i kinda forgot why i did it).

accessories involved:
Master AC Check -> Stateless switch. Upon turning on, run apple home shortcut to check current state of [Master AC] switch.
If current [Master AC] state is 1 (switch is on), turn [Master AC] off, and light up bulb with red.
If current [Master AC] state is 0 (switch is off), turn [Master AC] on, and light up bulb with green.

Master AC -> Stateful switch. I think I was trying to just mimic the current air conditioner state, and the light is for visual representation outside of the app.

Yeelight Light Bulb -> Colour light bulb, this is compatible with Homekit, not through Homebridge.

So for a while now, my colour light bulb just lights up for no reason, and after checking homebridge logs, it's because the [Master AC Check] switch was triggered. But, I did not trigger it...................... not physically, not via home app, not via homebridge. Is there a way to check why it was triggered? (but i'm guessing this is related to viewing homekit logs itself)

A bit more info bout this [Master AC Check]. I assign to turn this on (through Home app) when I single click and double click on a xiaomi wireless switch which is connected to the Aqara M2 hub. On the Aqara app itself, the single click will trigger the AC remote to turn on/off (via IR blaster), but double click does nothing (in case the [Master AC] status is not in synch with actual AC on/off, I'll just double click to switch the [Master AC] state without actually controlling the AC).

Refer to attached log line 25-27. I'm not sure why homebridge keeps trying to connect the cameras, but I guess i'll post check over there.
log.txt

After Homebridge reboot

Hi.

Great plugin. But one thing.

After Homebridge restart switch turns off and timer is interrupted. I think it should continue after reboot (the switch stay on and the timer continues to count down).

Regards.

Switch not triggering automations

I've had a rather consistent (but not 100%) issue where the stateless dummy switch fails to activate my automations when called via Siri. One of these automations is to lock all my Kevo locks, which are also controlled through Homebridge. So in that case, I can see the switch status being set to "1" then back to "False" without any command (via the automation) reaching the Kevo plugin. I was able to fix this by changing the timout to 5000 (5 seconds). Not sure if this is just some weird issue with my setup or if this is something others are experiencing when using these switches for automations. Might be worthwhile to set this via variable like Stateful and Reverse?

Dummy Dimmer?

I'd like a dummy dimmer switch. (dimming values from 0-100)

Bulb

hi can we make it appear as a light bulb and not as a switch?

Error installing plugin

My Homebridge is running fine. When I try to install this plugin, I get the following errors. Any clues?

npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/minimist-749a5162/example'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/bin'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/examples/counter'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/minimist-749a5162/test'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/examples'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/src'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/test'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/tests'
npm WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/homebridge-dummy-4d4976aa/test/mocks'
Unhandled rejection Error: EISDIR: illegal operation on a directory, open '/Users//.npm/_cacache/index-v5/54/d1'

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! https://npm.community

The switch should reset the internal timer/counter

Hi, the switch should reset the internal timer/counter if the switch is disabled.
e.g. If I set the switch for 1h and turn it on on 1pm the timer runs until 2pm.
But if I disable the switch at 1.30pm and activate it again at 1.45pm the timer should run until 2.45pm but it stops at 2pm (first timer set to end).

Serial number to switches?

It’s possible to add a feature like different (fake) serial numbers to each switch? Cause I’ve here a app which can make backups of Homekit, but complains about the same serial number in all fake switches.

Unable to Install dummy switch

Hi All,

Ive been running into some errors with my install regarding the dummy switches. In the meantime I was able to get homebridge-statefuldummy installed and running but a lot of what i want to do with the dummy switches would be more elegantly accomplished by stateless dummy switches. For reference I'm running homebridge on a mac. Below is what i get when i try and run the install for the plugin:

Last login: Tue Dec 25 19:37:58 on ttys000
"Username removed"sMacBookPro1:~ "Username removed"$ sudo npm install -g --unsafe-perm homebridge-dummy
Password
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/examples/counter'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/src'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/node-persist-6acb9485/tests'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/bin'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/examples'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/mkdirp-d6434059/test'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/minimist-749a5162/example'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/homebridge-dummy-4d4976aa/test/mocks'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/minimist-749a5162/test'
npm ERR! path /usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp/bin/cmd.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp/bin/cmd.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/"Username removed"/.npm/_logs/2018-12-26T02_39_54_605Z-debug.log
"Username removed"sMacBookPro1:~ "Username removed"$

**Edit: I just realized i forgot to put in the complete log for this"

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli '--unsafe-perm',
1 verbose cli 'homebridge-dummy' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session f9b255c5435e32d1
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/homebridge-dummy 277ms (from cache)
8 silly pacote tag manifest for homebridge-dummy@latest fetched in 290ms
9 timing stage:loadCurrentTree Completed in 461ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule [email protected] checking installable status
17 http fetch GET 304 https://registry.npmjs.org/node-persist 63ms (from cache)
18 silly pacote range manifest for node-persist@^2.1.0 fetched in 66ms
19 silly resolveWithNewModule [email protected] checking installable status
20 http fetch GET 304 https://registry.npmjs.org/is-absolute 61ms (from cache)
21 silly pacote range manifest for is-absolute@^0.2.6 fetched in 62ms
22 silly resolveWithNewModule [email protected] checking installable status
23 http fetch GET 304 https://registry.npmjs.org/mkdirp 153ms (from cache)
24 silly pacote range manifest for mkdirp@0.5.1 fetched in 155ms
25 silly resolveWithNewModule [email protected] checking installable status
26 http fetch GET 304 https://registry.npmjs.org/q 165ms (from cache)
27 silly pacote range manifest for q@1.1.1 fetched in 169ms
28 silly resolveWithNewModule [email protected] checking installable status
29 http fetch GET 304 https://registry.npmjs.org/is-relative 54ms (from cache)
30 silly pacote range manifest for is-relative@^0.2.1 fetched in 58ms
31 silly resolveWithNewModule [email protected] checking installable status
32 http fetch GET 304 https://registry.npmjs.org/is-windows 62ms (from cache)
33 silly pacote range manifest for is-windows@^0.2.0 fetched in 65ms
34 silly resolveWithNewModule [email protected] checking installable status
35 http fetch GET 304 https://registry.npmjs.org/is-unc-path 51ms (from cache)
36 silly pacote range manifest for is-unc-path@^0.1.1 fetched in 56ms
37 silly resolveWithNewModule [email protected] checking installable status
38 http fetch GET 304 https://registry.npmjs.org/unc-path-regex 63ms (from cache)
39 silly pacote range manifest for unc-path-regex@^0.1.0 fetched in 64ms
40 silly resolveWithNewModule [email protected] checking installable status
41 http fetch GET 304 https://registry.npmjs.org/minimist 86ms (from cache)
42 silly pacote version manifest for [email protected] fetched in 87ms
43 silly resolveWithNewModule [email protected] checking installable status
44 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 552ms
45 timing stage:loadIdealTree Completed in 559ms
46 silly currentTree lib
47 silly idealTree lib
47 silly idealTree └─┬ [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree ├── [email protected]
47 silly idealTree └── [email protected]
48 silly install generateActionsToTake
49 timing stage:generateActionsToTake Completed in 7ms
50 silly diffTrees action count 10
51 silly diffTrees add [email protected]
52 silly diffTrees add [email protected]
53 silly diffTrees add [email protected]
54 silly diffTrees add [email protected]
55 silly diffTrees add [email protected]
56 silly diffTrees add [email protected]
57 silly diffTrees add [email protected]
58 silly diffTrees add [email protected]
59 silly diffTrees add [email protected]
60 silly diffTrees add [email protected]
61 silly decomposeActions action count 80
62 silly decomposeActions fetch [email protected]
63 silly decomposeActions extract [email protected]
64 silly decomposeActions preinstall [email protected]
65 silly decomposeActions build [email protected]
66 silly decomposeActions install [email protected]
67 silly decomposeActions postinstall [email protected]
68 silly decomposeActions finalize [email protected]
69 silly decomposeActions refresh-package-json [email protected]
70 silly decomposeActions fetch [email protected]
71 silly decomposeActions extract [email protected]
72 silly decomposeActions preinstall [email protected]
73 silly decomposeActions build [email protected]
74 silly decomposeActions install [email protected]
75 silly decomposeActions postinstall [email protected]
76 silly decomposeActions finalize [email protected]
77 silly decomposeActions refresh-package-json [email protected]
78 silly decomposeActions fetch [email protected]
79 silly decomposeActions extract [email protected]
80 silly decomposeActions preinstall [email protected]
81 silly decomposeActions build [email protected]
82 silly decomposeActions install [email protected]
83 silly decomposeActions postinstall [email protected]
84 silly decomposeActions finalize [email protected]
85 silly decomposeActions refresh-package-json [email protected]
86 silly decomposeActions fetch [email protected]
87 silly decomposeActions extract [email protected]
88 silly decomposeActions preinstall [email protected]
89 silly decomposeActions build [email protected]
90 silly decomposeActions install [email protected]
91 silly decomposeActions postinstall [email protected]
92 silly decomposeActions finalize [email protected]
93 silly decomposeActions refresh-package-json [email protected]
94 silly decomposeActions fetch [email protected]
95 silly decomposeActions extract [email protected]
96 silly decomposeActions preinstall [email protected]
97 silly decomposeActions build [email protected]
98 silly decomposeActions install [email protected]
99 silly decomposeActions postinstall [email protected]
100 silly decomposeActions finalize [email protected]
101 silly decomposeActions refresh-package-json [email protected]
102 silly decomposeActions fetch [email protected]
103 silly decomposeActions extract [email protected]
104 silly decomposeActions preinstall [email protected]
105 silly decomposeActions build [email protected]
106 silly decomposeActions install [email protected]
107 silly decomposeActions postinstall [email protected]
108 silly decomposeActions finalize [email protected]
109 silly decomposeActions refresh-package-json [email protected]
110 silly decomposeActions fetch [email protected]
111 silly decomposeActions extract [email protected]
112 silly decomposeActions preinstall [email protected]
113 silly decomposeActions build [email protected]
114 silly decomposeActions install [email protected]
115 silly decomposeActions postinstall [email protected]
116 silly decomposeActions finalize [email protected]
117 silly decomposeActions refresh-package-json [email protected]
118 silly decomposeActions fetch [email protected]
119 silly decomposeActions extract [email protected]
120 silly decomposeActions preinstall [email protected]
121 silly decomposeActions build [email protected]
122 silly decomposeActions install [email protected]
123 silly decomposeActions postinstall [email protected]
124 silly decomposeActions finalize [email protected]
125 silly decomposeActions refresh-package-json [email protected]
126 silly decomposeActions fetch [email protected]
127 silly decomposeActions extract [email protected]
128 silly decomposeActions preinstall [email protected]
129 silly decomposeActions build [email protected]
130 silly decomposeActions install [email protected]
131 silly decomposeActions postinstall [email protected]
132 silly decomposeActions finalize [email protected]
133 silly decomposeActions refresh-package-json [email protected]
134 silly decomposeActions fetch [email protected]
135 silly decomposeActions extract [email protected]
136 silly decomposeActions preinstall [email protected]
137 silly decomposeActions build [email protected]
138 silly decomposeActions install [email protected]
139 silly decomposeActions postinstall [email protected]
140 silly decomposeActions finalize [email protected]
141 silly decomposeActions refresh-package-json [email protected]
142 silly install executeActions
143 silly doSerial global-install 80
144 verbose correctMkdir /Users/Username removed/.npm/_locks correctMkdir not in flight; initializing
145 verbose lock using /Users/Username removed/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
146 silly doParallel extract 10
147 silly extract [email protected]
148 silly extract [email protected]
149 silly extract [email protected]
150 silly extract [email protected]
151 silly extract [email protected]
152 silly extract [email protected]
153 silly extract [email protected]
154 silly extract [email protected]
155 silly extract [email protected]
156 silly extract [email protected]
157 timing action:extract Completed in 789ms
158 silly doReverseSerial unbuild 80
159 silly doSerial remove 80
160 silly doSerial move 80
161 silly doSerial finalize 80
162 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-windows
163 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/minimist
164 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp
165 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/q
166 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/unc-path-regex
167 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-unc-path
168 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-relative
169 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-absolute
170 silly finalize /usr/local/lib/node_modules/homebridge-dummy/node_modules/node-persist
171 silly finalize /usr/local/lib/node_modules/homebridge-dummy
172 timing action:finalize Completed in 37ms
173 silly doParallel refresh-package-json 10
174 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-windows
175 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/minimist
176 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp
177 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/q
178 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/unc-path-regex
179 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-unc-path
180 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-relative
181 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/is-absolute
182 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy/node_modules/node-persist
183 silly refresh-package-json /usr/local/lib/node_modules/homebridge-dummy
184 timing action:refresh-package-json Completed in 62ms
185 silly doParallel preinstall 10
186 silly preinstall [email protected]
187 info lifecycle [email protected]
preinstall: [email protected]
188 silly preinstall [email protected]
189 info lifecycle [email protected]
preinstall: [email protected]
190 silly preinstall [email protected]
191 info lifecycle [email protected]preinstall: [email protected]
192 silly preinstall [email protected]
193 info lifecycle [email protected]
preinstall: [email protected]
194 silly preinstall [email protected]
195 info lifecycle [email protected]preinstall: [email protected]
196 silly preinstall [email protected]
197 info lifecycle [email protected]
preinstall: [email protected]
198 silly preinstall [email protected]
199 info lifecycle [email protected]preinstall: [email protected]
200 silly preinstall [email protected]
201 info lifecycle [email protected]
preinstall: [email protected]
202 silly preinstall [email protected]
203 info lifecycle [email protected]preinstall: [email protected]
204 silly preinstall [email protected]
205 info lifecycle [email protected]
preinstall: [email protected]
206 timing action:preinstall Completed in 6ms
207 silly doSerial build 80
208 silly build [email protected]
209 info linkStuff [email protected]
210 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-dummy/node_modules as its parent node_modules
211 silly linkStuff [email protected] is part of a global install
212 silly linkStuff [email protected] is installed into a global node_modules
213 silly build [email protected]
214 info linkStuff [email protected]
215 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-dummy/node_modules as its parent node_modules
216 silly linkStuff [email protected] is part of a global install
217 silly linkStuff [email protected] is installed into a global node_modules
218 silly build [email protected]
219 info linkStuff [email protected]
220 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-dummy/node_modules as its parent node_modules
221 silly linkStuff [email protected] is part of a global install
222 silly linkStuff [email protected] is installed into a global node_modules
223 verbose linkBins [ { mkdirp: 'bin/cmd.js' },
223 verbose linkBins '/usr/local/lib/node_modules/homebridge-dummy/node_modules/.bin',
223 verbose linkBins false ]
224 timing action:build Completed in 6ms
225 verbose unlock done using /Users/Username removed/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
226 timing stage:rollbackFailedOptional Completed in 30ms
227 timing stage:runTopLevelLifecycles Completed in 1972ms
228 verbose stack Error: ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp/bin/cmd.js'
229 verbose cwd /Users/Username removed
230 verbose Darwin 18.2.0
231 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-dummy"
232 verbose node v8.11.2
233 verbose npm v6.5.0
234 error path /usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp/bin/cmd.js
235 error code ENOENT
236 error errno -2
237 error syscall chmod
238 error enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/homebridge-dummy/node_modules/mkdirp/bin/cmd.js'
239 error enoent This is related to npm not being able to find a file.
240 verbose exit [ -2, true ]

Dead dummy switch remained

I had to tinker with Homebridge and the configuration again. Well, didn't go well.

I had to delete all dummy switches and create them again. But now I have a single, former, non-functional dummy switch displayed. How do I get that deleted.

Delete plugin and install again? Delete a specific temporary directory?

dummy switch for HomeKit alarmsystem

Hello, @nfarina @ALL is it possible for a HomeKit alarm system to develop a dummy switch?

I think that would be great to set up an alarm system in HomeKit with plugs from koogeek or elgato with external sirens and contactsensors.

ad700950-35e7-46f3-a208-770b14145fe9

Maybe someone here who knows this has to make such a plugin or fork and realizes that this switch has tremendous potential.
Thank you.

Set Disable time to Never

Hello, is there a setting I can use if I do not need/want the switch to ever be disabled? I have it set to 604,800,000 milliseconds (one week) but would prefer to just disable it all together.

Dummy stateless switch does not work as trigger for automation

I am trying to use a stateless dummy switch to trigger an automation to open my garage door (so I can bypass the Siri security requirement that my iPhone be unlocked to open the garage door). The dummy switch works fine from Apple's Home app and Siri. "Test Automation" works fine to open the garage door when adding the automation. However, using the switch does not trigger the automation, either through the Home App, Siri or the Homebridge web UI.

Automation using an actual device as the trigger, for example a Wemo Light Switch, works fine to open the garage door. So the issue is definitely with the Homebridge dummy switch.

The hub providing automations is the new Apple HomePod mini running the latest OS, 14.2.

Using dummy switch with motion sensor

I'm using a timed switch with a motion sensor. The expected behaviour is that when the motion sensor detect motion, it turns on the light and the dummy swith. After the set time the dummy switches off, which is automated to turn turns of the light. This works.

The only problem is that the timer doesn't reset once it detected new motion (turning the dummy switch on again while it is on).
So if you stay in the room long enough the light briefly turns off after the timer and immediately turns back on by motion.

Timed reset

Is 9999ms the maximum duration for a resetting switch ? Seems to be so from my testing. Any workaround?

Depreciation Warning

3/23/2022, 12:53:31 PMDummy BridgeERROR(node:31351) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./helpers/" in the "exports" field module resolution of the package at /usr/lib/hoobsd/node_modules/es-abstract/package.json.
3/23/2022, 12:53:31 PMDummy BridgeERRORUpdate this package.json to use a subpath pattern like "./helpers/*".
3/23/2022, 12:53:31 PMDummy BridgeERROR(Use node --trace-deprecation ... to show where the warning was created)

Switch not being triggered when used in automations

I’m a bit lost here so please bear with me. I’m adding a simple stateful switch to hold a Boolean variable for my vacuum cleaner (Cleaned today) which i trigger via an automation: when vacuum is set to “on”, change switch to “on”. But it doesn’t work at all. I tried doing the same with some of my lights and other appliances and they work just fine. Only the switch state remains the same. I’m not sure if that’s a homekit bug and would appreciate any feedback here.

I tried using shortcuts app to create a shortcut, I added another plugin with a stateful switch with no luck at all. I’m also have a similar issue when using another switch that should trigger another switch that comes from broadlink RM plugin. So it seems to me to be related to HomeKit but I’m sure it was working before. Please help!

Error after Update: same UUID

After upgrading the core and the plugin Hoobs will not start with the following message:

[06.08.22, 19:25] Loading 6 accessories...
[06.08.22, 19:25] [Schlafen Dummy] Initializing DummySwitch accessory...
[06.08.22, 19:25] [Schlafen Dummy] Setting switch to true
[06.08.22, 19:25] Error: Cannot add a Characteristic with the same UUID as another Characteristic in this Service: undefined
at Service.addCharacteristic (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/src/lib/Service.ts:344:15)
at /usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/src/lib/AccessoryLoader.ts:128:15
at Array.forEach ()
at parseServiceJSON (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/src/lib/AccessoryLoader.ts:126:19)
at /usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/src/lib/AccessoryLoader.ts:69:21
at Array.forEach ()
at Object.parseAccessoryJSON (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/hap-nodejs/src/lib/AccessoryLoader.ts:68:17)
at Server.createHAPAccessory (/usr/local/lib/node_modules/@hoobs/hoobs/bridge/server.js:406:36)
at /usr/local/lib/node_modules/@hoobs/hoobs/bridge/server.js:314:36
at Array.forEach ()
at Server._loadAccessories (/usr/local/lib/node_modules/@hoobs/hoobs/bridge/server.js:282:33)
at Server.start (/usr/local/lib/node_modules/@hoobs/hoobs/bridge/server.js:152:18)
at /usr/local/lib/node_modules/@hoobs/hoobs/bridge/cli.js:94:16
at processTicksAndRejections (internal/process/task_queues.js:93:5)

iOS Notifications

Within the Home app on iPhone and iPad there is the option to include in Status but not notifications. I have occasions where I would want to activate a dummy switch and have a notification on my, or other, iOS devices. Is this a limitation of switch devices in HomeKit or is this possible?

Display time left

It would be really useful if when used as a timer, that the time remaining is displayed (in minutes and/or seconds) in the home app icon.

Also, the home app icon might show a timer instead of a switch/fan etc.

How to install the plugin

Hi.
I'm new to homebridge.
When I try to install this plugin using "sudo npm install homebridge-dummy" I get this error:
"
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

If I don't install the plugin and add the accessory to config.json when I try to run homebridge it gives me an error too since the dummy accessory wasn't linked to any plugin.

How can I solve this?

Slow state update on iphone app

Hi guys, is it normal to have a 1-2 seconds state refresh delay on iphone app?
Every time I open the Home app all icons shows 'Updating' for 1-2 seconds.

This is my code:
{ "bridge": { "name": "Homebridge", "username": "CC:22:3D:E3:CE:31", "port": 51826, "pin": "031-45-154" }, "platforms": [], "hosts": [ { "address": "192.168.0.4", "mac": "42:f7:c8:17:3f:51", "isRFSupported": false }, { "address": "192.168.0.5", "mac": "42:f7:c8:21:b4:33", "isRFSupported": false }, { "address": "192.168.0.8", "mac": "42:f7:c8:21:b5:43", "isRFSupported": false } ], "accessories": [ { "accessory": "mqttthing", "type": "lightbulb", "name": "Luz Comedor", "url": "mqtt://localhost", "username": "home", "password": "xxxxxxxx", "caption": "", "topics": { "getOn": "stat/ComedorNew/POWER1", "setOn": "cmnd/ComedorNew/POWER1" }, "onValue": "ON", "offValue": "OFF" }, { "accessory": "mqttthing", "type": "lightbulb", "name": "Luz", "url": "mqtt://localhost", "username": "home", "password": "xxxxxx", "caption": "", "topics": { "getOn": "stat/HabPrincipal/POWER1", "setOn": "cmnd/HabPrincipal/POWER1" }, "onValue": "ON", "offValue": "OFF" }, { "accessory": "mqttthing", "type": "lightbulb", "name": "Luz baño", "url": "mqtt://localhost", "username": "home", "password": "xxxxxx", "caption": "", "topics": { "getOn": "stat/Bano/POWER1", "setOn": "cmnd/Bano/POWER1" }, "onValue": "ON", "offValue": "OFF" }, { "accessory": "mqttthing", "type": "lightbulb", "name": "Luz Benja", "url": "mqtt://localhost", "username": "home", "password": "xxxxxx", "caption": "", "topics": { "getOn": "stat/Benja/POWER1", "setOn": "cmnd/Benja/POWER1" }, "onValue": "ON", "offValue": "OFF" }, { "accessory": "mqttthing", "type": "lightbulb", "name": "Reflector", "url": "mqtt://localhost", "username": "home", "password": "xxxxxx", "caption": "", "topics": { "getOn": "stat/Reflector/POWER", "setOn": "cmnd/Reflector/POWER" }, "onValue": "ON", "offValue": "OFF" }, { "accessory": "mqttthing", "type": "lightbulb", "name": "Pasillo", "url": "mqtt://localhost", "username": "home", "password": "xxxxxx", "caption": "", "topics": { "getOn": "stat/Pasillo/POWER", "setOn": "cmnd/Pasillo/POWER" }, "onValue": "ON", "offValue": "OFF" }, { "name": "Automatico Comedor", "stateful": true, "reverse": false, "time": 1000, "accessory": "DummySwitch" }, { "name": "Automatico Pasillo", "stateful": true, "reverse": false, "time": 1000, "accessory": "DummySwitch" }, { "name": "Automatico Reflector", "stateful": true, "reverse": false, "time": 1000, "accessory": "DummySwitch" }, { "name": "Automatico Baño", "stateful": true, "reverse": false, "time": 1000, "accessory": "DummySwitch" } ] }

iOS 16 beta

I have updated to iOS 16 beta. My dummy switch isn’t working now. Not sure if it’s just a beta issue or if they changed something and broke the plug-in?

Interruptor con tiempo definido

Buenas tardes.

Su dummy se desconecta de forma automática en 1 segundo. Hay forma de poder añadir mas segundos ese tiempo.

Gracias por tu trabajo, pero es que necesito que se mantenga encendido 4 segundos y otro 2 segundos.

Dummy Garage Door

Hi there, great job with the dummy switches plugin. It's so useful! I have to ask you something more: a gate / garage door dummy opener. It should act exactly as a timered dummy switch but with the HomeKit icon/animation of garage door....just to say to SIRI "open the gate" instead of "activate the gate" since I'm using a 1ch shelly switch.

Thanks and have a great day!
L

th

One accessory

Hi, is it possible to make few dummy switches in one grouped accessory. I mean ios13 like grouping. Maybe in the future?
Thanks

Dummy switch turns off when room should be

I’ve got a strange issue. When I command Siri to turn off the bedroom, the TV OFF dummy switch in HomeBridge is activated for some reason. This only happens using my 2 HomePod mini’s. If I use my iPhone/iPad, Siri executes the command successfully. If I delete the dummy switch, the command executes successfully via the HomePods.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.