![]() ![]() However, you must use the peacock thread and use the information in the Hardware-specific page to accurately identify your hardware and not create a problem that renders your router useless.Īfter you have read THIS page, and gotten some background on the peacock page, the Hardware-specific page may be the most useful page for you in terms of identifying your router, figuring out what files you need to download (including instructions), and figuring out the correct installation procedures. The user-friendly dd-wrt download page will help you identify the correct "killer" and dd-wrt firmware versions (as applicable) for your device as needed. (Read the English Broadcom Forum Announcements referenced above to find out why). Unfortunately, skipping this step leads many to brick (break) their routers. You will then want to follow what is written for your particular device.įor a list of recommended devices for installing DD-WRT, please see Which router should I buy? Before You Download, Upgrade, or Flashīefore you try to take any actions, including loading any firmware to your router.read the English Broadcom Forum Announcement entitled Peacock Thread It contains more information than just for those who are having problems. However, to avoid Bricking your router, please finish reading this entire page first. If your device is supported, you may find specific information in the Hardware-specific page for your router. If your router is not listed there, check the following wiki pages:įor a list of devices working with DD-WRT, please see Supported Devices.įor a list of devices not working with DD-WRT please see Known incompatible devices. Choosing the Correct Firmware - Extremely Important Is Your Router Supported? 3.4.1 Upgrading to a Newer Version of DD-WRT.3.3 Method 3: Flashing with Command Line.3 Flashing Your Router with DD-WRT Firmware.2.4 Going Offline/Before Implementation.1.3 Before You Download, Upgrade, or Flash.1 Choosing the Correct Firmware - Extremely Important.I could just use a Switch item instead, and that will be my immediate workaround, but it would be nicer if I could use a Contact item since that’s what they’re for. Does not accept commands, only status updates.” The OH documentation does describe the Contact item as “Status of contacts, e.g. The HA documentation lists “oh_post_update” and “oh_send_command” under ContactItem, but they don’t actually work. ![]() Now, I have created a Contact item in openHAB, and I want to set the state of this Contact so that other rules can act on it in a standardized way. the HABApp rule gets the message and knows the state of the door. In this case it’s through 433 mhz and MQTT, but that’s not important. I have my own wireless door sensor, and when the door is opened or closed, my HABApp rule is notified. This is probably as much an openhab question as a habapp question. Pastebin is a website where you can store text online for a set period of time. is the number one paste tool since 2002. What happens under hood if you do that? Are you passing a reference, a pointer, or a copy of the entire object? I’m asking as a C++ programmer, where nothing happens automatically as you know, so when you make a mistake, it’s always your own fault.īy the way here is the script as it’s running: Pastebin import HABAppfrom import ValueUpdateEvent, ValueChangeEvent. With regards to passing the rule as an argument, I have a follow-up question: 28 rules in a for-loop with delays would need some kind of solution like this as well. I was never able to solve this in my Node-RED prototype of this but I solved it in my HABApp script by making sure the latest command wins. n_at(0.1, self.handle_run_at, looptest_object)Īgain, this works but I would love some pointers Here it is Ģ8 rules in a for-loop could work too, but there’s one caveat: as the wipes for different dimmer levels go in different direction, if you’re too fast with a new command, one wipe will start before the previous one finished, creating a conflict where they’ll be fighting over some lamps. (n_test) #this works tooĭef handle_run_at(self, looptest_object): Log = logging.getLogger('HABApp.RunTest') I have created an example that shows the problem clearly. Unfortunately, I have found that creating an object that starts a sequence, does not work from a callback! The object gets created but run.at never executes. Obviously looping with sleep doesn’t work in an event-based system, so I’m using to get called periodically. I’m relying on being able to create an object which performs the transition upon command. So, I’m writing a script that is going to make cool light transitions. I will try to organize the code differently to avoid the issue. Edit: After sleeping on it, I realized that this is probably the special “running rules from another rule” case. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |