Announcement

Collapse
No announcement yet.

Under kitchen cabinet LED lamps with mcsMQTT control

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Michael McSharry
    replied
    I bought three or four to play with when the link was posted some weeks back. I have installed two with Espurna in cases with encoders and IR, but do not have any specific application for them at this time.

    What I did buy was a 10 ft strip with a hand-wave on/off switch that was on a Amazon Lightning deal. I was surprised that the technology that appears to be used for the switch was an IR emitter and receiver and the beam is deflected back when the hand is placed in front of it. I place this strip under the kitchen sink cabinet with the switch mounted on the vertical post between the two cabinet doors. It actually works quite well. What I actually would have preferred is a switch that was controlled when either cabinet doors was opened and then light off when either door closed. I know I could use a Sonoff Basic with two door/window sensors mounted on the doors, but the off the shelf solutions is still neat.

    Another project I did with the LED strip is with the NeoPixels where I implemented the Adafruit sketch for Fake TV in a Uno that I bought several years ago and never used. Rather than integrating software I found it easier to piggy back a Sonoff Basic in the case I printed to control the power to the Uno and Tasmota's timers to schedule when the Fake TV turns on and off. Often easier to hack hardware than hack software.

    Leave a comment:


  • Pete
    replied
    Went to purchase more MagicHome Controllers (same ones as above) and they all went up on Amazon...and one's that I got are gone...

    New endeavor here now...making more LED strips in aluminum holders with diffusers....and

    adding two more SonOff basic WiFi Espurna devices doing temperature and humidity on the second floor replacing current 1-wire Node Red OWFS set up.

    Very simple this time with 3 terminals on outside of case.

    Leave a comment:


  • Pete
    replied
    Tinkering this morning ssh'd over to the Mosquitto broker (RPi2) and noticed that I could ping every device just fine.

    Then started looking at the arp cache and added the devices to the arp table.

    I also found a script to do this with Tasmota devices as it is an issue with Tasmota and Espurna firmware devices.

    Then moved the broker over to the HS3 box running Ubuntu.

    Never rebooted any of the Sonoff or Magic home devices.

    I can now ping them from any device on the network and Jon00's monitor program lets me go to the interfaces web page. Now will wait a few hours and see if they work later.

    Works now. I can always get to the web page and Jon00's application works using ARP.

    Click image for larger version

Name:	aarp.jpg
Views:	207
Size:	78.5 KB
ID:	1271931

    xxxx

    Leave a comment:


  • Pete
    replied

    The two types of decoders are 20 detents and 360 degree turning. Didn't John have it set for two on off clicks to reset the counts on the decoder?

    I saw your stuff on the Espurna bug report relating to the interupts.

    Yes for testing here tried both BLLAN and Jon00's script while concurrently just pinged the network interface.

    BLLAN sees then always up even when I do not get ping responses. Jon00's script sees the interfaces down even when I get a ping response.

    I know I can tweak Jon00's settings for ping and will give it a try. I am running the script inside of a W2003 Virtual box with the connection bridged out on the Homeseer 3 Linux box and it does see rest of my devices on the main LAN.

    Added FastPing=0 under the Jon00 ini file settings section.

    Will download and update the two MagicHome controllers with the rotary encoders on them.

    Updated one with IR firmware and the other with DHT firmware.

    Works fine. 100% on one turn is higher on the WAF.

    Thank you Michael.

    I have not touched the mcsTasmota GDO SonOff WiFi basic device and it shows up on pings just fine.
    I did change the oui.txt file here. (mac address naming thing).

    #5 is the H801 RGB device with Espurna H801 firmware on it and no encoder.
    #2, #3 and #4 are SonOff Wifi Basic devices.

    Click image for larger version  Name:	jon00.jpg Views:	1 Size:	60.3 KB ID:	1271520
    xxx

    Leave a comment:


  • Michael McSharry
    replied
    I wonder what Jon00 is doing for monitoring. My understanding is that Mosquito uses ICMP and will report LWT which is normally Offline.

    I have increased the step size from 1 to 4 for my encoder firmware that bypasses the web server update as the knob is moved. I updated the zip at http://mcsSprinklers.com/mcsEspurnaMagicHome.zip to include the IR & DHT variants of the images.

    Leave a comment:


  • Pete
    replied
    Yeah here wife likes the digital on / off and dimmer pot and uses it all of the time. She has complained a bit about the slow rotation but never spins it.

    I have only one RGB controller (H801A) here in test mode connected to RGB, W and WW LED lamps using stock Espurna RGB firmware.

    No pot and RGB plus 2 channels works great.

    2 Magichome controllers are the only ones with the digital pots for use with brightness for one LED channel (SMD5050).

    2 SonOff WiFi basics only used for temperature stuff.

    The mcsMQTT with digital pot to Homeseer interface works great.

    Only utilize the browser interface here for configuration stuff. Originally only used the debug output for the on and off and dimming pieces to see them working.

    I did put in the IP and MAC addresses here for Jon00's monitoring utility and they do not show as online most of the time.

    Leave a comment:


  • Michael McSharry
    replied
    I have been running magichome LED strip with Espurna for about 2 days with browser window URL to the device Debug page. It continues to update and I continue to have control of brightness with the mcsEspurna version. I supported an investigation on github for encoder interrupt protection but it did not help the reset problem caused by spinning the decoder knob. It really does not matter to me if the Espurna Status page is updated as the encoder knob is changed since I normally will not be using the direct browser interface to the device.

    Leave a comment:


  • Pete
    replied
    Been tinkering with the 4 Espurna firmware devices. Initially did this to all four of them:

    Click image for larger version

