Thanks, the specs say clamps are only rated to 97A, my main breaker is 100A.
Are these certified in Australia? There’s no manual or documentation on the site.
There’s what looks like a C-tick on it, which was an old compliance mark. See: A-Tick and C-Tick logo approval in Australia | EMC Bayswater Pty Ltd
I’d ask to see the compliance certification.
1 Like
And 20 in Perth Aparently
This isn’t the smart plug with energy monitoring, this is just the existing new smart plug replacement for the Tradfri.
1 Like
Sorry, yes you’re right, I should have spotted that.
If it’s the S3 then you need to open them up if you don’t want Tuya. They changed the Beken chip to one not supported by ota cloudcutting. Otherwise functionally the same.
1 Like
Yes. They look identical, even the packaging. Latest builds state “Series 3” on the back of the plug. I had to open it, desolder Tuya board, flash via uart/usb, and then reassemble.
2 Likes
I asked Athom if there was certification and if there was a 100A CT option. In response they said:
The controller is separate, your actual current should not exceed 100A.
So I might steer clear 
I think between the somewhat expected reliability issues of these plugs now emerging as a pattern and not being able to flash these OTA, it’s hard to recommend anyone tries these plugs. Even for 10 bucks.
I’ve yet to have a failure on any device in over a year. I have 8 Arlec’s, some Athom’s, and generic China devices. Rarely switch under load so will see how that pans out. Opening and flashing wasn’t too hard so I would probably use more if required. Not that obvious it’s been opened.
1 Like
I’ve seen a few reports like this starting to pop up.
Time will tell. Mine have been good so far.
I have a few of the generic china zigbee ones, so far they have been working without issues but I still don’t recommend them without risk as they are not certified as looked up when I first posted about them.
So I’ve managed to get the Arlec MAL315HA and MAL352HA working reasonably well via xZetsubou’s fork of LocalTuya.
Fortunately with this updated version you can export/import device configs.
I’ve setup what I think are all the DP’s with either the original name from the Tuya API, or in the case of the MAL315HA what seems to be close enough to make sense (also based off this post and the 352’s DP names).
I’ve spent a bunch of time just staring at them to see if I could make them any better/simpler, but meh - for your perusal and ideas… with the following caveats…
In the case of the MAL315HA, you can use the light_state binary sensor to see whether the light is on as a pseudo occupancy/motion, and the mode select_option to manually turn it on/off/auto (in my main use case, Node Red switches it to on, then back to auto after a 5 min timer).
For the MAL352HA, I haven’t spent a huge amount of time working out what the switch_pir does vs setting device_mode to auto, but based of setting it via the Tuya Smart app - which now loads the Arlec screen for the device) it seems to be a specific switch just for the PIR. Not sure in what use case you’d have the PIR off but the device set to auto.
Also, on reflection whilst posting this, I noticed that on the MAL352HA it’s pir_state as per the Tuya DP name from the API, whereas the same one for the MAL315HA is light_state.
MAL315HA.yaml:
- select:
entity_category: config
friendly_name: device_mode
icon: ''
id: '101'
is_passive_entity: false
platform: select
restore_on_reconnect: false
select_options:
mode_auto: Auto
mode_off: 'Off'
mode_on: 'On'
- number:
entity_category: config
friendly_name: pir_sensitivity
icon: ''
id: '103'
is_passive_entity: false
max_value: 4.0
min_value: 0.0
platform: number
restore_on_reconnect: false
step_size: 1.0
- number:
entity_category: config
friendly_name: pir_light_duration
icon: ''
id: '104'
is_passive_entity: false
max_value: 900.0
min_value: 10.0
platform: number
restore_on_reconnect: false
step_size: 1.0
- number:
entity_category: config
friendly_name: pir_light_level
icon: ''
id: '105'
is_passive_entity: false
max_value: 3900.0
min_value: 0.0
platform: number
restore_on_reconnect: false
step_size: 1.0
- switch:
entity_category: config
friendly_name: reset_to_auto
icon: ''
id: '106'
is_passive_entity: false
platform: switch
restore_on_reconnect: false
- binary_sensor:
entity_category: diagnostic
friendly_name: light_state
id: '102'
platform: binary_sensor
state_on: 'True'
MAL352HA.yaml:
- light:
brightness: '22'
brightness_lower: 10
brightness_upper: 1000
color_mode: '21'
color_temp: '23'
color_temp_max_kelvin: 6500
color_temp_min_kelvin: 2700
color_temp_reverse: false
entity_category: None
friendly_name:
icon: ''
id: '20'
music_mode: false
platform: light
scene_values: {}
- select:
entity_category: config
friendly_name: pir_light_level
icon: ''
id: '53'
is_passive_entity: false
platform: select
restore_on_reconnect: false
select_options:
10lux: 10 lux
2000lux: 2000 lux
300lux: 300 lux
50lux: 50 lux
5lux: 5 lux
- select:
entity_category: config
friendly_name: pir_sensitivity
icon: ''
id: '54'
is_passive_entity: false
platform: select
restore_on_reconnect: false
select_options:
high: High
low: Low
middle: Medium
- number:
entity_category: config
friendly_name: pir_light_duration
icon: ''
id: '55'
is_passive_entity: false
max_value: 3600.0
min_value: 5.0
platform: number
restore_on_reconnect: false
step_size: 1.0
- switch:
entity_category: config
friendly_name: switch_pir
icon: ''
id: '56'
is_passive_entity: false
platform: switch
restore_on_reconnect: false
- binary_sensor:
entity_category: diagnostic
friendly_name: pir_state
id: '52'
platform: binary_sensor
state_on: 'True'
- select:
entity_category: config
friendly_name: device_mode
id: '51'
is_passive_entity: false
platform: select
restore_on_reconnect: true
select_options:
auto: Auto
manual: Manual
- number:
entity_category: config
friendly_name: standby_time
id: '58'
is_passive_entity: false
max_value: 480.0
min_value: 1.0
platform: number
restore_on_reconnect: false
step_size: 1.0
unit_of_measurement: min
- number:
entity_category: config
friendly_name: standby_bright
id: '59'
is_passive_entity: false
max_value: 1000.0
min_value: 0.0
platform: number
restore_on_reconnect: false
step_size: 1.0
- number:
entity_category: config
friendly_name: countdown
id: '26'
is_passive_entity: false
max_value: 86400.0
min_value: 0.0
platform: number
restore_on_reconnect: false
step_size: 1.0
unit_of_measurement: s
1 Like
I have had these running for probably 3-4 years now and no issues. Odd drop out using Local Tuya but stays connected to Tuya integration.
Has anyone using Ikuu light switches managed to find a way to disable back light for TS0001 or TS0002 or anyone for that matter.
Have tried setting through cluster but no effect.
Back on the 29th of Nov (11am) I got the following notification that it was back in stock at my local. I’ve had notifications for stock at Ikea before and this one was very different with it urging me to click and collect!
A limited number of INSPELNING are back in stock at IKEA Canberra. It’s a popular product so consider buying using our click and collect option to ensure you get it. Check for its availability before going to the store.
But I was too slow, and THAT AFTERNOON it was already out of stock!! I don’t know what they are playing at by removing it, but hopefully it’s just a supply issue and they are waiting until they have a proper amount stock before putting it back up again. (ideally not with a higher price tag!)
I can confirm that though they no longer show up on the website, if you have them in your browsing history in the app you can find them. The only store that has any in stock is Richmond, which has 7 currently in stock, and they can be purchased, and there is a shelf labeled for them. So they haven’t been discontinued after all, just a weird rollout.
I’ve got Pixie wall dimmers and I can’t find any simple way to integrate them into HA.