Has any one managed to get state from NUE Smart Zigbee Gadgets | Wall Mount Light Switch | 4 Gang?
I can turn them on and off but I don’t get the state when manually turned on or off. 3 Gang model works with no issues.
deConz + ZHA
Finally putting my Brilliant fan controllers to use after they sat in a box for a year. I flashed the first one with Tasmota and tried to follow this guide for the settings, but I think I have the MQTT topics messed up. Can anyone please help me out? The guide doesn’t explain the MQTT in detail and this is my first Tasmota device.
This is what I have in the info page on Tasmota:
Tuya MCU Module
Tasmota
| Program Version | 8.1.0.2(tasmota) |
|---|---|
| Build Date & Time | 2019-12-30T19:07:34 |
| Core/SDK Version | 2_6_1/2.2.2-dev(38a443e) |
| Uptime | 0T00:24:50 |
| Flash write Count | 59 at 0xF9000 |
| Boot Count | 15 |
| Restart Reason | Power on |
| Friendly Name 1 | Tasmota |
| Friendly Name 2 | Tasmota2 |
| AP1 SSId (RSSI) | DR_i_24g (54%, -73 dBm) |
| Hostname | Bedroom Fan |
| IP Address | 192.168.0.131 |
| Gateway | 192.168.0.1 |
| Subnet Mask | 255.255.255.0 |
| DNS Server | 192.168.0.1 |
| MAC Address | xx:xx:xx:xx:xx:xx |
| MQTT Host | 192.168.0.14 |
| MQTT Port | 1883 |
| MQTT User | hassio_mqtt |
| MQTT Client | Bedroom_Fan |
| MQTT Topic | tasmota/fans/master_bedroom |
| MQTT Group Topic | tasmotas/cmnd/ |
| MQTT Full Topic | tasmota/fans/master_bedroom/cmnd/ |
| MQTT Fallback Topic | cmnd/Bedroom_Fan_fb/ |
| Emulation | Disabled |
| mDNS Discovery | Disabled |
Ignore the old MQTT username, I couldn’t be bothered changing it!
In HA:
fan:
- platform: mqtt
name: "Fan Master Bedroom"
command_topic: "tasmota/fans/master_bedroom/cmnd/POWER1"
state_topic: "tasmota/fans/master_bedroom/tele/STATE"
state_value_template: "{{ value_json.POWER1 }}"
speed_command_topic: "tasmota/fans/master_bedroom/cmnd/Backlog"
speed_state_topic: "tasmota/fans/master_bedroom/tele/RESULT"
speed_value_template: >
{% if value_json.TuyaReceived.Data == "55AA03070005030400010016" %}
Power1 1; TuyaSend4 3,0
{% elif value_json.TuyaReceived.Data == "55AA03070005030400010117" %}
Power1 1; TuyaSend4 3,1
{% elif value_json.TuyaReceived.Data == "55AA03070005030400010218" %}
Power1 1; TuyaSend4 3,2
{% endif %}
availability_topic: tasmota/fans/master_bedroom/tele/LWT
payload_available: Online
payload_not_available: Offline
payload_low_speed: "Power1 1; TuyaSend4 3,0"
payload_medium_speed: "Power1 1; TuyaSend4 3,1"
payload_high_speed: "Power1 1; TuyaSend4 3,2"
payload_off: "OFF"
payload_on: "ON"
qos: 1
retain: false
speeds:
- low
- medium
- high
light:
- platform: mqtt
name: "Light Master Bedroom"
command_topic: "tasmota/fans/master_bedroom/cmnd/POWER2"
state_topic: "tasmota/fans/master_bedroom/tele/STATE"
state_value_template: "{{value_json.POWER2}}"
availability_topic: "tasmota/fans/master_bedroom/tele/LWT"
brightness_command_topic: "tasmota/fans/master_bedroom/Dimmer"
brightness_state_topic: "tasmota/fans/master_bedroom/tele/STATE"
brightness_scale: 100
on_command_type: "brightness"
brightness_value_template: "{{value_json.Dimmer}}"
payload_on: "ON"
payload_off: "OFF"
payload_available: "Online"
payload_not_available: "Offline"
qos: 1
retain: false
The above is largely copied from the blog post but i tried to update the MQTT topics. Not sure if the json data bit needs to be updated to relate to my specific device also?
EDIT: I think it is actually working… I don’t have it connected to anything at the moment so just trying to see if HA reflects what I press using the wireless remote. Looks good, time to wire it up
you have the topics in reverse at first glance… and extended beyond normal. reverse isn’t necessarily a problem except auto discovery does it in reverse to what you have I think. cmnd and tele are usually first.
should be:
MQTT Client DVES_009C34
MQTT Topic ESP-ir
MQTT Group Topic cmnd/tasmotas/
MQTT Full Topic cmnd/ESP-ir/
MQTT Fallback Topic cmnd/DVES_009C34_fb/
responses would be
tele/ESP-ir/STATE
the tasmota device console should show how the responses are showing up if you can see it.
You can compare with my blog post about the same fan controller. I have partially used auto-discovery, for example for the light. However, as soon as you configure auto-discovery on the Tasmota device (SetOption19 1) the MQTT topic order changes.
1 Like
The Kogan Smart kettle is half price at the moment if anyone is interested.
Hey All,
I’m trying to get a Bahama Smart DC ceiling fan up and running as @exxamalte has done above.
So far i’ve been unable to flash it with tuya-convert (assumption is i’m running the latest 2.4.4). It’s just not picking up any available devices and timing out. Interestingly, i’m not seeing obviously SSID coming from the controller. This tuya-convert setup recently did some genio LED strips.
To get into pairing mode (there is no reset button etc) I’ve tried just powering it up and also powering it up and then holding the remote “fan on” button for 10 seconds until I hear a second been as confirmed by Malte and the booklet. I’ve also tried 3 quick-ish power cycles to no avail.
I assume its likely i’ve just purchased it too late for the older tuya-convert capable firmware.
Inside the controller is a TYWE2S with accessible pins at the bottom.
I guess I shouldn’t have much trouble with a serial flash but i’d prefer to avoid it.
Before things get messy i’m going to try and figure out how to get tuya-convert 2.3 onto my pi and try again.
A big question I have is: if its determined I have no choice but to serial flash it, is there any harm in getting it connected to my phone with the brilliant app, make sure its working and seeing how far I get with things like tuya-local, native tuya integration etc?
Yes i’d much rather tasmota but If it were to be fully functional through the cloud in HA with reverse directions, all speeds etc then its not a bad outcome - until another firmware kills that off too 
At which time I could pull the controller and flash it.
Any insights would be great - its almost summer and i’d say there are a few of us looking at this. Would love to provide another guide for people.
Cheers,
Linton
1 Like
It looks like you may be hitting the PSK Identity issue that is preventing Tuya-Convert from working with newer devices (I hit this issue with my newer Brilliant Smart Dimmer mechs - these also use TYWE2S modules inside)
You can always flash using serial regardless of what version of Tuya firmware is running on the TYWE2S. But based on your photos, you might find it tricky accessing the IO0 pad which needs to be pulled to GNS in order to enter programming mode (The pad sits directly behind that big capacitor in your first pic):
Good luck - let us know how you go.
1 Like
Yeah I’m thinking I can reach the GPIO0 pad with a breadboard jumper lead 
I’ll be breaking out the soldering gear tomorrow
Progress!
Picked up a set of the 800 LED bulbs today.
No luck doing Tuya Convert. Opened up the control box and the chip is a Tuya WB3L chip.
1 Like
Quick question for you gurus. I assume Oz is similar or the same as NZ. What’s the deal with plugging in micro controllers around the house via wall wart etc. being extra low voltage they are sweet as? Wall wart is obviously required to be compliant? If the device interfaces (ie switches mains voltages) then I assum
The electrical approval is the same for both countries, there is a joint NZ/AU standard.
Yes you can plug, say, an esp device into a wall wart. But as you say, if it controls a mains voltage it needs to be approved.
I’ve had my eye on these lights for ages but wondering if they can be flashed with Tasmota / ESPhome. I can’t find any evidence of anyone doing it. Did you try at all?
Does this mean that it can’t be flashed by tasmota or esphome?
Was thinking of getting these too not sure if this is a deal breaker or not
Yes it is a deal breaker.
Hi All,
I have a tricky problem with 3 out of my 6 Brilliant Ceiling fan controllers flashed with Tasmota on latest version 9.1.0.1, was also happening on earlier versions, I updated them all as a troubleshooting step (see https://templates.blakadder.com/brilliantsmart_99111.html, I followed https://newadventuresinwi-fi.blogspot.com/2019/12/brilliant-smart-ceiling-fan-remote-in-home-assistant.html and got a lot help from @oscill8ory)
I got these about 11 months ago and now 3 don’t work via their remotes (which run on 433.9MHz frequency). These all work correctly in Tasmota/Home Assistant and there appear to be no differences between the logs of the ones that do work and don’t. They all worked out of the box when I got them, now given it’s summer again I find these issues. One positive is other house members now have to use Apple Home to turn them on and it means I can do way with physical wall switches in the future (I can dream)
What have I done:
Changed batteries in remotes
Changed the dip switches on the remote of one not working to a fan that does work and it works (so says the remote is ok)
I want to get some help to see if this could be software or hardware?
I can still return them (under 12 month warranty) but concerned returning 3 might raise questions, given I can’t put the original firmware back on there (with out soldiering as did these via OTA and do have some parts/tools to do a serial connection I would prefer not to) if they want to check they refuse the exchange.
Thanks for any help.
I had a quick scan back through this big post, but couldn’t find out the latest update.
Are the Arlec Grid connect devices still flashable with Tuya Convert. Specifically the powerboard https://www.bunnings.com.au/arlec-grid-connect-smart-4-outlet-powerboard-with-usb-charger_p0074829
I bought one about a month ago and it flashed fine via tuya convert. I used an ESPHome implementation.
Good news. Thanks.
Hi There
Anyone had any luck flashing these https://www.bunnings.com.au/deta-grid-connect-smart-7w-led-downlight_p0102572 with Tasmota lately?
I purchased 4 a few months ago and flashed them all successfully with tuya convert and they work perfectly. So i went and purchased another 4 a few days ago and now no go! could it be the new tuya firmware issue?
I might need to flash them via serial but it looks like a pain to solder.