[BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

p.kaczmarek2 178080 1242

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Reply Cool? Ranking DIY | New topic

Notify about new articles

#871 20148005 17 Aug 2022 16:08

staszek_org staszek_org

Level 2

» | Helpful post? (0)

Post #871
20148005 17 Aug 2022 16:08

Is it possible to port WLED https://kno.wled.ge/ to light bulbs supporting OpenBaken, since Baken microcontrollers are very similar to ESP (WLED works on ESP)?
And would it be difficult?
ADVERTISEMENT
#872 20148036 17 Aug 2022 16:28

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (+1)

Post #872
20148036 17 Aug 2022 16:28

@staszek_org what exactly functionalities do you need from this? OpenBeken "bulbs" do not operate on NeoPixel (WS2812B, WS2811, SK6812).

EDIT: is it about animation? This project probably also supports other systems than Neopixel, so maybe that's it ..

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#873 20150147 18 Aug 2022 20:41

Tych0 Tych0

Level 6
Helpful post? (+1)

Post #873
20150147 18 Aug 2022 20:41

p.kaczmarek2 wrote:
I really need to get more test devices.

@everyone so... make a donation to support the project!!

p.kaczmarek2 wrote:
@Tych0 it should be fixed now, but to be honest, I have no idea how you managed to get CW light working in earlier version without setting dummy PWMs for RGB, the correct solution has been added just today and still it's not a final one as I don't have such light to test....

Ok maybe we are not on the same page then. What I understand, you mean by setting 'dummy pins' is: setting pins for RGB that are not really existing. What I did is, I only set channel 4 and 5 for the pins that are actually connected. Like I did with this light: https://www.elektroda.com/rtvforum/topic3911757.html

p.kaczmarek2 wrote:
I would like to get all the outputs for the given commands. Or maybe try 4MB instead of 2MB, not sure now how much memory that BK has.

Earlier this week I received the A9 WiFi Cam. I created the dumps as you requested. But the dumps with parameter '-s 0x0' failed with the error :
uartprogram a9_3.bin -d /dev/tty.usbserial-0001 -r -l 0x200000 -s 0x0
Code: text Expand Select all Copy to clipboard
UartDownloader.... Read Getting Bus... Gotten Bus... Set baudrate successful len: 200000 startAddr: 0 Reading 0 ReadSector Failed 0

The other dumps are added as attachments. The last one is a 4mb dump.
Outputs of the commands:
Code: text Expand Select all Copy to clipboard
uartprogram a9_1.bin -d /dev/tty.usbserial-0001 -r UartDownloader.... Read Getting Bus... Gotten Bus... Set baudrate successful len: 119000 startAddr: 11000 Reading 11000 ReadSector Success 11000 len 1000 ... CRC should be ff7d658a CRC is ff7d658a Wrote 119000 bytes to a9_1.bin

Code: text Expand Select all Copy to clipboard
uartprogram a9_2.bin -d /dev/tty.usbserial-0001 -r -l 0x200000 UartDownloader.... Read Getting Bus... Gotten Bus... Set baudrate successful len: 200000 startAddr: 11000 Reading 11000 ReadSector Success 11000 len 1000 ... CRC should be a2aa9e9c CRC is a2aa9e9c Wrote 200000 bytes to a9_2.bin

Code: text Expand Select all Copy to clipboard
uartprogram a9_3.bin -d /dev/tty.usbserial-0001 -r -l 0x400000 UartDownloader.... Read Getting Bus... Gotten Bus... Set baudrate successful len: 400000 startAddr: 11000 Reading 11000 ReadSector Success 11000 len 1000 ... CRC should be 1a1299f9 CRC is 1a1299f9 Wrote 400000 bytes to a9_3.bin

Looking forward on getting on progress on this BK7252

Attachments:

a9_3.bin Download (4 MB)

a9_2.bin Download (2 MB)

a9_1.bin Download (1.1 MB)
#874 20150573 19 Aug 2022 05:59

ferbulous ferbulous

Level 18

Helpful post? (0)

Post #874
20150573 19 Aug 2022 05:59

Hi @p.kaczmarek2
Trying it on tuya relay device, it's N device, flashed the QIO.bin and hooked it to main.
But I'm not seeing the openbk ap. Then i flashed the UA.bin but still the same issue,
Any ideas why or how to fix this
#875 20150746 19 Aug 2022 10:15

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Topic author Helpful post? (0)

Post #875
20150746 19 Aug 2022 10:15

@ferbulous Did you flash it to correct offset?
What is the debug output of the device?

@Tych0 good to see someone else with this camera, altough I mostly meant the bootloader so data starting at 0x0

Maybe we should try SDKs for BK7252
https://chowdera.com/2021/07/20210727131509465r.html
env_released_1.1.3.7z ?

https://docs.dfrobot.com.cn/DFRobot-BK7252/

this file looks like Arduino core for BK7252, anyone wants to try installing it?

Dodano po 13 [minuty]:

Dodano po 3 [minuty]:

It seems that compiler has to be manually placed:
Quote:

exec: "/bin/arm-none-eabi-g++": file does not exist
Error compiling for board FireBeetle BK7252.

edit ah ok you install it by:
Code: text Expand Select all Copy to clipboard
http://download.dfrobot.top/DFRobot-BK7252/package_bk7252_index.json

Dodano po 8 [minuty]:

Dodano po 9 [minuty]:

it compiles something, and that's it for me now, as I am away from home and don't have BK at hand

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#876 20151316 19 Aug 2022 15:54

Dark Man Dark Man

Level 13
» | Helpful post? (0)

Post #876
20151316 19 Aug 2022 15:54

I will share my latest struggles.
About 3 months ago I bought a light bulb at Action and immediately after that I tried to take it apart to find out what chip it is based on.
Opening it ended with breaking the casing a bit and tearing out the pads connecting the power supply with the PCB with LEDs.
Unfortunately, it turned out that there is no ESP but the WBLC9 module on the BK7231T chip and I left it for a better time.

Today, having some time, I returned to her.
I desoldered the module, downloaded three times the original firmware (not yet connected to Wifi) - attached (maybe it will be useful for cludcutter, because I did not find this bulb in the profiles)
I have uploaded your latest firmware and detected the following pin configuration:
R: P8 PWM 1
G: P9 PWM 2
B: P24 PWM 3
C: P26 PWM 4
W: P7 PWM 5
I soldered the module, connected the broken pads with cables and it works :)

