Just to confirm for you, I re-paired the Trådfri outlet to my hub running 2.1.3.125 and after several attempts (I hate pairing these), it rejoined and works just fine.
1 Like
Just as a data point, I'm on 2.1.6.118 and all six of my outlets are functioning using the Tradfri control outlet driver. All have bin:-1 state variable too.
2 Likes
Me too, I have four outlets in waterproof enclosures in the garden and all have bin:-1.
I use two IKEA Tradfri Signal Repeaters to get Zigbee round the garden - I highly recommend them.
As the other posters above, I have many (15 I think!) Tradfri outlets bought at various different times over the last 12 months and they all work perfectly with the specific Tradfri driver. All have bin:-1. I'm on 2.1.6.118 but these have worked fine on all the previous versions since the specific driver was introduced and on the Generic Zigbee Outlet before that. I know this isn't much help to the OP, but I think it possibly points to a dodgy unit. I'm in the UK but I think the internals of the outlet are universal.
It may be a problem unit, but that doesn't explain why a unit that I've owned for a year now, cannot function when I pair it with the latest build, but works fine when I pair it with 2.1.3.125
It may be that it continues to function if it was paired on an earlier version of the platform, and then if upgraded, it continues to work. But if you were to remove the device and re-pair, or try to pair a new one, it might not work?
PLEASE, DO NOT RISK YOUR WORKING DEVICE TO TEST THIS. WAIT FOR MIKE TO INVESTIGATE
True. I hadn't spotted that part of the thread. That is very odd.
1 Like
I didn't know there was a bespoke driver for these now.
I'm still on the Generic Zigbee Outlet driver. 
1 Like
Steady on!
1 Like
I'm not sure the specific driver changes anything functionally but it does give the option to look at the route table and signal quality in the logs if you want to.
1 Like
I actually added 4 new ones 2 days ago (running 2.1.6.118). A couple of them were a bit slow to get into pairing mode on the unit itself, but they all paired and work fine. I do have a couple of these that aren't doing anything yet (they are ready for Xmas lights). Maybe I should take one for the team and try to remove and re-pair one?
3 Likes
This is strange. I tried several times, pairing and un-paring. Trying Trådfri driver and Generic Driver on version 2.16.117 and then the latest beta build and neither gave any response. Always using the Configure button of course.
Next, reset the outlet and paired it again with my main hub running 2.1.3.125 and as I've said already, it started working again, just as before.
I don't want anyone to unnecessarily end up with a non-working device you need to use. Best just to wait.
So, because @SmartHomePrimer tempted me with his bold type warning 
, I removed and re-paired one. Didn't have any problem pairing and it functions as it should, but did see some weird behavior while pairing. It was discovered three times, with three different ID's, and a fourth time as Device already discovered. I saved all of them, but the third is the only one that appears in my device list and zigbee list.
I would suggest folks check their zigbee device list and make sure there aren't any devices with identical 64 bit addresses.
1 Like
So it showed up 4 times in your device list? I didn't see that happen. Only one entry.
I had pairing issues, but that's been my experience with these. I had the same pairing problems when moving it back to 2.1.3.125, but it works there.
It did not show up 4 times in the device list, but rather 4 times during discovery. I made the last comment about checking the zigbee list thinking maybe multiple instances of the same device could be getting saved and the attempted control of a "ghost" device might be the OPs issue. More unfounded guessing on my part, than anything else.
1 Like
I'm puzzled. Need the experts to step in and help.
@MurphMS, can you please file a support ticket via support@hubitat.com so @bobbyD then has it logged in the support queue.
https://docs.hubitat.com/index.php?title=How_to_collect_information_for_support
1 Like
I’ve emailed them in the past but support told me to move the hub closer. What’s the correct way about getting a ticket opened and assigned ?
https://docs.hubitat.com/index.php?title=How_to_collect_information_for_support
Submit updated info and any logs that may help via the previous support ticket already opened on this.
Every ticket gets assigned 
You could reply to your existing ticket, open a new one or send me a private message to further look into your problem. 
2 Likes
Thanks - I have replied to my pervious email with support and also included this post as background
some general comments.
the state.bin variable is used to distinguish between physical and digital commands in many drivers, in and of itself it will not have any effect on whether an event it produced or not.
In regards to the outlet working on a hub running 2.1.3 and not working on 2.1.6, unless these this problem exists on the same hub being switched between 2.1.3 and 2.1.6 we can't really conclude that the issue is platform related since we're dealing with two different zigbee networks.
Regarding the device joining eventually but not actually working afterwords, I would be interested in what the results are when all the ikea and other bulbs are physically unscrewed from their sockets and then an attempt is made to control the outlet. Note that these bulbs don't need to be removed from HE, just completely powered down, after the bulbs are powered down the outlet should be unplugged then plugged back in to give a chance to find another parent (assuming that it was routing through a bulb) if the outlet now starts working, then the bulb(s) are not forwarding the commands to the outlet.