Name:	eespurna.jpg
Views:	201
Size:	52.7 KB
ID:	1270928

    BLLAN shows them all responding to Pings which they are not. I can only ping one or two of them at any given time.

    Jon00 monitor shows one active only.
    MQTT works on all of these as I can send command and getting status just fine.

    I do see many bug reports about loss of web gui on many Espurna firmware upgraded devices. All the same. Working for a day or so then dropping off then coming back.

    Only thing that is hit or misst is the browser GUI. I can only get to one of the 4 browsers. If I keep trying then they all eventually come up. I have not rebooted any of them since last writing here.

    The mcsTasmota GDO WiFi Sonoff basic device continues to work fine in the garage with no issues.

    xxx

    Leave a comment:


  • Pete
    replied
    Redid the BLLAN stuff labels. Just noticed after goofing around here and not rebooting the Espurna DHT22, 1-Wire and H801A web interfaces came up but not the two MagicHome Espurna firmware devices.

    Click image for larger version

Name:	BLLAN.jpg
Views:	188
Size:	111.9 KB
ID:	1270439



    xxxx

    Leave a comment:


  • Pete
    replied
    When I was testing yesterday to provide debug "crash" and "info" data I had a case where I totally lost the firmware and was not able to connect with browser. Had to resolder the wires for manual flashing. Just reflashing did not help. I had to flash with Tasmota and then flash again with Espurna to bring it back. Apparently something was retained in non-volatile memory that killed Espurna.

    Saw your posts on the Espurna bug stuff forum posts.

    Did the crash and burn happen after an OTA update of modified Espurna Firmware?

    Are you doing the two step upgrade of firmware? (cuz it is over 500 k now)

    Here will modify another MagicHome controller with Espurna firmware but no digital pot / DHT22 and leave it such that I can update the firmware via the serial port.

    I only wired up two of the MagicHome Controllers to date. It is a PITA to wire up and once done will put connectors at the end of the wires for easy firmware update.

    Thinking John mentioned using the connector for the RX/TX Ground connection and GPIO 0 / ground just for the purpose of updating the firmware via a serial link.

    You indicated that you are using Espurna for several microcontrollers. Is it only the magichome configuration that is dropping off?

    Currently have implemented:

    1 - SonOff Basic WiFi #1 with mcsTasmota for GDO stuff - working fine. Sometimes I cannot get to the web interface and keep trying until I get to it. MQTT status and button working fine.

    2 - SonOff Basic WiFi #2 with Espurna and one DHT22. MQTT status is fine on Homeseer 3. Just tried the web interface and cannot get to it.

    3 - SonOff basic WiFi #3 with Espurna and multiple DS18B20's. MQTT status is fine on Homeseer 3 / mcsMQTT. Just tried the web interface and cannot get to it.

    4 - H801 RGB controller with Espurna and 5 channels of LED lamps. Relating to web interface same as above. MQTT is fine.

    5 - Magic Home Controller #1 with mcsEspurna and one LED channel and digital on off pot. Same as #2,3,4, Note already had issues with base Espurna MagicHome RGB firmware.

    6 - Magic Home Controller #2 with mcsEspurna and one LED channel and digital on off pot. Same as #2,3,4, Note already had issues with base Espurna MagicHome RGB firmware.

    Note here too have now added 3 custom OpenWRT AP's just for all of this stuff. I do see the MAC addresses of all of the above just fine with descent RSSI.

    I am using BLLAN and John's network monitoring.

    Via BLLAN see all except for one updated device.

    Click image for larger version