https://www.action.com/pl-pl/p/inteligentna-wielokolorowa-arowka-led-lsc-smart-connect3
Intelligent multi-color LED bulb LSC Smart Connect
470 lumens
5W
E14
case model: 970721

Attachments:

bk7231s_dump-2022- 8-19-14-43-40.bin Download (956 KB)

bk7231s_dump-2022- 8-19-14-43- 3.bin Download (956 KB)

bk7231s_dump-2022- 8-19-14-32-58.bin Download (956 KB)
#877 20151366 19 Aug 2022 16:31

ferbulous ferbulous

Level 18
Helpful post? (0)

Post #877
20151366 19 Aug 2022 16:31

p.kaczmarek2 wrote:
Did you flash it to correct offset?
What is the debug output of the device?

Do you mean this?
Code: text Expand Select all Copy to clipboard
python uartprogram C:\Users\theba\Desktop\Openbkt\OpenBK7231N_UG_1.12.38.bin -d com5 -w -u -s 0x0

This worked for my other N devices
Just tried flashing on my 2nd tuya relay device, and it's the same thing again, the ap's not showing up

As for the debug output, I'll need to find my 2nd uart. So I just need hook it up to tx2, rx2 and how do I get to the console?
ADVERTISEMENT
#878 20151398 19 Aug 2022 16:57

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #878
20151398 19 Aug 2022 16:57

Just hook it up. Your USB dongle RX to the CB2S TX2.

Wait.... for N, I always flashed QIO binary, not UG. I haven't even tested if flashing UG works.

As far as I remember, UG is for tuya-cloudcutter.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#879 20151474 19 Aug 2022 18:08

ferbulous ferbulous

Level 18

Helpful post? (0)

Post #879
20151474 19 Aug 2022 18:08

p.kaczmarek2 wrote:
Just hook it up. Your USB dongle RX to the CB2S TX2.

Wait.... for N, I always flashed QIO binary, not UG. I haven't even tested if flashing UG works.

As far as I remember, UG is for tuya-cloudcutter.

