[RELEASE] Enhanced Smart Plug Driver

⚙️ Custom Apps and Drivers
41

Steve,

Easier said than done. The 3210-L is on a 4-foot power strip attached to the back of my desk. I left a walkway between the desk and wall, but I just filled most of that space with 8 golf cart batteries stacked 2 wide. It's [ahem] "fun" trying to squat and work back there now.

I reset the plug and got it back into pairing mode. Doing a Zigbee discovery it doesn't show as being found. Went into the device and hit configure anyway. Now it doesn't accept the on command. Guessing there's a good chance that it's failed. Fortunately I bought "a few" (15) of these and therefore have spares.

This is the first one of the 3210-L I've deployed. I had it setup as Zigbee device and Z-wave repeater using both of your drivers. As I mentioned before, I was using it to control a small heater pulling 570-590 watts when running. According to the spec sheet its rated for 12 amps at 120 volts. So it should (by spec) handle 1440 watts. I don't trust specs usually, but thought it should manage significantly less than half specified load.

Since I use the heater a lot, I've pulled the 3210-L and replaced it with my spare Zooz Zen15 which is probably overkill, but I know they work well for heaters as I have several of them in use with other heaters that draw nearly 3 times that wattage.

I think I'm going to trash this one and drag another 3210-L out to test... elsewhere.

Thanks,
Bill

42

It still might not have completely reset so I wouldn’t give up on it just yet.. If it’s in a difficult location you’ll probably want to swap it with a different one so you can work on it in an easier spot..

There’s a second hard reset that you can try... Plug in the smartplug while you hold the button down, but do not release it until the relay fires on its own. That takes about 10 seconds. I’m told that is a factory reset and self-test.. If the relay doesn’t fire after 20 seconds you can bet the plug is a goner.

Good luck! And I know what it’s like to have these things in ridiculous places. That is true for about half of the plugs used in our Christmas lights this year.. I think the builders of my home specifically placed outlets where they knew furniture would hide them.

43

Steve,

I would give a full reset a try, but I'm cautious about any questionable device being in my smart home setup. That's especially true if the device is a repeater. I'm more inclined right now to gut it and use as a project box for a later device build than trust it as a part of my mesh. It was after all only ~$10 and the frustration it could cause down the road is considerable. My piece of mind is more valuable to me than a Hamilton.

Just a heads-up, I have the gear here to setup multiple hubs using HubConnect. So expect more inane questions down the road!

Bill

44

Having an issue with this driver, can't update config, therefore can't pull data.

IRIS IL03_1 plugs according to the back, data from device page as follows:

  • endpointId: 01
  • application:
  • softwareBuild:
  • inClusters: 0000,0003,0006,0402,0B05,FC01,FC02
  • outClusters: 0003,0019
  • model: 1113-S
  • manufacturer: iMagic by GreatStar

Tracing logs show the following:

dev:2792020-02-03 12:38:02.430 am errorPOWER REPORTING CONFIG FAILED- error code:134

dev:2792020-02-03 12:38:02.427 am traceParsed data... Evt: [:], msg: [raw:catchall: 0104 0B04 01 01 0040 00 EDB7 00 00 0000 07 01 86000505, profileId:0104, clusterId:0B04, clusterInt:2820, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EDB7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 05, 05]]

dev:2792020-02-03 12:38:02.420 am traceMsg: Description is catchall: 0104 0B04 01 01 0040 00 EDB7 00 00 0000 07 01 86000505

dev:2792020-02-03 12:38:00.406 am debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x0b, 0x00], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xedb7, isClusterSpecific: false, sourceEndpoint: 0x00, profileId: 0x0000, command: 0x00, clusterId: 0x8021, destinationEndpoint: 0x00, options: 0x0040)

dev:2792020-02-03 12:38:00.402 am warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00

dev:2792020-02-03 12:38:00.399 am traceParsed data... Evt: [:], msg: [raw:catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:EDB7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0B, 00]]

dev:2792020-02-03 12:38:00.383 am traceMsg: Description is catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00

dev:2792020-02-03 12:37:58.405 am errorPOWER REPORTING CONFIG FAILED- error code:134 dev:2792020-02-03 12:38:02.430 am errorPOWER REPORTING CONFIG FAILED- error code:134

dev:2792020-02-03 12:38:02.427 am traceParsed data... Evt: [:], msg: [raw:catchall: 0104 0B04 01 01 0040 00 EDB7 00 00 0000 07 01 86000505, profileId:0104, clusterId:0B04, clusterInt:2820, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EDB7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 05, 05]]

dev:2792020-02-03 12:38:02.420 am traceMsg: Description is catchall: 0104 0B04 01 01 0040 00 EDB7 00 00 0000 07 01 86000505

dev:2792020-02-03 12:38:00.406 am debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x0b, 0x00], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xedb7, isClusterSpecific: false, sourceEndpoint: 0x00, profileId: 0x0000, command: 0x00, clusterId: 0x8021, destinationEndpoint: 0x00, options: 0x0040)

dev:2792020-02-03 12:38:00.402 am warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00

dev:2792020-02-03 12:38:00.399 am traceParsed data... Evt: [:], msg: [raw:catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:EDB7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0B, 00]]

dev:2792020-02-03 12:38:00.383 am traceMsg: Description is catchall: 0000 8021 00 00 0040 00 EDB7 00 00 0000 00 00 0B00

dev:2792020-02-03 12:37:58.405 am errorPOWER REPORTING CONFIG FAILED- error code:134

Any Ideas?

45

Did you read this?

I think the driver is not compatible with Iris 3rd version

46

Im very confused by iris... I have now been told these are v1, v2, v3, and also told they aren't iris plugs at all ... guess ill never get them working properly, but thank you for the fast reply!

47

They work, but this driver is not for it, the v3 doesn't have z wave, it's zigbee only. Only the v2 has zigbee for controlling the device and z wave for repeating z wave.

Just use the driver HE hub chose when you added the device.

Good luck.

They where made by Centralite, same as some of Smartthings plugs

48

it doesn't pick one, labels it device. Selecting generic zigbee outlet doesnt give any power features but allows the switch to work. Power monitoring is the main reason i have these :confused:

49

Ohh wait a minute, let me look for something, don't go, I will edit this post

Yeah, I looked and no reports of power is the way. I thought I had a driver from smartthings but it was for a v3 motion. Sorry.

50

its all good thank you for taking the time to reply and look.

51

I'm afraid I have bad news. These are the lower cost 3rd generation of Iris devices. This plug in particular, does not support power monitoring unlike its' predecessors. Oddly it does support temperature monitoring, but I have no plans to add that to the driver as any readings would be influenced by the plugs own electronics making them useless.

52

Thank you. I had been using the Generic Zigbee Switch driver for the two Iris V2 outlets I have. This is much better. Any chance of having a version that works for Iris V1 outlets (AlertMe SmartPlug 2.5)?

53

There's already a native driver in Hubitat for that. I don't think I can add anything of value to that driver. After looking at the Arcus code, I do not see a way to configure the power reporting intervals. They seem to be fixed in the plugs firmware.

54

Lovely...

Now that I have my hub and understand the system and how to use it, 90% of the info i looked up in the hubitat docs and on these forums before making any of my home automation purchases have turned out to be false or highly misleading.

Im starting to think I'd be better off returning my hub and going with HA on a pi4... seems like id have far more power and functionality, for less cost, just the trade off in ease of initial set up.

I mean i cant even run tinycam on them to transcribe my rtsp feeds, or assistant relay, where a pi 4 can easily handle all that node red and more with no slowdowns and at a lower price.

Am I missing something that really does make these hubs worth the cost we paid?

Sorry to derail the thread, that wasnt my intent, just a bit frustrated and trying to understand why anyone is keeping these once realizing just how limited they really are.

55

I have some of those.. It works with the generic zigbee outlet driver included in he

56

But the device has no power reporting feature.. And that is a limitation of the device not HE

1 Like
57

There are definitely Pros and Cons to every solution. Hubitat excels at providing a home automation platform, with cloud connectivity and excellent Zigbee and Z-Wave device support for a very low one-time cost of $75 (current price as of this writing.)

A Raspberry Pi 4, 4GB, with a 32GB uSD card, case, power supply, cooling fan, etc. will easily run you more than $75. And that does not include Zigbee and Z-Wave radios, which will set you back another $35 at least (assuming you use the same USB stick Hubitat used on the original C3/C4 hubs.) And, this solution while very powerful and capable, does not include a secure cloud endpoint server to have at your disposal. Poking holes (i.e. port forwarding) in one's router leads to serious security concerns. The Home Assistant Cloud service is an extra $5 per month...

So, as far as cost, I really don't believe one can build what Hubitat offers for less money, assuming you have to buy everything from scratch. And as you have mentioned, the learning curve to configure/run Home Assistant to accomplish everything Hubitat does out of the box, is pretty steep.

For the folks here in this Community, most like what Hubitat offers, especially when compared to cloud-based home automation platforms like SmartThings, Iris, and Wink. For those who are hard-core DIYrs, Home Assistant on a RPi is a very attractive offering. Some folks even run both side-by-side, using the strengths of both systems.

But cost between the two is really not a differentiating factor that would lead users to choose the custom solution over Hubitat. I would guess that the main hub in most home automation setups is only a fraction of the total cost. The devices are where 99% of my money has been spent.

Options are a good thing! :wink:

6 Likes
58

I’m not sure how you got from point A to point B on this. The plug, made by Lowe’s for the now defunct Iris system works perfectly with Hubitat using the Generic Zigbee Switch driver. It just doesn’t support power monitoring. That’s not a fault of Hubitat. No matter what platform you use, that plug ain’t ever going to report energy.

HA and Haas simply doesn’t have the device support that Hubitat has. For example, Zigbee devices are limited and it takes a bit of work to get them going. Plus, with Hubitat you can pretty much use any device or integration available on SmartThings too.

Someone is going to have to actually prove that. I have a Pi 4 and it isn’t hard to slow it down at all. Video transcoding is very CPU hungry. Once you get a couple transcoder sessions going it starts to bog down pretty good.

At least. I did a quick check and it’s closer to $100 not including the older style radio stick.

HA isn’t ready to run out of the box like Hubitat is. It’s reasonable to say that a user can get his first device connected within 10 minutes of unboxing. It’ll take at least that long to assemble the Pi.

Then you have to image the OS, configure it, secure it (a step few know how to properly do), and install HA, find the right drivers, etc.

I tried it a year ago and it wasn’t for me.

5 Likes
59

pi4 8gb $55 with case fan etc....

never mind. not going to get a response that is actually of any use or bothers to actually read my original issues with the platform which is documentation and claims, plus not the right place!

Back to the topic, so the author can continue his work :slight_smile:

60

Good luck with whatever hub you end up on. :+1:

7 Likes