In Part-1 of this post I explored my attempt to get a LoRa gateway (RAK Wireless 2247) and end node (Heltec LoRa CubeCell) connected to TheThingsNetwork (TTN). After two days of deep ‘funstration’ , I was about to give up. But ‘Ole Sopwith NEVER gives up. Up, over, or around – this experiment was going to work.
Many Makers at this point would strongly believe they were sold bum hardware. You know the drill, “When in doubt – blame the hardware.” I do not subscribe to this theory. In all my years of Making, I cannot recall the last time I was shipped a Maker device that was DOA. Yes, it happens, but it is very, very, very rare. The QC in modern factories is excellent, and if something does not work out of the box, I blame the hardware last.
My problem was how to tell if the CubeCell connection problem was the CubeCell or the gateway – or both.
I spent a lot of time messing around with the devEui, appEui, and appKey arrays. Lots of documentation and videos suggest if your device does not connect, you should reverse the array entries to account for endian differences in the transport layer.
In fact, the TTN configuration page has a handy reversing capability that makes copying the entries in either order. Changing the endian order did not fix the issue.
As i continued to review the source code of the Heltec SendReceive.ino example app, I saw this code in the Setup() function:
Several folks have brought to my attention my SkyWeather2 automated installation script fails to complete. The problem has been corrected and a new version of the script is available here.
The latest script has been tested with SkyWeather2 Version 027.1 and Raspberry PiOS dated October 30, 2021.
This is Part-III of an ongoing series of Ol’e Sopwith’s adventures with a home automation project. Part-1 started off with the ambitious idea of doing a bake-off between openHAB and Home Assistant. In Part-II, I learned the openHAB platform and achieved all of my goals of getting numerous Z-Wave devices on-line. I even took the time to create a detailed openHAB “How-To” to assist those of you that are new to the platform. Very happy with the results.
Here in Part-III, my plan was to do the same with Home Assistant. Dig into the bits and document how it works. My hope was to get all of my Z-Wave devices behaving the same way in Home Assistant (HA) as they were in openHAB.
Not so fast Shirley. From the moment I started to learn HA, I ran into problems. For example, I started on this page, “Install Home Assistant”, and followed the instructions exactly. I burned the image and booted the Pi. Notice the below instructions 6-8.
In my last post, I railed about the HP decision to lock down their printer firmware to prevent third party print cartridges from working. Interestingly enough, there has been enough of a backlash that HP decided to respond.
This article from ars TECHNICA describes how HP reacted to the consumer backlash by providing a special firmware upgrade that will bypass the new 3rd party cartridge restriction.
It appears HP has backed off from this crazy nonsense (temporarily) because of pressure from the Electronic Frontier Foundation (EFF) summarized in a letter from Cory Doctorow.
Here is the response from Jon Flaxmen, CEO of HP, Inc. Read it carefully and note the nuance.