Then I would just use putty, and go to COM5 (for the uart I'm using) to see the logs, correct? Just the TX2, so no RX2
Looks like it's working now, I'm not sure why it wasn't working previously when I already had flashed UG.

As for resetting the device, is there another method now other then cutting off the power 6-7 times until it resets?

Trying to configure the pins now, I've got the relays but not the buttons

Relay
L1 - P24
L2 - P17
L3 - P26
L4 - P6

Button
P8
P9
P15
P17
P28

On stock firmware, one of them is the buzzer, but I'm not sure how to configure that one. I've assigned the remaining pins as button but it's not toggling any relays yet. Any thoughts on this?

This is the device https://www.aliexpress.com/item/1005003425831720.html
#880 20152569 20 Aug 2022 14:33

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #880
20152569 20 Aug 2022 14:33

ferbulous wrote:

Then I would just use putty, and go to COM5 (for the uart I'm using) to see the logs, correct? Just the TX2, so no RX2

Yes

ferbulous wrote:

Looks like it's working now, I'm not sure why it wasn't working previously when I already had flashed UG.

So WiFi is up and it's ok?

ferbulous wrote:

As for resetting the device, is there another method now other then cutting off the power 6-7 times until it resets?

clearConfig command in console will clear all config if that's what you mean, otherwise only power cycling I think

ferbulous wrote:

. I've assigned the remaining pins as button but it's not toggling any relays yet. Any thoughts on this?

Check the PCB if there is really a button on this pin. Maybe this device has some extra pull up or pull downs resistor that are not expected by the firmware? Firmware assumes that button connects pin to ground and IO uses built-in pull up resistor.

ferbulous wrote:

This is the device https://www.aliexpress.com/item/1005003425831720.html

I can buy that one if you need to get it working

ferbulous wrote:

buzzer

what is the role of the buzzer there? Is it on PWM pin?

To confirm - you are able to toggle relays through the web page, but not by buttons?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#881 20153328 21 Aug 2022 05:35

ferbulous ferbulous

Level 18

Helpful post? (0)

Post #881
20153328 21 Aug 2022 05:35

p.kaczmarek2 wrote:
So WiFi is up and it's ok?

Working fine now

p.kaczmarek2 wrote:
Check the PCB if there is really a button on this pin. Maybe this device has some extra pull up or pull downs resistor that are not expected by the firmware? Firmware assumes that button connects pin to ground and IO uses built-in pull up resistor.

I'll test it again with another rocker switch

p.kaczmarek2 wrote:
what is the role of the buzzer there? Is it on PWM pin?

To confirm - you are able to toggle relays through the web page, but not by buttons?

On the stock firmware, buzzer was for pairing wifi indication it seems since it doesn't have led indicator.
That's correct, I can toggle relays from the webpage, not yet with the buttons
#882 20155052 22 Aug 2022 09:24

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #882
20155052 22 Aug 2022 09:24

Thanks for the firmware dumps, @ darkman1. I have already handed them over to where they need to be.

What method did you desolder the module with? I'm going to throw in youtube video showing how I desolder the WB2L_M1 module with the cheapest soldering iron from Tuya LED Bulb E14, so it may be useful to someone.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#883 20155066 22 Aug 2022 09:35

Dark Man Dark Man

Level 13

» | Helpful post? (0)

Post #883
20155066 22 Aug 2022 09:35

I did this module desoldering mainly with hot air from the soldering station
WEP 872D
because there were 8 pins to be desoldered at once.
When assembling (soldering the module and PCB with LED) and connecting the cables, I used a butt from the same soldering station.
#884 20155083 22 Aug 2022 09:49

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #884
20155083 22 Aug 2022 09:49

I have a different way, better for beginners / people without equipment.

Flux + lead binder (the most common tin) given on the pads in large quantities works wonders.

In fact, you had this lamp with a motion sensor what ADC needed? I have already added ADC and it works for BK.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#885 20155106 22 Aug 2022 12:00

Dark Man Dark Man

Level 13

» | Helpful post? (0)

Post #885
20155106 22 Aug 2022 12:00

I would do the same if I did not have hot air
It is true that the module that I desoldered WBLC9 had pins / pads on both sides, so it would be more difficult, but it would probably work
(can be combined with a pen dust extractor or a copper braid)

Yes, I had this LSC floodlight with ADC. Then I did a transplant on the ESP-12 module. It is true that, from what I remember, motion detection worked strangely (even on Tasmot) - it detected one time and the LEDs could turn on without motion. I put it somewhere at home to mount it for tests (not in the workshop), somewhere outside, only temporarily sealing the sensor housing, but when I put it, it has not been installed since then
And the time will come for her someday :P

Added after 1 [hours] 59 [minutes]:

In my resources I found a quite old Smart socket that I used at the beginning of my adventure with smart home.
energy EG-PM1W-001
Ralink RT5350F chip
+ probably memory bone

From what I remember, the interface was via a browser plus some manufacturer's cloud
I remember that the interface was clunky and very heavy, so you didn't feel like using it.

Do you know anything related to the chip type?
Maybe something fresh could be uploaded there?
ADVERTISEMENT
#886 20155339 22 Aug 2022 12:54

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #886
20155339 22 Aug 2022 12:54

I do not know this RT5350F chip, but from what I can see there are even open hardware projects on it:
https://www.olimex.com/Products/OLinuXino/RT5350F/RT5350F-OLinuXino/open-source-hardware
https://www.olimex.com/Products/OLinuXino/RT5350F/RT5350F-OLinuXino-EVB/open-source-hardware
Some SDKs are also:
https://github.com/search?q=RT5350

You could probably make a port, but unfortunately, as long as only one socket with this system is known, I do not know if I will find time for it, because there are more popular systems and features to be added in the queue.

And as for this ADC floodlight, how much did it cost and what exact model was it? I think I will buy something to test on the ADC on BK7231, because so far I have only tested "artificially" by connecting the potentiometer to the Tuya 4CH relay controller board

Dark Man wrote:

It is true that the module that I desoldered WBLC9 had pins / pads on both sides, so it would be more difficult, but it would probably work
(can be combined with a pen dust extractor or a copper braid)

This is even simpler than the gif process I showed - the flux + braid removes the entire binder without any problems

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#887 20155365 22 Aug 2022 21:46

Dark Man Dark Man

Level 13
» | Helpful post? (0)

Post #887
20155365 22 Aug 2022 21:46

p.kaczmarek2 wrote:
I do not know this RT5350F chip, but from what I can see there are even open hardware projects on it:
https://www.olimex.com/Products/OLinuXino/RT5350F/RT5350F-OLinuXino/open-source-hardware
https://www.olimex.com/Products/OLinuXino/RT5350F/RT5350F-OLinuXino-EVB/open-source-hardware
Some SDKs are also:
https://github.com/search?q=RT5350

You could probably make a port, but unfortunately, as long as only one socket with this system is known, I do not know if I will find time for it, because there are more popular systems and features to be added in the queue.

Okay, no need to play with the old socket, there are other newer ones :)

p.kaczmarek2 wrote:
And as for this floodlight with ADC, how much did it cost and what exact model was it? I think I will buy something to test on the ADC on BK7231, because so far I have only tested "artificially" by connecting the potentiometer to the Tuya 4CH relay controller board

This is exactly this:
https://www.action.com/pl-pl/p/reflektor-led-lsc-smart-connect/
Price PLN 45
Power 20W 1500lumens
I would like to remind you that all control with the Beken system is in a protruding housing with a PIR sensor :)