Name:	BLLAN.jpg
Views:	278
Size:	120.6 KB
ID:	1270429

    xxxx

    Not seeing any of the above with Jon00 application. I haven't really configured it all yet though.

    I have configured all of the Espurna boxes with the 3 WAPs and scanning.

    Leave a comment:


  • Michael McSharry
    replied
    When I was testing yesterday to provide debug "crash" and "info" data I had a case where I totally lost the firmware and was not able to connect with browser. Had to resolder the wires for manual flashing. Just reflashing did not help. I had to flash with Tasmota and then flash again with Espurna to bring it back. Apparently something was retained in non-volatile memory that killed Espurna.

    You indicated that you are using Espurna for several microcontrollers. Is it only the magichome configuration that is dropping off?

    Leave a comment:


  • Pete
    replied
    Lost network connectivity to the two MagicHome Custom Espurna firmware.

    It was though losing it with the original Espurna Magic Home RGB firmware.

    Current solution is to power it off and on again. Ping only worked a couple of times.

    Same issue here with the H801 Espurna firmware RGB controller. This controller is connected to an RGB strip, White LED strip and WW led strip (5 channels of LEDs). Not really in to RGB here but using this controller to test it. I have not modified this controller.

    It is still working and running built in schedule but I cannot get to the interface.

    Digital pot and on and off switch working fine. Also tried continuous pings and was not successful bringing up the interface.

    Michael McSharry I see you are posting on the Espurna bug list about this issue and fast rotating of digital pot.

    If you update another MagicHome RGB controller with the Espurna Magic Home base firmware with no physical updates to it; it will also drop off the network after some time.

    Leave a comment:


  • Pete
    replied
    Started a DIY pictorial just for the endeavor of using the Magic Home Controller.

    Baby steps here as I want to label the IR remote wires and LED channel wires to update this picture.

    For wiring best to tin ends of wire and use a flux pen on board and small soldering iron tip. Here used alligator hands and painters tape to hold the wires in place while soldering. Still not as neat as I wanted it to look.

    Note that the rotary encoder switch only controls brightness and not individual color channels. Here for my endeavor only using one channel to control the kitchen under counter white SMD5050 LEDs.

    Click image for larger version

