How to use Keywords for SEO and Web Sustainability
5 stars based on
Das Ergebnis ist in den folgenden Bildern zu sehen ein Video gibt es unten:. Heute geht es erst mal um die grundlegende Idee und die Funktionen.
Inspiriert hat mich ein Geschenk, das wir zu unserer eigenen Hochzeit bekommen haben. Die Gitarre kann ich nutzen, ggf. Die beiden Figuren auch. Aber dann kamen erst die Probleme: Und auf Playmobil gekommen. Da hab ich doch auch schon mal Gitarren gesehen. Da sind aber schon einige coole Sachen dabei. Also erstmal nach Sets gegoogelt, die Musikteile beinhalten. Dann die Einzelteile herausgesucht dabei helfen http: Alles weitere dazu kommt in einem seperaten Teil.
Dann aber schnell gemerkt, dass das nichts werden kann. Licht ist sowieso kein Problem. Von oben nach unten: Ich habe einige Teile bereits vorgeschrieben, allerdings geht es da eher um den eher trockenen Software-Part. On the site http: Every single piece is taken apart and detailed pictures were taken describing all the identifiable parts. With my little bit french from school even I can read through it.
But maybe Google Translator may help others. I decided to order two pieces because they were very cheap at Gearbest at that time and they would make a perfect match to the nightpanel lights I am currently building and replace the currently used Amazon Dash button. On faire-ca-soi-meme there are several detailed images of the button and also the pinout from the test pins.
Unfortunately these are pogo pins and my tries to solder a wire to them were not very successful. I was successful though with using jumper wires to connect 3.
Just shortly connect a ground wire to it when connecting the power even with my shaky hand that works. I used the compile flag for the JN and it compiled successfully. There is an error when flashing the firmware with the flash utility from BeyondStudio but this is only the validation after flashing.
The reason is that the chip was read-protected from Xiaomi in order to make reengineering their firmware impossible or not-so-easy. So the flashing was successful which can be seen from the serial monitor after rebooting:. This ouput is repeated from the timer resetting the device. There seems to be something wrong. The last output message can be found and after that the drivers eTouchInit method is called. I added some debug output and commented out the first for loop is this a delay or what is that for?
This results in the following output the BWE was added because I wanted to be sure I have the correct call:. So there seems to be something wrong with the for-loop. Maybe it tries to read from a wrong pin because it was made for the JN I will have to take a closer look at the driver and see what I can do.
I think I have to understand how it is working first it is build for a remote control with several buttons so I guess a more simple solution has to be found. I also have to see which DIO pin the buttons are connected to…. In parallel there are also some comments from lucac81 on peeveeone. I also remember a comment asking about using the chip as a switch for HUE.
So maybe someone else is also making progress on this end. I build a new one from the demo application with all debugs enabled and the keys in place as I did with the JN but I am getting the same output I had when not correctly putting the keys in place the first time with the JN see my post http: Which definitely hints to a key problem.
JN discussion on https: In this post I will describe how to connect the two devices and what to do to make the Arduino understand commands from the JN As the Arduino is using 5V level on the serial connection and the JN is using 3. This little device connects the two serial interfaces shifting from 5V to 3. To have a more stable connection to the Arduino I reduced the baud rate fromwhich is the default rate, to which the Arduino can handle better.
Once I am able to create more endpoints I may create another output. I will describe both solutions anyway:. In the vIdEffectTick there is an endpoint reference available so I added this similar to the function call above. This is why I currently go with the second option:.
Together with the first option this will result in the following output as I said it produces a smooth transition:. You can also see that the RGB values changed. This is according to the level value. The level is not really necessary in the output because the RGB values are already adjusted. I kept them anyway. For the Arduino part I first setup the serial connection I connected it to Serial2 and read the input. Then it parses the input line using the function strtok. The serial input is lagging sometimes though I think this is only the case when using the serial output to the other serial port so garbage is getting read as a line.
In case of not set values I checked whether the value is correctly set. Otherwise the old value is used. This may lead to wrong values but better than nothing. This may not be the best way of communication SPI may be better but it is the easiest to setup. To command 4 separate endpoints I may have to use option 1 and go without transitions or implement them myself on the arduino.
The bottle neck seems to be the serial connection as the arduino seems to be too slow to process the serial input fast enough. This is another argument for option 1 as it sends fewer lines. Although it is sending more than one line for a simple light change, too. Maybe the app itself also sends several commands to have a nice transition. I may check this later on. In any case I recommend disabling all other debug outputs to make better use of the serial communication and loose fewer lines.
Currently I am also building a board to connect everything together. It will not be very professional as I will be using many jumper wires instead of connecting everything directly but I want to be flexible but should work for me. It will be hidden away anyway.
The board connected to the Arduino and the serial connection to the JN can be seen in the upper left with one temporarily connected RGB strip. In the final version they will be connected with screw terminals. The LLC will also go from the breadboard to the custom board. There will be 4 RGB connections in the final version to be connected with screw terminals, the LLC and a connection for an external power source.
This is all still work in progress so I will publih the final schematics when I am ready and know that everything is working as expected. Today I will describe my progress on the development of my own Hue connected lights. Because other people developing with the JN are not necessarily german speakers I will continue my project which I call HUEify in english.
There is some discussion going on at the latest post from PeeVeeOne. As I had some trouble with the build provided by PeeVeeOne lights not turning off, dimming and red not working properly I had to go through the proecss of building my own binary. This was planned anyways because I have some other plans on top. This post is all about my troubles getting the demo app and a custom build project to work.
So far it is all his work that I am just setting to work on my device. The general setup of the developing environment BeyondStudio and the demo application is described in this post by PeeVeeOne. Both were not joining the Hue bridge and were not giving any debug information, though the binary directly downloaded from PeeVeeOne was doing both without any issues.
But that is not enough as the builder is getting the command additionally mind the configuration in the dropdown at the top of the window In the project properties you have to change the Build command:. To trace the startup and the connection you can leave the USB serial converter FT wired to the chip after flashing the binary.
It will send debug information which you can read at your PC. I use the serial monitor from the Arduino IDE you have to close the monitor before flashing the binary because it will lock the serial connection and you get an access error.
In the default of the demo application and the PeeVeeOne github rep the debugs are not enabled. This is the debug output when starting the device with no search for new devices from the Hue bridge. It goes through all channels serching for something to connect to. So it seems like 6ad40ce is the ID of my bridge. When not searching for devices it recognizes it but is not trying to join. When searching for devices it is trying but it is not successful.