I found another socket in the scraps.
This time it
Ferguson FS2PG - 16A with current measurement on HLW8012
https://ferguson-digital.eu/produkt/inteligentne-garówka-wi-fi-fs2pg/
It was also waiting for better times, because there is an ARM system in it and a second Mediatheque
I will not combine with an unknown chip, but I am already preparing ESP12 for it, because I have already found the paths

Added after 8 [hours] 30 [minutes]:

Dark Man wrote:
I will share my latest struggles.
About 3 months ago I bought a light bulb at Action and immediately after that I tried to take it apart to find out what chip it is based on.
Opening it ended with breaking the casing a bit and tearing out the pads connecting the power supply with the PCB with LEDs.
Unfortunately, it turned out that there is no ESP but the WBLC9 module on the BK7231T chip and I left it for a better time.

Today, having some time, I returned to her.
I desoldered the module, downloaded three times the original firmware (not yet connected to Wifi) - attached (maybe it will be useful for cludcutter, because I did not find this bulb in the profiles)
I have uploaded your latest firmware and detected the following pin configuration:
R: P8 PWM 1
G: P9 PWM 2
B: P24 PWM 3
C: P26 PWM 4
W: P7 PWM 5
I soldered the module, connected the broken pads with cables and it works :)

https: // www.action.com / en-pl / p / intelligent-multicolor-led-lsc-smart-connect3-led-bulb
Intelligent multi-color LED bulb LSC Smart Connect
470 lumens
5W
E14
case model: 970721

I have a problem with the software of the bulb - it loses Wifi connectivity after trying to control the Home Assistant via MQTT.
This is exactly how:
Appears on the network after approximately 15 seconds after connecting to the power supply. It can still be controlled via the GUI in the browser. It connects to the MQTT broker and is visible in the Home Assistant.
With any command sent, e.g. turn off, change color or brightness, immediately the bulb disconnects from the Wifi network (it cannot be pinged) and does not come back anymore, unless I disconnect its power and turn it on again.
Firmware version: Build on Aug 19 2022 10:42:51 version 1.12.39
HA configuration:

Code: text Expand Select all Copy to clipboard
- name: "obk42E97C5D RGBCW" unique_id: "OpenBK7231T_42E97C5D_light_rgbcw" rgb_command_template: "{{ '#%02x%02x%02x0000' | format(red, green, blue)}}" rgb_state_topic: "cmnd/obk42E97C5D/led_basecolor_rgb" rgb_command_topic: "cmnd/obk42E97C5D/led_basecolor_rgb" command_topic: "cmnd/obk42E97C5D/led_enableAll" availability_topic: "obk42E97C5D/connected" state_topic: "obk42E97C5D/led_enableAll/get" payload_on: 1 payload_off: 0 brightness_command_topic: "cmnd/obk42E97C5D/led_dimmer" brightness_scale: 100 brightness_value_template: "{{ value_json.Dimmer }}" color_temp_command_topic: "cmnd/obk42E97C5D/led_temperature" color_temp_state_topic: "cmnd/obk42E97C5D/ctr" color_temp_value_template: "{{ value_json.CT }}"
#888 20156410 23 Aug 2022 01:00

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #888
20156410 23 Aug 2022 01:00

Today I fixed one problem on some devices in rare situations, but I don't know if this is the bug you are seeing.
Would you be able to give the whole log or somehow narrow down the situations, define what's breaking?

and if you enter the command via the console (e.g. this is led_enableall) or led_basecolor_rgb it is also a problem?

What flags do you have on?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

#889 20156418 23 Aug 2022 01:16

Dark Man Dark Man

Level 13

Post #889

20156418 23 Aug 2022 01:16

Commands sent in the GUI do not break connectivity
I checked: led_enableall and led_basecolor_rgb
the change from HA no longer generates the logo because there is a loss of connectivity immediately

Info:MAIN:Time 44, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MQTT:Publishing led_enableAll = 1 

Info:MQTT:[g_bPublishAllStatesNow] item -9 result 0

Info:MAIN:Time 45, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 46, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 47, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MQTT:Publishing led_basecolor_rgb = FFFFFF 

Info:MQTT:[g_bPublishAllStatesNow] item -8 result 0

Info:MAIN:Time 48, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 49, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 50, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MQTT:Publishing led_dimmer = 100 

Info:MQTT:[g_bPublishAllStatesNow] item -7 result 0

Info:MAIN:Time 51, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 52, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 53, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MQTT:Publishing sockets = 4 

Info:MQTT:[g_bPublishAllStatesNow] item -5 result 0

Info:MAIN:Time 54, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 55, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 56, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MQTT:Publishing rssi = -59 

Info:MQTT:[g_bPublishAllStatesNow] item -4 result 0

Info:MAIN:Time 57, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_enableall 0]
Info:CMD: enableAll (led_enableall) received with args 0
Info:GEN:No change in channel 1 (still set to 0) - ignoring


Info:GEN:No change in channel 2 (still set to 0) - ignoring


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:CHANNEL_Set channel 5 has changed to 0 (flags 2)


Info:MQTT:Publishing led_enableAll = 0 

Info:MAIN:Time 58, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 59, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MQTT:Publishing uptime = 59 

Info:MQTT:[g_bPublishAllStatesNow] item -3 result 0

Info:MAIN:Time 60, free 102520, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 61, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 0, socks 4/38

Info:MAIN:Time 62, free 89072, MQTT 1, bWifi 1, secondsWithNoPing 1, socks 5/38

Info:MQTT:Publishing freeheap = 102752 

Info:MQTT:[g_bPublishAllStatesNow] item -2 result 0

Info:MAIN:Time 63, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 2, socks 4/38

Info:MAIN:Time 64, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 3, socks 4/38

Info:MAIN:Time 65, free 102752, MQTT 1, bWifi 1, secondsWithNoPing 4, socks 4/38

Info:MQTT:Publishing ip = 192.168.10.113 

Info:MQTT:[g_bPublishAllStatesNow] item -1 result 0

Info:MAIN:Time 66, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 67, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 68, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Forced channel publish! Publishing val 1 with 0 

Info:MQTT:Publishing 1 = 0 

Info:MAIN:Forced channel publish! Publishing val 2 with 0 

Info:MQTT:Publishing 2 = 0 

Info:MAIN:Forced channel publish! Publishing val 3 with 0 

Info:MQTT:Publishing 3 = 0 

Info:MAIN:Forced channel publish! Publishing val 4 with 0 

Info:MQTT:Publishing 4 = 0 

Info:MAIN:Forced channel publish! Publishing val 5 with 0 

Info:MQTT:Publishing 5 = 0 

Info:MAIN:Time 69, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 70, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 71, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 72, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_enableall 1]
Info:CMD: enableAll (led_enableall) received with args 1
Info:GEN:CHANNEL_Set channel 1 has changed to 100 (flags 2)


Info:GEN:CHANNEL_Set channel 2 has changed to 100 (flags 2)


Info:GEN:CHANNEL_Set channel 3 has changed to 100 (flags 2)


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_enableAll = 1 

Info:MAIN:Time 73, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 74, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 75, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 76, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 77, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 78, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 79, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 80, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 81, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 82, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 83, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 84, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 85, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 86, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 87, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 88, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 89, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 90, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 91, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 92, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 93, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 94, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 95, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 96, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 97, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 98, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 99, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 100, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 101, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 102, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 103, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 104, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 105, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 106, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 107, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 108, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb]
Debug:CMD: BASECOLOR got 
Info:GEN:No change in channel 1 (still set to 100) - ignoring


Info:GEN:No change in channel 2 (still set to 100) - ignoring


Info:GEN:No change in channel 3 (still set to 100) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = FFFFFF 

Info:MAIN:Time 109, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 110, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 111, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 112, free 102544, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 113, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 114, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 115, free 89072, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 5/38

Info:MAIN:Time 116, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 117, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 118, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 119, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 120, free 89072, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 5/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 121, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 122, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 123, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 124, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 125, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 126, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 127, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 128, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 129, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 130, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 131, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 132, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 133, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 134, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 135, free 89072, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 5/38

Info:MAIN:Time 136, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 137, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 138, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 139, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 140, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 141, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 142, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 143, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 144, free 89072, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 5/38

Info:MAIN:Time 145, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 146, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 147, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 148, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 149, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 150, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 151, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 152, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 153, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 154, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 155, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 156, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 157, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 158, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 159, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 160, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 161, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 162, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 163, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 164, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 165, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 166, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 167, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 168, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 169, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 170, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 171, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 172, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 173, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 174, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 175, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 176, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 177, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 178, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb 255,0,0]
Debug:CMD: BASECOLOR got 255,0,0
Info:GEN:CHANNEL_Set channel 1 has changed to 14 (flags 2)


Info:GEN:CHANNEL_Set channel 2 has changed to 1 (flags 2)


Info:GEN:CHANNEL_Set channel 3 has changed to 0 (flags 2)


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = 250500 

Info:MAIN:Time 179, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 180, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:MAIN:Time 181, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 182, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 183, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 184, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 185, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 186, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 187, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 188, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 189, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:MAIN:Time 190, free 102752, MQTT 1, bWifi 1, secondsWithNoPing -1, socks 4/38

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [logfeature 6 0]
Debug:CMD:logfeature set 0x01FFFDBF
Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb 255,0,0]
Debug:CMD: BASECOLOR got 255,0,0
Info:GEN:No change in channel 1 (still set to 14) - ignoring


Info:GEN:No change in channel 2 (still set to 1) - ignoring


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = 250500 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:CMD: BASECOLOR got #ff0000
Info:GEN:CHANNEL_Set channel 1 has changed to 100 (flags 2)


Info:GEN:CHANNEL_Set channel 2 has changed to 0 (flags 2)


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = FF0000 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb FF0000]
Debug:CMD: BASECOLOR got FF0000
Info:GEN:No change in channel 1 (still set to 100) - ignoring


Info:GEN:No change in channel 2 (still set to 0) - ignoring


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = FF0000 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb 00FF00]
Debug:CMD: BASECOLOR got 00FF00
Info:GEN:CHANNEL_Set channel 1 has changed to 0 (flags 2)


Info:GEN:CHANNEL_Set channel 2 has changed to 100 (flags 2)


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = 00FF00 

Debug:CMD: BASECOLOR got #ff0000
Info:GEN:CHANNEL_Set channel 1 has changed to 100 (flags 2)


Info:GEN:CHANNEL_Set channel 2 has changed to 0 (flags 2)


Info:GEN:No change in channel 3 (still set to 0) - ignoring


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = FF0000 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [help]
Error:CMD:cmd help NOT found (args )
Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [cmd]
Error:CMD:cmd cmd NOT found (args )
Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Debug:API:POST to api/cmnd
Debug:CMD:cmd [led_basecolor_rgb FF00FF]
Debug:CMD: BASECOLOR got FF00FF
Info:GEN:No change in channel 1 (still set to 100) - ignoring


Info:GEN:No change in channel 2 (still set to 0) - ignoring


Info:GEN:CHANNEL_Set channel 3 has changed to 100 (flags 2)


Info:GEN:No change in channel 4 (still set to 0) - ignoring


Info:GEN:No change in channel 5 (still set to 0) - ignoring


Info:MQTT:Publishing led_basecolor_rgb = FF00FF 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d 

Info:GEN:dhcp=0 ip=192.168.10.113 gate=192.168.10.1 mask=255.255.254.0 mac=84:e3:42:e9:7c:5d

Added after 1 [minutes]:

I do not know what flags are meant: /
[movie: 756f1998b3] https://filmy.elektroda.pl/25_1661198151.mp4 [/ movie: 756f1998b3]

#890 20156650 23 Aug 2022 10:11

ferbulous ferbulous

Level 18

Helpful post? (0)

Post #890
20156650 23 Aug 2022 10:11

@p.kaczmarek2
Hi, I browsed a few posts back and apparently I might need to use togglechannel for my buttons
I tried that, but it's still not toggling the relays
Anything else I need to add in the custom command
#891 20156687 23 Aug 2022 10:42

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #891
20156687 23 Aug 2022 10:42

@ferbulous it should work in this configuration. Are you saying that the device is not able to discover the change in pin state?

Ok, so do two things.
1. Set those pins to DigitalInput (with pull up and without - test both cases) and see if the OpenBeken is able to read the state on those input pins (1 or 0, depending whether button is in ON or OFF state)
this obviously is not a final solution but it's a way to determine whether the wiring is correct
2. Check the PCB tracks to determine whether there are some extra components on those tracks, like pull down or pull up resistors

PS: I fixed a serious HTTP crash last night, but haven't yet time to test on all devices, so wait a day or so with updating to latest build

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#892 20157309 23 Aug 2022 17:45

ferbulous ferbulous

Level 18

Helpful post? (0)

Post #892
20157309 23 Aug 2022 17:45

p.kaczmarek2 wrote:
1. Set those pins to DigitalInput (with pull up and without - test both cases) and see if the OpenBeken is able to read the state on those input pins (1 or 0, depending whether button is in ON or OFF state)
this obviously is not a final solution but it's a way to determine whether the wiring is correct

Relay
L1 - P24
L2 - P17
L3 - P26
L4 - P6

Remaining pins:
P14 - reset button, set to button 1 triggers relay 1
P16
P7
P8
P9
P15
P28 - could be for buzzer? when I setup as button 4, it was toggling relay 4 on and off, like a wifi led that's blinking behavior I think?

Tried assigning remaining pibs P7, P8, P9 & 15 for digitalinput & digitalinput_nopull up
It does toggle the relays on when I assign digitalinput & relays off for digitalinput_n. Same goes for digitalinput_nopullup

Toggling the physical buttons doesn't trigger anything yet so far
--Update--
Pin 14 - Reset button on the wifi module, set to button 1 triggers relay 1

p.kaczmarek2 wrote:
. Check the PCB tracks to determine whether there are some extra components on those tracks, like pull down or pull up resistors

How can I check for that?
#893 20157540 23 Aug 2022 20:03

Dark Man Dark Man

Level 13

» | Helpful post? (0)

Post #893
20157540 23 Aug 2022 20:03

For something completely different.
An offer of cheap filament bulbs with Wifi appeared on Allegro.
https://allegro.pl/oferta/zarowka-led-nityam-e27-g95-700lm-300k-wifi-6w-12141516228?
I ordered 5 pcs. If ESP would be great, and like Beken, I would count on a detailed tutorial about the cloudcutter, which you wrote about in your last column
#894 20157716 23 Aug 2022 21:31

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #894
20157716 23 Aug 2022 21:31

Thanks for the link, I will consider whether to buy it. Or maybe you would like when they come to take a few photos from the outside and from the inside and send them to the "Device Interiors" section? If you rip the batch (but the whole 2mb, not 700kb), you could try to do cloudcutter, as long as haxomatic works (if there is bk)

As for the hang problem ... since you didn't mess up the flags, it's a difficult matter. You don't have how to download logs directly from UART, do you?
And how do you turn off the PWM pins and set the Relay to a pin for the test and then try to treat it as a HA relay, it also hangs as with HA you change the state of the channel / relay?
Or maybe try the latest build or an older version to determine when the problem occurred?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#895 20157914 23 Aug 2022 23:50

Dark Man Dark Man

Level 13
» | Helpful post? (0)

Post #895
20157914 23 Aug 2022 23:50

I'm making progress. Here's what I was able to deduce from HA, MQTT, ICMP and GUI debugging:
- I do not have access to UART
- the new build didn't change anything for me
- I did not turn off PWM in OpenBK, because I started to play with the configuration in YAML in HA
- I think that the generated YAML code (in GUI) for PWM channels should look different (after many tests on one channel):

Code: text Expand Select all Copy to clipboard
- unique_id: "OpenBK7231T_42E97C5D_light_1" name: "obk42E97C5D 1" state_topic: "obk42E97C5D/1/get" command_topic: "obk42E97C5D/1/set" brightness_command_topic: "obk42E97C5D/1/set" brightness_state_topic: "obk42E97C5D/1/get" on_command_type: "first" brightness_scale: 100 qos: 1 payload_on: 100 payload_off: 0 retain: true optimistic: false availability: - topic: "obk42E97C5D/connected"

(of course replacing the abbreviated name and channel number)
Thanks to the above code, we have the real status of the PWM channel, we can control the on / off, we know the real state of on / off (come on, and here it would be better to fix OpenBK to add the PWM channel status as 1 if it is set from 1 to 100 and the status 0 if PWM is 0
eg: obk42E97C5D / 1 / state 1 | 0

- while I found a possible reason for breaking the connection: OpenBK is not able to process the led_enableAll command sent by MQTT in the subject
cmnd / obk42E97C5D / led_enableAll
after sending a test in "MQTT Explorer" with a value of 1 or 0, the bulb breaks the connection.

If you can fix it, I will test it further and make YAML code for the generator.
#896 20159640 25 Aug 2022 03:06

xabean xabean

Level 6

Helpful post? (0)

Post #896
20159640 25 Aug 2022 03:06

Hey! I'm back. And I come with a gift:

I managed to track down more releases of the bk7231t platform repository code drops from tuya, and recreated the history.

https://github.com/warewolf/platform_bk7231t

This has MUCH older (and I think, two newer) releases of the platform zip mentioned in https://github.com/openshwprojects/OpenBK7231T/blob/master/build_app.sh -- we're working off bk7231t_1.0.22-beta.1.zip, but a 1.0.22 and 1.0.23 exist.

Now you can read through the history of older releases I tracked down https://github.com/warewolf/platform_bk7231t/wiki/Releases
#897 20159904 25 Aug 2022 10:10

staszek_org staszek_org

Level 2

» | Helpful post? (0)

Post #897
20159904 25 Aug 2022 10:10

p.kaczmarek2 wrote:
@staszek_org what exactly functionalities do you need from this? OpenBeken "bulbs" do not operate on NeoPixel (WS2812B, WS2811, SK6812).

EDIT: is it about animation? This project probably also supports other systems than Neopixel, so maybe that's it ..

The project also supports PWM control of RGB and RGBW LEDs.
And it can be used for various purposes, but it works best wherever speed of response is required, i.e. synchronization of light with music or a picture. For example, it supports the DDP protocol.
So you can make a light that reacts with the music in real time and gives cool effects (LEDFX project), use it to create holiday animations on the building (xLights)
or combine with Ambilight lighting made at https://github.com/hyperion-project/hyperion.ng

It also works very well in combination with HomeAssistant and other SmartHome projects.
And for controlling lighting (LED bulbs) it works much better than Tasmota.

And since now most of the bulbs are built on Baken microcontrollers and thanks to your design you can win the software wirelessly, it would be great if WLED also works on them.

I am happy to send a few light bulbs as a gift for testing, just write what and where (maybe Kanlux?).
#898 20161326 26 Aug 2022 08:52

Dark Man Dark Man

Level 13

» | Helpful post? (0)

Post #898
20161326 26 Aug 2022 08:52

p.kaczmarek2 wrote:
@ darkman1 could use a UART log, so do older versions have this problem?

In the sense of pin TX2 or TX1?
Please check first on your test device (this is the mqtt command), to which you have soldered the wires, because I would prefer not to desolder the entire bulb again :(

Which old version do you suggest to upload?
#899 20161474 26 Aug 2022 10:33

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #899
20161474 26 Aug 2022 10:33

Okay then wait with that soldering / opening.

The first version that supports what you need. Do you use the UI on the layout website or only with HA?

It works for me:

One user already reported to me that he had problems with the new CB2S but it was about http, it turned out to wipe the calibration partition and by the way it also fixed mac and other things ... I will look for a better fix for it in the SDK used. Tuya changed something in newer systems and hence the problem (when I uploaded OpenBeken on CB2S a few months ago it worked without problems).
But you have the BK7231T I think.

EDIT: What do you have here?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Reply Cool? Ranking DIY | New topic

Notify about new articles

Report a violation of the law

Topic summary

The discussion revolves around the development and implementation of custom firmware for devices using the BK7231T and BK7231N chips, particularly focusing on creating a mini HTTP server, MQTT support, and integration with Home Assistant. Users share their experiences flashing various smart devices, troubleshooting issues related to UART connections, and configuring GPIO pins for different functionalities. The conversation also touches on the challenges of maintaining WiFi connectivity, the importance of proper pin configuration, and the potential for using I2C for additional device control. Several users report successful firmware updates and the addition of new features, including support for various sensors and devices.
Summary generated by the language model.