alexryd / homebridge-shelly-ng Goto Github PK

Hello,

with 1.3.0 i am getting this:

TypeError: Cannot read properties of undefined (reading 'reconnectInterval') at new PlatformOptions (/volume1/@appdata/homebridge/lib/node_modules/homebridge-shelly-ng/src/config.ts:107:33) at new ShellyPlatform (/volume1/@appdata/homebridge/lib/node_modules/homebridge-shelly-ng/src/platform.ts:154:20) at /volume1/@appdata/homebridge/lib/node_modules/homebridge/src/server.ts:440:40 at Array.forEach (<anonymous>) at Server.loadPlatforms (/volume1/@appdata/homebridge/lib/node_modules/homebridge/src/server.ts:372:27) at Server.start (/volume1/@appdata/homebridge/lib/node_modules/homebridge/src/server.ts:159:29)

Homebridge 1.4.0.
1.3.0_beta is fine. Do i need to clear cache or something? :)

Btw: Happy Easter!

Have Shelly Pro 2 (SPSW-202XE16EU)
Homebridge write in console

[shellypro2-30c6f78aa540] Unknown device of model "SPSW-202XE16EU" discovered.

How fixit?

Hello ,

Is it possible to include "fakegato" in shelly plugin to allow power consumption to be send and store in homekit for EveApp

https://github.com/simont77/fakegato-history

Dear @alexryd,

If you ever consider developing support for authentication on the PRO Series, this bit of code might help. It comes from Shelly's own technical team, so it should work fine.

const http = require("http");
const crypto = require("crypto");

const username = "admin"; // always
const password = "secretpassword";

const postData = {
  id: 1,
  method: "Shelly.GetStatus",
};

const options = {
  hostname: "192.168.2.16",
  port: 80,
  path: "/rpc",
  method: "POST",
  headers: {
    "Content-Type": "application/json",
  },
};

const __sha256ToHex = async (str) => {
  return crypto.createHash("sha256").update(str).digest("hex");
};

const _getAuthResponse = async (authParams, pass = null) => {
  let _respAuthParams = { ...authParams };
  let _shaUserToken = "";
  if (pass !== null) {
    let _userTokenStr = username + ":" + _respAuthParams.realm + ":" + pass;
    _shaUserToken = await __sha256ToHex(_userTokenStr);
  }
  let _shaMethod = await __sha256ToHex("dummy_method:dummy_uri");

  _respAuthParams.username = username;
  _respAuthParams.nonce = parseInt(_respAuthParams.nonce, 16);
  _respAuthParams.cnonce = Math.floor(Math.random() * Math.pow(10, 8));

  let _respArray = [];
  _respArray.push(_shaUserToken);
  _respArray.push(_respAuthParams.nonce.toString());
  _respArray.push("1");
  _respArray.push(_respAuthParams.cnonce.toString());
  _respArray.push("auth");
  _respArray.push(_shaMethod);
  _respAuthParams.response = await __sha256ToHex(_respArray.join(":"));
  return _respAuthParams;
};