Name:	magichome1.jpg
Views:	219
Size:	101.4 KB
ID:	1269805

    xxxx

    Leave a comment:


  • Pete
    replied
    Found out if I ping them I can bring them back without powering off the devices.

    Leave a comment:


  • Pete
    replied
    Only thing so far that I have noticed is that the Espurna Magic Home controller drops off of the network after a few hours and I have to power it off and on to get back to the network.

    I can bring the web interface back by pinging the device.

    ping 192.168.244.224
    PING 192.168.244.224 (192.168.244.224) 56(84) bytes of data.
    64 bytes from 192.168.244.224: icmp_seq=1 ttl=128 time=4.69 ms
    64 bytes from 192.168.244.224: icmp_seq=2 ttl=128 time=3.49 ms
    64 bytes from 192.168.244.224: icmp_seq=3 ttl=128 time=5.18 ms
    64 bytes from 192.168.244.224: icmp_seq=4 ttl=128 time=16.0 ms

    Once in typed crash to debug. (RSSI -70)

    [112167] [WEBSOCKET] Requested action: dbgcmd
    [112171] [DEBUG] Latest crash was at 49017140 ms after boot
    [112172] [DEBUG] Reason of restart: 2
    [112175] [DEBUG] Exception cause: 3
    [112177] [DEBUG] epc1=0x4010011d epc2=0x00000000 epc3=0x40000f68
    [112180] [DEBUG] excvaddr=0x40037068 depc=0x00000000
    [112184] [DEBUG] sp=0x3fff1fd0 end=0x3fff2130
    [112188] [DEBUG] >>>stack>>>
    [DEBUG] 3fff1fd0: 00000000 3fff2060 402379a1 3ffef470
    [DEBUG] 3fff1fe0: 3fff2228 000008bf 000008bf 4010020c
    [DEBUG] 3fff1ff0: 3fff0d4c 00000000 3fff2b04 4010068c
    [DEBUG] 3fff2000: 3fff2040 00000000 3fff0d4c 40107608
    [DEBUG] 3fff2010: 402370ba 3fff2b04 3fff2b04 4023961f
    [DEBUG] 3fff2020: 00000008
    [DEBUG] 00000000 00000000 3fff2070: 3fff0680 3fffdad0
    [DEBUG] 00000000
    [DEBUG]
    [DEBUG] 3fff20c0: 40227a44
    [DEBUG] 4022d348
    [DEBUG]

    Noticed the same with the H801 RGB controller. (RSSI ==> -61)

    047893] [WEBSOCKET] #1 connected, ip: 192.168.244.233, url: /ws
    [060006] [MAIN] System OK
    [065210] [WEBSOCKET] Requested action: dbgcmd
    [065218] [DEBUG] Latest crash was at 848492 ms after boot
    [065220] [DEBUG] Reason of restart: 2
    [065223] [DEBUG] Exception cause: 3
    [065226] [DEBUG] epc1=0x4010011d epc2=0x00000000 epc3=0x40000f68
    [065229] [DEBUG] excvaddr=0x40037da8 depc=0x00000000
    [065233] [DEBUG] >>>stack>>>
    [DEBUG] 3fff2070: 00000000 3fff2100 40234c21 3ffef4f0
    [DEBUG] 3fff2080: 3fff22c8 00000a53 00000a53 4010020c
    [DEBUG] 3fff2090: 3fff0e2c 00000000 3fff2ba4 4010068c
    [DEBUG] 3fff20a0: 3fff20e0 00000000 3fff0e2c 40107440
    [DEBUG] 3fff20b0: 4023433a 3fff2ba4 3fff2ba4 402368a7
    [DEBUG] 3fff20c0: 4023516e 3fff2ba4 3fff2ba4 3fff57a8
    [DEBUG] 3fff20d0: 40216bc1 3fff0f0c 00000001 fffffffe
    [DEBUG] 3fff20e0: ffffff00 3fffc6fc 00000000 0000000a
    [DEBUG] 3fff20f0: 3fff0c70 3fffdad0 3fff11a8 00000030
    [DEBUG] 3fff2100: 00000000 00000000 3fff11b0 00000000
    [DEBUG] 3fff2110: 3fff0bf4 3fff2160 4022a5b8 3fff11b0
    [DEBUG] 3fff2120: 4023433a 00000008 00000064 4022a630
    [DEBUG] 3fff2130: 40104832 0fcd3838 00000001 4022a670
    [DEBUG] 3fff2140: 401048ee 3ffef258 0fcd3838 00000000
    [DEBUG] 3fff2150: 40104ac0 00000000 3fff0f0c 40224961
    [DEBUG] 3fff2160: 3ffef270 3fff2220 3fff11b0 3fff11a8
    [DEBUG] 3fff2170: 3fffdad0 3fff0c70 3fff0f0c 40224d5d
    [DEBUG] 3fff2180: 402020ce 0000000a 00000003 40224e40
    [DEBUG] 3fff2190: 3fffdad0 3fff08f8 3fff0845 40210822
    [DEBUG] 3fff21a0: 00000000 3fff0c70 00000003 40204670
    [DEBUG] 3fff21b0: 3fffdad0 00000000 3fff11a2 4022a604
    [DEBUG] 3fff21c0: feefeffe feefeffe 3fff11b0 401006fc
    [DEBUG] <<<stack<<<
    [065646] +OK

    Leave a comment:

Working...
X