|
Post by papa on Jul 9, 2018 20:18:58 GMT
anthonys: "fatal error: SPIFlash.h: No such file or directory #include <SPIFlash.h> ^ papa: That means what even the non-verbose says: The SPIFlash.h file does not exist on your computer where the IDE can find it. If you search the node sketch for SPIFlash.h, you see I provided a link to download the file: However, looks like the SPIflash library is now at: You can only get such a compiling error if you UNcomment (delete the starting // ) from the sketch line:// #define MOTEMEM // to use Moteino SPI Flash memory, incl wireless programming You don't need to uncomment that line ^^ unless you are using a Moteino.
A Moteino from lowpowerlab.com is a small 3.3 volt Arduino compatible with pre-installed RFM69 radio & extra memory. An Anarduino Miniwireless is similar, but using its memory requires .h library file different from that for a Moteino.
I hope you don't need the Moteino Wireless Programming libraries because it looks like lowpowerlab.com may have changed their approach to this since I provided that option in the sketch (& I never had a Moteino to try it). Link for Moteino Wireless Programming: github.com/LowPowerLab/WirelessProgramming
|
|
|
Post by papa on Jul 2, 2018 17:33:12 GMT
"Once again thanks for your help and I will keep you posted. Regards Anthony in San Diego, CA"
"the switchable one, which is coming from china"
^^ papa: I hope it's something like a Buono Uno which supplies more 3.3 volt current than some boards. The RFM69 radio, especially the "H" high power ones need a lot of current.
You are welcome, anthonys, good to hear from you.
|
|
|
Post by papa on Jul 2, 2018 14:09:51 GMT
Welcome, anthonys, we all start somewhere. I've never used a logic level converter. I've started this new thread that might draw more attention from others & I'll do my best to respond.
You are wise to protect your RFM69 radio from the Uno's 5 volts that would damage the radio. One must do more than connect the Uno's 3.3 volt pin to the RFM69's Vcc (power in). One must also protect the RFM69 from the 5 volts the Uno sends thru the digital pins like D2,D10-D13. For this I use a Buono Uno that can be switched to send only 3.3 volts thru those pins. Some people use logic level converters with a Uno.
For a Uno, I believe this Adafruit product might be a better option. In one package it supplies the RFM69 radio & the translation between 3.3 volts & 5 volts for ALL the RFM69 pins needed. The logic level converter board you referenced can only handle 4 pins so I believe you will need TWO LLC boards for each RFM69 radio.
As to using the LLC, I base my suggestions on this Sparkfun schematic. As I see it ... connect the schematic's "high side" GND pin to the Uno's GND. Connect the schematics "low side" GND to the RFM69 GND. Connect Uno 3.3 volt pin directly to RFM69's VCC pin. For a digital pin connection needed between the Arduino & RFM69 (see forum schematics), connect the Arduino pin to one of the HV pins AND at the LOW side LV pin of the same channel connect the RFM69 pin indicated by a forum schematic.
For example ... in our forum's node schematics, RFM69 pin DI00 connects to Arduino D2. So you might connect the Uno D2 pin to the LLC's HV1 pin AND then connect LLC's LV1 to RFM69's DIO0 pin. The LLC's Channel 1 would then connect Arduino D2 to RFM69 DIO0 & as needed, translate the voltages between the Uno & the RFM69. Do this with all Uno digital pins (like D2, D8, D10-D13) that a forum schematic connects to an RFM69. Each LLC channel should provide a safe voltage translation bridge between an Uno & an RFM69 radio.
Again if you use an Arduino Uno (5 volts), I believe the Adafruit product would be a more compact, convenient option & save you some soldering.
Disclosure 1: I've never received compensation from Adafruit.
Experienced users of Logic Level Converters, what are your suggestions?
|
|
|
Post by papa on Jun 29, 2018 21:41:09 GMT
Welcome to yourfriendcaspian who just became member 725. I'm glad for all the members & guests who stop by to learn DIY Home Automation. Even more, I appreciate those who share their questions, their hints, & their projects that extend this forum's projects. Recently, kisa & I plus greginkansas have had extensive interactions on getting kisa started with RFM69 Gateway & Nodes & with OpenHAB / Mosquitto. Perhaps others of you benefited from following those interactions.
Recently in my interactions with kisa & in separate threads, I've offered more OpenHAB starter files & scripts which I hope will make it easier for you to get started with this exciting, but often challenging approach to DIY Home Automation.
Again I'm glad for all who participate here & for your respectful, supportive participation. I strongly encourage you to become a forum member (no cost) so you can open the pictures, download the code attachments & identify yourself with this project.
|
|
|
Post by papa on Jun 27, 2018 15:37:41 GMT
kisa: "I'd want to be able to click on the individual temperatures and be taken to a page that shows the battery level and RSSI for that temperature node."
In a browser tab, enter http://localhost:8080/basicui/app?sitemap=weather_Metric At first, it should display "Weather ...Outdoor Temp ..." You can click "Outdoor Temp" because it is a link to open a new page of related information.
kisa, I believe you could use ^^ this approach to get what you want.
|
|
|
Post by papa on Jun 27, 2018 15:23:38 GMT
Yes, kisa, as greg said (thanks, greg), you can nest sitemap frames inside of another frame & you can uses various "elements" like text color to manipulate how data displays on a User Interface via a sitemap.
This official documentation on sitemaps is helpful. This section describes a bare sitemap. As it says, a sitemap's contents (in frames) fit between the left & right curly brackets { } shown in the bare sitemap.
Let's apply this ^^ to your sitemap (My.sitemap): (blue text is notes & can NOT be in the sitemap)
sitemap My label="My House" < should be OK since 2 cases of My in green match. { < sitemap's outer left curly bracket Group item=Nodes label="Temperatures" icon="temperature" < If rest of sitemap is OK, this line should work.
Switch item=Act_Node50 label="Node50_Output" < error, line needs to be in a frame. } < error, curly brackets must be a left / right matching pair } < sitemap's outer right curly bracket
I believe this would be a corrected version of your My.sitemap above: sitemap My label="My House" { Group item=Nodes label="Temperatures" icon="temperature" < Indents are cosmetic to help show the groupings.
Frame { < papa added the needed start of the frame
Switch item=Act_Node50 label="Node50_Output" } } ----------------------------------------------------------------
Group item=Nodes label="Temperatures" icon="temperature" ^^ This line works a little differently from a frame. On the User Interface, it displays a temperature icon plus "Temperatures" When you click on Temperatures it should open a new web page that displays the data from all items that defined the group property as (Nodes) like this one:
Number Temperature_Node50 "Temperature_Node50 [%.1f C]" <temperature> (Nodes) {mqtt="<[mosquitto:home/rfm_gw/nb/node50/dev50:state:default]"} ----------------------------------------------
Switch item=Act_Node50 label="Node50_Output" ^^ According to the items you listed above, this sitemap line won't do much. To work this line needs an item like ...
Switch Act_Node50 { mqtt="<[mosquitto:home/rfm_gw/nb/node50/dev16:state:default::]", mqtt=">[mosquitto:home/rfm_gw/sb/node50/dev16:command:*:default]" } With the just above sitemap line & item line, the sitemap should display a virtual switch which when clicked should toggle the node 50's device 16 pin on & off.
|
|
|
Post by papa on Jun 23, 2018 13:43:21 GMT
kisa: "I have no idea what I did differently this time that is allowing everything to work, but it is." ;-) kisa, I would almost expect a !! Hallelujah !! in there, but I guess you are afraid that after all the work we put into this ... (I won't say it) As I often warn, this is a very challenging, complicated project with many important details to cover, especially when doing the RFM69 Gateway & nodes. Of course, once the RFM69 devices are working, one can do more with them than the ESP82xx devices I believe that by trying all this more than once (with support), you accumulated enough knowledge & experience to succeed. It may be difficult to do, but starting over can be a useful strategy. I find it helpful to make & refer to careful notes of what I think worked & not.That's a great plan to save an image of your openhabian SD to have a working backup on hand. It's good to publish here your eventual success with openhabian on a Pine64 single board computer. I'm hoping that my scripts, github sample files, & RFM69 radio test sketches will help users (especially beginners) have a way to check essentials & get hints on what is working & what might need fixing.
If you continue to get log warnings about the .sitemap file & want to fix that, be sure you delete any comments from the file (any lines that start with //, which are ok in .items & .rules files)
I'm very glad you've gotten to this next big success, because for the next few days, I will not be very available to offer help. I hope to hear from you from time to time & also hope when you get insights on doing or extending this DIY Home Automation project that you will share them to benefit others.
|
|
|
Post by papa on Jun 22, 2018 15:43:42 GMT
OK, in a local User Interface (in a browser on a computer in your local network), you tried something like 192.168.1.165:8080/openhab.app?sitemap=MyAND the resulting display of the sitemap still shows no values, right?
To perhaps avoid some confusion, for now, I won't comment on the sitemap & weather warnings in your logs.
|
|
|
Post by papa on Jun 22, 2018 13:33:32 GMT
kisa, I added response comments to a couple of your posts before your last one just above. In the next few posts, I'll respond to different pieces of your post just above. Thanks for providing your log. kisa: "A couple of things stand out, a... (not sure why they are though):- Metadata with key 'mqtt:Act_Node50' already exists from provider GenericMetadataProvider! Failed to add a second with the same UID from provider GenericMetadataProvider!" Troubleshooting tip if you have not tried this: In search engine like Google, search for (& look at the resulting links) OpenHAB Metadata with key 'mqtt:Act_Node50' already exists from provider GenericMetadataProvider! Failed to add a second with the same UID from provider GenericMetadataProvider! This link from the search seems to indicate that this might have been a bug in recent versions. This warning relates to a new OpenHAB feature announced here. As with all "improvements" this may mean changing from what has worked before. I'll have to see. I don't know yet, but this might relate to your difficulty in deleting configurations.
The item Act_Node50 relates to the "actuator" pin for that node. If that pin is set high, then that can turn on an LED or relay that is properly wired to the right Arduino pin & to ground according to the DHT node schematic (pin set low turns off). The actuator can be toggled via the User Interface virtual switch or via the DHT node push button. On your node 50, did you wire LED, relay, or push button?
The good news is that no warning was logged for Node 50's temperature item.
================================================================================== kisa: "there is still no temperatures showing on my mobile phone" papa: Looks like your OpenHAB is connecting to openhabcloud. Is temperature data showing up in your local User Interface that does not use openhabcloud (as the phone app does)?
|
|
|
Post by papa on Jun 21, 2018 16:27:26 GMT
|
|
|
Post by papa on Jun 21, 2018 15:31:11 GMT
papa: kisa, I made some comments at the end of your previous post here. Good to see that your RFM69 Gateway & Nodes are communicating. That's a big step accomplished. kisa: "I recall I may have add some things to the addons.cfg (it's currently in the original state), but can't remember what and can't find it. Could that be the issue?" papa: Yes, that's definitely a broken link between OpenHAB & the RFM69 devices. You need the following for that OpenHAB <> Mosquitto / MQTT communication to work ... For one thing, you need Mosquitto message service installed on the computer running OpenHAB. Remember openhabian has an option for installing that in its additional configuration utility.
You also need configuration of addons.cfg & mqtt.cfg. If you are starting with new .cfg files, you can probably overwrite them in OpenHAB's \services folder with the sample addons.cfg & mqtt.cfg files at my github. Or you can look at those sample files to see what you might need. In the samples I tried to include a lot of what might be needed for this DIY Home Automation Project, including weather, etc. A little explanation about stuff in those two sample .cfg files that relate to MQTT communication & openhab cloud ...
In addons.cfg you especially need two lines with (& no # at the beginning so they are active, not comments): remote = true legacy = true
In addons.cfg, you also need a line that starts with (& has no # at the beginning). binding = After binding = you need to have (don't miss the number 1 at the end): mqtt1 If you have other binding names after binding = then use a comma to separate mqqt1 from them
NOT in my sample addons.cfg, at the end, you also need: (no # at the beginning) misc = [ the short name for openhab cloud that is listed in PaperUI ]
I think the short name might be misc-openhabcloud & that translates to an addons.cfg entry of misc = openhabcloud Please let me know what you find out & if it works.
------------------------------------------- The sample mqtt.cfg has 4 new lines of what is needed & they all have NO # at their start so they are active & not just comments. ============================== kisa: "how to remove the original sitemap from the openHAB options" You deleted it from OpenHAB's \sitemaps folder, right? If after deleting, it still shows up as an option, then stopping & restarting OpenHAB may clear that up or it may clear up over time.
|
|
|
Post by papa on Jun 20, 2018 21:17:48 GMT
Logging & storing collected data depends on configuring OpenHAB's "Persistence" features. There are a variety of databases one can use for this. See this official documentation & internet search (including community.openhab) for more information. My thread on Displaying Weather Data uses one method of Persistence to make a chart of some weather data. One Caution: Persistence methods may write a lot of data to storage folders. Some users (not all) feel that this can fill up SD card storage, even corrupt it.
|
|
|
Post by papa on Jun 20, 2018 21:09:07 GMT
The above thread was updated & augmented in June 2018.
It was updated to work with OpenHAB 2. It was augmented with more examples & sample files to help get a user started with this topic.
|
|
|
Post by papa on Jun 19, 2018 15:39:25 GMT
kisa, don't miss my comments in the two previous posts. Things may have changed since my version of OpenHAB 2 & what's needed for your version may be different than mine. Looks like they're trying to add more security & allow customization of what openhab data is "exposed" online. Of course, it could be more complicated. Please check something for me in your OpenHAB 2 that may help me help you.
Open PaperUI & in the left column click on Add-ons
Click through the links near the top of the page (Actions, Bindings, etc) & look through each list under those links until you find "OpenHAB Cloud Connector"
Don't install anything. Just copy what you see just under "OpenHAB Cloud Connector" & post it here. To the right of "OpenHAB Cloud Connector" does it say Install or Uninstall?
For example, in my PaperUI under "OpenHAB Cloud Connector" it says misc-openhabcloud - 2.1.0 To the right mine says "Uninstall"
^^ !!! kisa, what does it say in your PaperUI? !!! I'd appreciate knowing that.
|
|
|
Post by papa on Jun 19, 2018 15:11:00 GMT
kisa, don't miss my comments in the previous post. Some more thoughts ...
When you do new openhab or openhabian installs, you are creating a new UUID & Secret that need to be recorded in your myopenhab.org account & your phone app.
At community.openhab.org, one user reported this advice:
"Only thing that helped was to delete my account [at myopenhab.org] and create a new one, confirm the resulting email, and then restart openhab."
|
|
|
Post by papa on Jun 19, 2018 14:59:06 GMT
kisa: "I did install binding-weatherunderground - 2.2.0, but found it got uninstalled when I rebooted my OpenHAB Gateway, so I guess there is a setting inside the Gateway that is overriding the weather setting."
kisa: With the weather binding, I did that install through paperUI, add-ons, bindings, then searched for "weather".
papa: I believe you've been doing some binding, etc installs thru my recommended method of editing configuration text files, in this case, addons.cfg. My understanding is that the text file settings take precedent over doing a setting in PaperUI. So ... if weather binding was set in PaperUI, but NOT in addons.cfg then the weather binding install would indeed be "knocked out" when openHAB is restarted.
As I said, I'm working on a revision of using the weather binding, but you keep coming up with other matters to address, like openhabcloud. ;-) ========================
Thanks for clarifying what you mean by the OpenHAB Gateway. What you call "OpenHAB Gateway" I call "the OpenHAB Computer" or "the computer that runs OpenHAB."
|
|
|
Post by papa on Jun 19, 2018 14:34:06 GMT
I understand your frustration. Been there, done that, still happens sometimes. On the good side, it sounds like with your efforts (& mine) you have made real progress: OpenHAB "is running fine and I can view my devices locally." That's a big step forward. Your main hurdle now is access to your OpenHAB on a phone or other computer that is not on your local network. "What is the difference between misc = openhabcloud and misc = myopenhab?" In my PaperUI/Addons/Misc under "OpenHAB Cloud Connector" it says "misc-openhabcloud" That means to install OpenHAB Cloud Connector, addons.cfg must have openhabcloud after misc =
misc = openhabcloud is what I have in my addons.cfg & it is working with the OpenHAB 2 install I have on a Windows computer. I'm trying to research what is the current way to set up the openhabcloud connection & see if things have changed.
Run my script again to see if it finds something missing.
What did you find in your logs about openhabcloud or related terms?
|
|
|
Post by papa on Jun 19, 2018 0:21:16 GMT
kisa: "I did install binding-weatherunderground - 2.2.0, but found it got uninstalled when I rebooted my OpenHAB Gateway, so I guess there is a setting inside the Gateway that is overriding the weather setting." papa: I realize there is a Weather Underground Binding, but I'm working on the Weather Binding because it can use Weather Underground OR other weather data services. Sometimes, these services go down for a while or longer.
BTW, how did you install binding-weatherunderground - 2.2.0? PaperUI ?? Configuration text file ?? Another way ??
=======================================
kisa, when you say "OpenHAB Gateway," I think of the physical device with an Ethernet Shield & an RFM69 radio that bridges communication between OpenHAB & an RFM69 node. I'm not sure that's what you mean. I believe you might mean "I did install binding-weatherunderground - 2.2.0, but found it got uninstalled when I rebooted my OpenHAB service [or maybe OpenHAB User Interface in a browser], so I guess there is a configuration inside OpenHAB that is overriding the weather configuration." I realize you are just learning this stuff & its terminology. Perhaps clarifying what you mean by "OpenHAB Gateway" will help us help you.
|
|
|
Post by papa on Jun 19, 2018 0:09:46 GMT
As I wrote earlier, "Looks like you're using a weather binding install from OpenHAB ONE (perhaps via me), not TWO." OpenHAB 2 no longer puts configurations in a file called openhab.cfg.
Thanks for creating this new thread to address this error.
I'm working on updating weather binding use from OpenHAB 1 to OpenHAB 2. I'll let you know when I feel its ready for you & others to start using it.
|
|
|
Post by papa on Jun 18, 2018 14:43:04 GMT
Sometimes (especially weekends) the openhabcloud services are down for maintenance. I just checked & it was up at the moment. My openhabcloud connection is working & I have the following settings: addons.cfg misc = openhabcloud openhab app on my phone, settings: Demo mode OFF Local URL http://[IP where openhab running]:8080 Remote URL myopenhab.orgUserName [username for my openhabcloud account] Password [password for my openhabcloud account] Ignore SSL Certificates is ON ... Your logs should have an entry about openhabcloud.
You might try rebooting your openhab computer or stopping the openhab service & restarting it.
|
|
|
Post by papa on Jun 18, 2018 14:27:42 GMT
kisa: "My solution was to simply declare TempFactor as a float with all the other variables. Is there any issue with just doing that?"
papa: No big deal. Doing it your way gets the job done, but will use some variable memory that you don't need. I also believe my "better" solution will be easier to see what variables go with what node options.
kisa: "I tried D5 with both SLEEPY and without SLEEPY and both cases gave the same issue. I also tried increasing DSdelay up to 1000, but that didn't make any difference either. I do intend to use SLEEPY on a number of my temperature sensors (not all of them), so I'll experiment further with them once I build them. I don't mind the delay in them working eventually, the plan is to do the measuring for over a year or more, so missing the first dozen or so readings wont hurt"
papa: You're really diving into this DIY Home Automation stuff. Your perspective & approach on the DS18 & SLEEPY seems reasonable to me. What you said earlier ("I am using a 3.3v Moteino, so maybe the data lines are struggling to pull the DS power line high enough") may be a factor. I've used the DS18 sensor with a Buono Uno, not a Anarduino Miniwireless or a Moteino & the Buono typically provides more current than other compatibles.
|
|
|
Post by papa on Jun 17, 2018 23:55:12 GMT
kisa: I'm also finding that I'm getting 85.00 reading when I use the power control line (D5), but after about 3 attempts (sometimes never) it finally gets the right temperature and keeps reading it correctly from then on. If I tie that line to high it shows the correct temperature straight away. I am using a 3.3v Moteino, so maybe the data lines are struggling to pull the DS power line high enough? I'm not sure is this is an issue with computourist_node_v2.2MhC_choices_pub or if I've done something wrong, but certainly happy to hear either way. =============================================== kisa: ... when I use the power control line (D5) ...
papa: What you describe is typical ...
(Line numbers refer to computourist_node_v2.2Mh D_choices_pub) Are you trying to use the SLEEPY functions (sleep & help save battery power) with the DS18 probe? Are you wiring the DS18 VCC line to Arduino pin D5 & then turning D5 off & on to power & unpower the temperature probe? I allowed for that possibility around lines 2193-2206, but in this post's schematic, I wired the DS18 VCC line straight to 3.3 volts so I may have found (I don't remember) that turning power on & off via D5 was not reliable. Typically in situations like this one turns on power & then uses a delay to let power stabilize before doing a temperature read. Line 656 [#define DSdelay delay(300);] sets a delay of .3 second. Line 2195 implements the delay before temperature is read. You could try increasing the DSdelay variable above 300 which may help temp reading reliability.
|
|
|
Post by papa on Jun 17, 2018 19:42:16 GMT
Test Results on Correcting the Sketch Error
Testing compiles of the new sketch version:
With the sketch in the previous post, I customized radio frequency & NODEID 50. 1) I uncommented: #define DS18 & #define DS18B. I alternated uncommenting: #define FAHR & #define CELS << This all compiled without error.
2) I added uncommenting: #define HT << compiled without error.
I added uncommenting: #SOILMOIST << compiled without error.
=======================================
I uploaded the various versions of 1) & 2) above. The resulting nodes all compiled without error AND output expected temp data to the Arduino IDE Serial Monitor.
With the following OpenHAB config entries, the nodes reported temp data to an OpenHAB User Interface:
.items Number TempProbe_Node50 "Probe50 [%.1f °F]" <temperature> {mqtt="<[mosquitto:home/rfm_gw/nb/node50/dev50:state:default]"}
.sitemap
Text item=TempProbe_Node50 =====================================================================
Thanks kisa, for finding & reporting the error.
I will post the above Node Choices sketch with the thread on building one's first RFM69 network.
|
|
|
Post by papa on Jun 17, 2018 19:32:49 GMT
?? A Better Solution for the Sketch Error ??
The solution in the last post would add much clutter for a variable that is only used at line 2328: mes.intVal = mes.intVal * TempFactor; // temperature correct the soil moisture I believe a better solution is to delete these TempFactor lines: 2152, 2157, 2200, 2205 & use their calculations near 2328 as controlled by some #defines. (The line 2328 area is already a SOILMOIST section.) Lines 2327-2329 have been: #ifdef DS18 // We have soil temp & can correct for it mes.intVal = mes.intVal * TempFactor; // temperature correct the soil moisture #endif But we could expand 2327-2329 to be: #ifdef DS18 // We have temp & can use it to correct data based on resistance #ifdef CELS TempFactor = 1+((temp-20)*.00395); // temperature correcting multiplying factor for soil moisture, CELS #endif // ifdef CELS #ifdef FAHR TempFactor = 1+((((temp-32)* .5556)-20)*.00395); // temperature correcting ..., FAHR #endif // ifdef FAHR mes.intVal = mes.intVal * TempFactor; // temperature correct the soil moisture #endif // ifdef DS18 computourist_node_v2.2MhD_choices_pub.ino (107.79 KB) << I believe I've made these changes in this new version of the Choices Sketch. Next: Test Results on Correcting the Sketch Error
|
|
|
Post by papa on Jun 17, 2018 14:49:29 GMT
kisa: exit status 1 'TempFactor' was not declared in this scope
Read this post AND the next post to the end before you do anything with them.
kisa, for the moment, I'll address this part of your post. You found an error, part of the risks of putting so many nodes in one sketch. Maybe I can do some teaching here to help you find & correct sketch errors in the future: Use the Arduino IDE's find function to search for all instances of TempFactor The first instance is line 337 float TempFactor = 1; which is where the TempFactor variable is declared BUT look at line 332 #ifdef SOILMOIST & line 338 #endif // ifdef SOILMOIST. 332 & 338 mean that TempFactor & the other variables are NOT declared unless one uncomments // #define SOILMOIST earlier in the sketch. You don't need the SOILMOIST functions except for the DS18 temp sensor & since SOILMOIST was not defined, you get the not declared error. One possible solution ( not the optimum) is to find other TempFactor lines AFTER 337 & make sure you have #ifdef SOILMOIST before those lines & #endif // ifdef SOILMOIST after them. For example ... Line 1153 has been TempFactor = 1+((temp-20)*.00395); // temperature correcting multiplying factor for soil moisture You could instead have 3 lines, 1153-1155: #ifdef SOILMOIST TempFactor = 1+((temp-20)*.00395); // temperature correcting multiplying factor for soil moisture #endif // ifdef SOILMOIST Next, ?? A Better Solution to the Sketch Error ??
|
|
|
Post by papa on Jun 15, 2018 13:59:12 GMT
kisa: ... made the difference, it now WORKS
Awesome to hear your progress, kisa. As I keep saying, this project is very challenging with lots of details. It's easy to miss things. I'm glad to hear that my time spent in documenting & simplifying (where possible) has been helpful. I'm also hoping that my scripts & RFM69 radio tests will help users (especially new ones) report here what they might need to work on to get success.
kisa: Hopefully I can proceed from here without harassing you too much.
You've been very respectful & have supplied good information to help me help you. I hope you will check in from time to time with your progress & what works for you. Feedback helps & encourages. I'd especially like you to share any new aspects of the project that you discover or try or info that may need correcting.
kisa: Thank you very much for your speedy help and patience You are welcome. Thanks for being the first user to report results from the check_OH script. What did you think of the script? ==============================================
kisa: "one warning/error that comes up now when viewing openhab.log ... weather binding."
papa: Looks like you're using weather binding install from OpenHAB ONE (perhaps via me), not TWO. Please create a new thread maybe called "Issues with Weather Binding" In the new thread's first post, put the last section of your last post: " there is one warning/error that comes up now when viewing openhab.log ... I hate seeing errors"
I'm busy for a couple days, but after that I can probably help you with the weather binding via that new thread you are starting.
|
|
|
Post by papa on Jun 15, 2018 1:02:01 GMT
Original post content was deleted. Post is retained for possible future use.
|
|
|
Post by papa on Jun 14, 2018 21:54:30 GMT
kisa, you are welcome. I'm glad some things are working better. Yes, that is a nice feeling. kisa: "the RFM69 Gateway was working all along (you were correct with the high on D8) and it was my node not doing the right thing, when I got a Moteino and used it as a node (instead of the ATTiny) it worked almost straight away" papa: In this thread, did you see the small Gateway & node sketches I posted to test if the RFM69 radios were working? kisa: "I am using a 5v UNO, but on the circuit I built that attaches to it I use a 5v to 3.3v (and 3.3v to 5v) logic converter (for 4 of the lines and a resister voltage divider for one of the UNO transmit lines)" papa: Yes, that's one approach to protect the RFM69 radio from damage, making sure that only 3.3 volts go from the UNO to ALL the RFM69 radio pins (digital pins as well as the power pin. I've never tried that. From reports here, it works for some users & not for others.
|
|
|
Post by papa on Jun 14, 2018 21:42:04 GMT
Original post content was deleted. Post is retained for possible future use.
|
|
|
Post by papa on Jun 13, 2018 15:25:04 GMT
Original post content was deleted. Post is retained for possible future use.
|
|