const shellyHttpCall = async (options, postdata) => {
  return new Promise((resolve, reject) => {
    options.headers["Content-Length"] = Buffer.byteLength(
      JSON.stringify(postdata)
    );
    const req = http.request(options, async (res) => {
      let buffer = new Buffer.alloc(0);
      if (res.statusCode == 401) {
        let _challengeAuthParams = {};
        let _auth_header_params = res.headers["www-authenticate"]
          .replace(/\"/g, "")
          .split(", ");
        for (_param of _auth_header_params) {
          let [_key, _value] = _param.split("=");
          _challengeAuthParams[_key] = _value;
        }
        let _authParams = await _getAuthResponse(
          _challengeAuthParams,
          password
        );
        return resolve(
          shellyHttpCall(options, { ...postdata, auth: _authParams })
        );
      }
      res.on("data", (chunk) => {
        buffer = Buffer.concat([buffer, chunk]);
      });
      res.on("end", () => {
        return resolve(buffer.toString("utf8"));
      });
    });
    req.write(JSON.stringify(postdata));
    req.end();
  });
};

shellyHttpCall(options, postData)
  .then((data) => {
    console.log("Device response: ", data);
  })
  .catch((err) => {
    console.log("Request failed");
  });

I unplugged the device (Shelly Plus 1PM) and replaced it with another one (Shelly Plus 1).
The new device was successfully found.

[Shelly NG] Failed to add discovered device (id: shellyplus1pm-441793a4d6a0): Error connecting to device (code: 1006)
[Shelly NG] Error: Error connecting to device (code: 1006)
at JSONRPCClientWithAuthentication.requestWithAuthentication (/homebridge/node_modules/homebridge-shelly-ng/node_modules/shellies-ng/src/rpc/auth.ts:114:29)
at processTicksAndRejections (node:internal/process/task_queues:96:5)

Hi,

three days ago I installed homebridge-shelly-ng at homebridge running on a QNAP NAS. Everything is working fine direct after restarting homebridge. But after a few hours shelly disconnects without any reason. A restart solves the problem and the device is working again.

Any idea how to find the reason?

[3/29/2022, 11:24:44 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /homebridge/node_modules
[3/29/2022, 11:24:45 PM] [HB Supervisor] Started Homebridge v1.4.0 with PID: 911
[3/29/2022, 11:24:47 PM] Loaded config.json with 0 accessories and 3 platforms.
[3/29/2022, 11:24:47 PM] Loaded 1 cached accessories from cachedAccessories.
[3/29/2022, 11:24:47 PM] ---
[3/29/2022, 11:24:48 PM] Loaded plugin: [email protected]
[3/29/2022, 11:24:48 PM] Registering platform 'homebridge-neato.NeatoVacuumRobot'
[3/29/2022, 11:24:48 PM] ---
[3/29/2022, 11:24:49 PM] Loaded plugin: [email protected]
[3/29/2022, 11:24:49 PM] Registering platform 'homebridge-shelly-ng.ShellyNG'
[3/29/2022, 11:24:49 PM] ---
[3/29/2022, 11:24:49 PM] Loaded plugin: [email protected]
[3/29/2022, 11:24:49 PM] Registering platform 'homebridge-config-ui-x.config'
[3/29/2022, 11:24:49 PM] ---
[3/29/2022, 11:24:49 PM] Loading 3 platforms...
[3/29/2022, 11:24:49 PM] [Config] Initializing config platform...
[3/29/2022, 11:24:49 PM] [Config] Running in Service Mode
[3/29/2022, 11:24:49 PM] [NeatoVacuumRobot] Initializing NeatoVacuumRobot platform...
[3/29/2022, 11:24:49 PM] [NeatoVacuumRobot] Refresh is set to: auto
[3/29/2022, 11:24:49 PM] [Shelly NG] Initializing ShellyNG platform...
[3/29/2022, 11:24:49 PM] [Shelly NG] mDNS device discovery started
[3/29/2022, 11:24:49 PM] [Shelly NG] [Steckdose Esszimmer] Device added
...
[3/30/2022, 7:41:49 PM] [Shelly NG] [Steckdose Esszimmer] Device disconnected (reason: )
[3/30/2022, 7:41:59 PM] [Shelly NG] [Steckdose Esszimmer] Failed to set switch: Request timeout

Hi,
seems like my Shelly 1 Plus is reconnecting quite often (several times per hour) to the homebridge shelly ng plugin. Its wifi connection (rrsi: -75) is poor but stable, cause it seems reachable during all homebridge reconnection attempts.

[03/05/2022, 22:17:15] [Shelly NG] [shellyplus1-44179394536c] Device disconnected (code: 1006)
[03/05/2022, 22:17:15] [Shelly NG] [shellyplus1-44179394536c] Reconnecting in 5 second(s)
[03/05/2022, 22:17:21] [Shelly NG] [shellyplus1-44179394536c] Device connected

The log shows "code 1006" - anybody knows what that means?
For any other ideas, thanks in advance.

Best regards!

Hey guys,

I using my shelly 1 plus for our new door to unlock. Is it possible to say in the plugin that it is not a switch but rather a lock like here?

Thanks

Hi,

I just configured Shelly Pro 4PM and it works. However I get a lot of errors with mDNS discovery:

[29/03/2022, 16:15:19] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge xxxx) is running on port 51940.
[29/03/2022, 16:15:19] [Shelly NG] mDNS device discovery started
[29/03/2022, 16:15:19] [Shelly NG] [Shelly1] Device added
[29/03/2022, 16:15:22] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[29/03/2022, 16:15:22] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label)
[29/03/2022, 16:15:30] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)

I have no other Shelly devices. I connected it to my IoT vlan and tried to put different mdns interfaces but none of them works.

Could you please help how to debug it?

I have two Shelly NG devices (Shelly Plus 1, Shelly Plus 2PM) on the network, and one of them is not showing up in the NG plugin.
I can see in the homebridge log that both devices are discovered using mDNS, but only one of them is correctly identified:
[25/07/2022, 18:27:37] [Shelly NG] [Gäste] Device added
[25/07/2022, 18:27:37] [Shelly NG] [shellyplus2pm-441793a7abc0] Unknown device of model "SNSW-102P16EU" discovered.

Seems the Shelly Plus 2PM is not known to the plugin yet?

Thanks
Jonathan

Hi @alexryd ,

do you see the chance to include the Shelly Plus i4?
I will install 2 the next days, so if you need some feedback or testing, I could help if possible!

Thanks for working in the NG devices!

Hi Alex,

today I just installed a Shelly PRO 1, can you let me know if this device is already supported?

I now got below message in Homebridge:

[02/02/2022, 20:22:22] [Shelly NG] [shellypro1-deviceID] Unknown device of model "SPSW-001XE16EU" discovered.

I tried to add it manually but this doesn't work. Looking at the supported devices I think this one is not (yet) supported?

If I need to test or gather info please let me know

Many thanks!

Hello, is it possible to add support for the Shelly Plug Plus?

Thanks!

Hi, I have a problem with automation. I have photo sensor running during night but in the morning Shelly 1PM+ is not reachable in Homekit. In the photo you see after the homekit aumatically turned it off.

Please add the possibility to set a Password for the mDNS auto configuration.

Is it somehow possible to represent the input state of a detached switch from a shelly pro 4pm in homekit/homebridge?

Update!
I can see the readings in Eve, however there is an issue with total consumption - it come from Shelly in Wh not in KWH , however you send it as kWh and it shows I have 5000kwh consumption.
you should divide by 1000 before send it to HomeKit.
thank you so much for this amazing update !

Hi !

May be a new type 'light' for devices. switch:0-3.type can be introduced in order do not to have to reconfigure the accessories again in HomeKit from Switch -> Light - in case the switch is only handling lights ... :)

thx alex

Hello there,

When I set it from the shelly ios application, it detects the cover position correctly, when I set it from the ios home application, I get the error in the title.

Thank you so much for your great work developing this plugin!

It works like a charm with my Shelly 1 Plus.

However, I'm getting the following error about once or twice a minute on the homebridge log:
An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)

I have my Shellys on a different VLAN. Could you specify what this error means exactly? I'm guessing I have to update my firewall setting to make it disappear. I'm a bit confused why it has no problem discovering my devices, though.

Here is a longer excerpt from the homebridge log:

[2/7/2022, 2:27:52 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge xxxx) is running on port 51504.
[2/7/2022, 2:27:52 PM] [Shelly] Admin server is running on port 8181
[2/7/2022, 2:27:52 PM] [Shelly NG] mDNS device discovery started
[2/7/2022, 2:27:53 PM] [Shelly NG] [WoZi Tisch] Device added
[2/7/2022, 2:28:09 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:28:09 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:28:27 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:28:49 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:28:49 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:29:57 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:29:57 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:31:10 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:31:10 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:32:14 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:32:47 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:32:47 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:34:18 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:34:18 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:34:52 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:35:00 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[2/7/2022, 2:35:00 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)

[this goes on and on]

Thanks for the PlugIn. But unfortunately I get for a Shell Plus 2 PM only the message
[Shelly NG] [shellyplus2pm-a8032ab727c4] Unknown device of model "SNSW-002P16EU" discovered.

Actually, a shutter should be operable via Homebridge here. But this shelly does not appear at all.

What is interesting is that a Shelly Plus 1 appears that I do not have.

[Shelly NG] [shellyplusi4-083af20109d8] Unknown device of model "SNSN-0024X" discovered.

{"name":null, "id":"shellyplusi4-083af20109d8", "mac":"083AF20109D8", "model":"SNSN-0024X", "gen":2, "fw_id":"20211101-134319/i4prod0-g2345cff-279-i4-production-bundles-2143-dirty", "ver":"i4prod0", "app":"PlusI4", "auth_en":false,"auth_domain":null}

Failed to add discovered device (id: shellyplus1pm-441793ceexxx): Cannot read property 'toUpperCase' of undefined

hello,

a have a lot of Shelly Plus 2 PM in cover mode, all detected automatically via mDNS.
How can I change the type from "window" to "windowCovering"?

This is a feature request to assign more accessory types aka Shelly-Switch-Configurations. For example motionSensor was available in alexryd/homebridge-shelly. It looks as though type-switch is the only HomeKit type available.

Thank you alexryd once again for the great work !

Just installed it. I have a Shelly plus1PM in the network but the accessory did not appear after the HB restart.

Even though the plugin is loaded as seen below:

[1/20/2022, 9:44:58 PM] Loaded plugin: [email protected]
[1/20/2022, 9:44:58 PM] Registering platform 'homebridge-shelly-ng.shelly-ng'

the HB log does NOT report the normal platform initialization but a red error message:

[1/20/2022, 9:45:01 PM] No plugin was found for the platform "Shelly NG" in your config.json. Please make sure the corresponding plugin is installed correctly.

Running on docker, latest HB version 1.3.9
Node.js v16.13.1
Npm v8.1.2
Homebridge Network settings, mDNS advertiser is set to Ciao.
Plugin config:
{
"name": "Shelly NG",
"platform": "Shelly NG"
}

I installed a new ShellyPlus 2PM for my Window Covering. I replaced an old Shelly 2.5. The Shelly 2.5 was displayed
in homekit as "Window Covering" while the ShellyPlus2PM is shown as "Window". Is it possible to configure the ShellyPkus2PM as "Window Covering" as well?

Hello,
I've added a Shelly Plus 1 PM to my Homebridge and after it didn't respond (even not with the physical switch), I've changed it to another Shelly Plus 1 PM. After the initial configuration of the new one I removed with the "x" symbol the old one from the device list on Homebridge UI. Now every time I restart my Homebridge it gives me the error code 1006 "it couldn't find the device". Of course it can't be found as it isn't there :) How can I fix the problem? Does anyone know?
PS: The Shelly also appears in my HomeApp on my Apple Device and I can't remove it from there easily.
Best regards!

Log file gives the following error.

[homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 257.8 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.

As title: is it possible that with new ios16 there’s some bug about Shelly?
I’ve also Shelly 1 plus and Shelly 2pm installare successfully and all of them I can see in homekit through shelly next gn plug-in.
Could you help me please!
because the shelly i4 I’m using to see state of my alarm!

thanks a lot!

Having 2 Shelly 1PM.
Configured with different names in config.
Both discovered and naming works fine in HomeKit.

But under accessories in Homebridge i get 2 switches with the same name : Switch 1

Also in node-red i get 2 devices "Switch 1 - Switch" - so i can only control one of them.

temp fix: set on type to 'switch', the other to 'outlet'

is it possible to get the device name instead as with homebridge-shelly, e.g. 'Shelly Plug S C3F17D' or the id e.g. 'shellyplus1pm-4719da1774bd' maybe as prefix ?

Hi,

I'm getting these very frequently in logs:
[30/05/2022, 17:08:07] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[30/05/2022, 17:08:07] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label)
[30/05/2022, 17:08:16] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)
[30/05/2022, 17:08:16] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label)
[30/05/2022, 17:08:43] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label)

I've disabled mDNS, since I add my devices manually, but the errors still come.
{
"name": "Shelly NG",
"mdns": {
"enable": false
},
"devices": [
{
"id": "shellypro1-30c6f7847ed0",
"name": "Shelly Pro 1",
"exclude": false,
"hostname": "172.21.1.92"
}
],
"platform": "ShellyNG"
}

I have only the one device right now, testing on the bench, but things seem to work. There are just a lot of log entries.

Hi,
I got a Raspberry running Homebridge image (updated to latest stable version for Homebridga and Raspi OS) :

• plugin for Shelly working fine in HomeKit (with latest stable firmware)
• plugin for Shelly Plus with 2x 1Pm and 1x 2PM (with latest stable firmware), not working into HomeKit (not visible !)

Homebridge Logs :
[17/09/2022, 18:49:45] [Shelly NG] Loaded homebridge-shelly-ng v1.6.0 child bridge successfully
[17/09/2022, 18:49:45] Homebridge v1.5.0 (HAP v0.10.2) (Shelly NG) is running on port 37751.
[17/09/2022, 18:49:45] [Shelly NG] mDNS device discovery started
[17/09/2022, 18:49:45] [Shelly NG] [shellyplus1pm-44179395067c] Device added
[17/09/2022, 18:49:45] [Shelly NG] [shellyplus2pm-485519a19260] Device added
[17/09/2022, 18:49:46] [Shelly NG] [shellyplus1pm-441793a4d6b0] Device added

On the Homebridge UI and from the Accessories Menu I got the Shelly Plus device and I can control them but I don't have anything into HomeKit using the Home app, why ?

I try to switch from Avahi to Ciao with the same result.

I don't know how to investigate...

Thanks in advance.
Nicolas

Hello, can you please add these two shelly for support :)

Shelly Plus 2PM
{"name":null,"id":"shellyplus2pm-a8032ab7260c","mac":"A8032AB7260C","model":"SNSW-002P16EU","gen":2,"fw_id":"20220214-154302/0.10.0-beta3-gd36941f","ver":"0.10.0-beta3","app":"Plus2PM","auth_en":false,"auth_domain":null,"profile":"switch"}

Shelly Plus I4
{"name":null, "id":"shellyplusi4-083af20140a4", "mac":"083AF20140A4", "model":"SNSN-0024X", "gen":2, "fw_id":"20220120-094630/i4prod1-g480b553", "ver":"i4prod1", "app":"PlusI4", "auth_en":false,"auth_domain":null}

Plugin 1.0.1 crashes Homebridge on startup, if Device (shelly Plus 1) is unreachable.

Jan 21 16:40:04 HomeServer homebridge[1301]: [21.1.2022, 16:40:04] [Shelly NG] mDNS device discovery started
Jan 21 16:40:07 HomeServer homebridge[1301]: [21.1.2022, 16:40:07] [Homebridge UI] Homebridge Config UI X v4.42.0 is listening on :: port 8080
Jan 21 16:40:07 HomeServer homebridge[1301]: [21.1.2022, 16:40:07] Error: connect EHOSTUNREACH 192.168.178.40:80
Jan 21 16:40:07 HomeServer homebridge[1301]: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Jan 21 16:40:08 HomeServer systemd[1]: homebridge.service: Main process exited, code=exited, status=143/n/a
Jan 21 16:40:08 HomeServer systemd[1]: homebridge.service: Failed with result 'exit-code'.

As PM Shellie's offer power measurement it would be nice to expose it to HomeKit as well.

We have this issue in cover mode when the cover is moved with the buttons connected on the Shelly. It seem that homekit is not updated with the current position

Is it possible to exlude only one chanel from a Shelly Pro 4 PM? Inside the Shelley App, the Chanels have a"_1" or _2" at the end of the ID like "shellypro4pm-abcdefg12345_2".

However, when I enter that ID shellypro4pm-abcdefg12345_2, nothing happens. Without the "_2" suffix, the entire Shelly is excluded.

THX

Hello @alexryd !
How to add manually a Shelly 1 plus ?
My devices are on a separate network and the automatic discovery doesn't work... So I want to add all manually.

Thanks for your answer :)

I have change de Device name in the Shelly Device/app
The name are showing in Logfile but the name is not change in Homekit. He lists it as "Switch 1"
In the accessories tab it also indicates it wrong

For example, if I link HomeKit to LG ThinQ, the name is correct.

Hi,

I installed a Shelly Pro 1 with latest firmware and still get unknown device.
Does anyone know why?
It ist a supported device!?

[7/10/2022, 9:01:23 PM] [Shelly NG] [shellypro1-30c6f7813af4] Unknown device of model "SPSW-201XE16EU" discovered.

{"name":null,"id":"shellypro1-30c6f7813af4","mac":"30C6F7813AF4","model":"SPSW-201XE16EU","gen":2,"fw_id":"20220617-111854/0.10.3-g7c89a05","ver":"0.10.3","app":"Pro1","auth_en":false,"auth_domain":null}

After configuring the shelly plus 1 pm manually, i get an error message "[Shelly NG] [shellyplus1pm-441793cf50ec] Unknown device of model "undefined" discovered."

Shelly Plus 1 PM:
{"name":"Treppenhauslicht","id":"shellyplus1pm-441793cf50ec","mac":"441793CF50EC","gen":2,"fw_id":"20220330-151110/0.10.1-g8d603a2","ver":"0.10.1","app":"Plus1PM","auth_en":false,"auth_domain":null}

Any idea?

hej alex!

• only after a clean restart I can control my two shelly plus2pm shutters via homekit.
• shortly therafter I see "No Response" in homekit, and "[Shelly NG] [Rollo Links] Failed to set target position: Invalid password" in homebridge.log (yes, I've gota authentication pwd set)
• via the shelly app I see a correct position; and can control them at all times.

Howto debug and resolve this?!

I'm running version 1.4.1 of homebridge-shelly-ng and get a lot of warnings in the log about too large values for the Voltage characteristic:

[7/17/2022, 2:52:34 PM] [homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 252.7 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.
[7/17/2022, 2:52:46 PM] [homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 252.7 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.
[7/17/2022, 2:53:02 PM] [homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 252.7 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.
[7/17/2022, 2:53:18 PM] [homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 252.6 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.
[7/17/2022, 2:53:34 PM] [homebridge-shelly-ng] This plugin generated a warning from the characteristic 'Voltage': characteristic was supplied illegal value: number 252.8 exceeded maximum of 250. See https://homebridge.io/w/JtMGR for more info.

Those values don't look plausible to me.

Hi, i just got a shelly plus 1 and i have the 0.11.0 Firmware installed, i get this error when in Homebridge, i also tried to add it via the plugin using id and ip of the device but i get the same issue.

is it because of the firmware or is it a new revision of the device? it is weird that the model is "undefined"

here is my /shelly data

{"name":"Licht","id":"ShellyPlus1-63EFAC","mac":"7C87CE63EFAC","gen":2,"fw_id":"20220830-130249/0.11.0-gfa1bc37","ver":"0.11.0","app":"Plus1","auth_en":true,"auth_domain":"ShellyPlus1-63EFAC"}

I just installed an i4 and the Shelly NG Plugin. The device was discovered immediately but HomeKit shows 4 switches instead of 4 buttons. i4 firmware is 0.10.1.

Does anyone know how to solve:
Failed to add discovered device (id: shellyplus2pm-xxxxx): Request timeout

Shelly Plus 2PM

id hidden

probably related to #26

Hello,

I got a new Shelly Plus H&T today, but it's not recognized by the plugin yet. Can you please add support in the future?
If I can support somehow, let me know.

I want to buy an Shelly 1 Pro for my Garage Door. Can I configure this plugin for that? It should be shown in HomeKit as an Garage Door

I deleted a shelly device in the Shelly app. Log file gives the following message:

"Failed to add discovered device (id: shellyplus1-a8032abe6704): Error connecting to device (code: 1006)"

Asked shelly if it was really removed and got the following response

"We couldn't find any information regarding the Shelly Plus 1.

It can be added successfully somewhere else."

How can I get this error out

Greeting Kasper