Current State. What makes it show?

Looks like an ESP8266, with an LCD display and a DHT22 Temp/Humidity sensor... Sound about right?

Have you looked at my HubDuino project? You can build the same thing, with code and drivers already written for Hubitat or SmartThings, for about $15 (no LCD). Obviously, it's nice to have a business writing and maintaining the software for you, which it sounds like pp-Code is doing a great job of.

Take a look at HubDuino. It can do temperature measurement, servo motors, contact sensors, alarm sirens/strobes, etc...

1 Like

BTW - Did you miss my earlier post regarding CaSe SeNsItIvItY ?

You may be right. And I will check it out. Right now though, I'm time limited, so I don't mind slipping these guys 35 bucks for something ready to rock 'n roll, but I'm all for DIY usually.

I MUST have missed your cAsE MatTerS post :slight_smile: because I had to learn it the hard way. I'm used to variables requiring it, but that looked like a string and I didn't think it mattered.

Thanks for all your help. Even the parts I missed.

1 Like

Oh, and it looks like an AM2302 T&H sensor

That's actually a pretty decent price, since it comes with the enclosure and power supply as well (and a team a developers!)

Which is just a DHT22 with different packaging, I believe... :wink:

Another option you might be interest in, if you want something smaller and Zigbee, is @iharyadi's Environment Sensor. It does temperature, humidity, barometric pressure, illuminance, and is a Zigbee repeater. If also has some GPIO pins that you can use as you see fit. Very cool device!

1 Like

I'll check that out, thanks. (and i just looked at the numbers on the side of the case. I haven't researched any components) I doubt there are 47 different companies making these sensors.

I don't appreciate my code being rip and all my credits being stripped out. Either restore the credits or create your own code.

Code:
https://raw.githubusercontent.com/sgrayban/Hubitat-Ports/master/Drivers/rpi/Raspberry-Pi-Stats.groovy

/**
 *
 *  Raspberry Pi Stats
 *
 *  Copyright Janos Elohazi
 *  Copyright Scott Grayban
 *
 *  Ported to Hubitat by Scott Grayban with help from ogiewon and royski
 *
 *  Monitor your Raspberry Pi using SmartThings and Raspberry Pi Monitor <https://github.com/sgrayban/raspberrypi.monitor>
 *
 *  *************************************************************************
 *  Licensed under the GNU v3 (https://www.gnu.org/licenses/gpl-3.0.en.html)
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *  *************************************************************************
*/

GPLV3 does NOT give you any rights to remove credits and pretend you wrote it. Friggin thieves.

He's not overreacting and you violated the license that he released the code with. You need to include the original license and mentioned what the handler started out as and include the original author. (I usually release under Apache 2 so GPLV3 might be a little different, but I'm sure it requires at least those things)

Borrowing a block of code is not the same as taking someone else's handler, making a few changes, and re-posting it. Developers spend a lot of time writing code and they post it online for free so that others can use it so either respect their license or don't post the modified version at all.

Like you said, you don't have time to write code from scratch, but if you did spend lots of time writing a full handler and then someone removed your name from it and posted it on the forum, I'm sure you'd be upset too...

2 Likes

While I personally don't really care if I get credit on things I am doing/giving away for free anyway (I mean really, what are the damages - loss of 'street cred'?), Scott and Kevin are 100% right that what was done is not proper and should not have been done that way.

It takes MORE WORK to remove the credits than to leave them in....So lack of time isn't a good excuse.

2 Likes

Look... You can rationalize it however you want. But the fact is, you were wrong on how you went about this.

Just own it, and move on. We all make mistakes and learn from them.

2 Likes

What I don't get is that someone called you out for removing their license and you could have spent a couple of minutes adding something like below to the top of your code which could have solved the problem, but instead you posted a bunch of times trying to rationalize the removal of the license.

/**
 *
 *  pp-Code H&T Sensor 
 *
 *	Created from  driver Raspberry Pi Stats
 *   - Original Copyright Janos Elohazi
 *   - Original Copyright Scott Grayban (sgrayban)
 *   - Originally Ported to Hubitat by Scott Grayban with help from ogiewon and royski
 *
 *
 *  *************************************************************************
 *  Licensed under the GNU v3 (https://www.gnu.org/licenses/gpl-3.0.en.html)
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *  *************************************************************************/
3 Likes

He didn't use just a block of code he USED the WHOLE thing and just changed a few variables. IT'S THEFT and if I want to take this to court he will lose. I can still file a complaint.

I agree he shouldn't have done that, and he was in the wrong.

But come on - take it to court? For what? What are the damages? I'm agreeing with you in spirit, but let's not get hyperbolic here. At best you could get a cease and desist, but whoopie...

Because this hasn't been the first time some lazy ass loser stole my code and pretended they spent hours making it.

Which is wrong - I agree with you. I'm just pointing out there is no "take them to court" on something that has no damages. That's all. If you, or he, was selling the code in a product there would definitely be a case, but neither of that is true.

In any case, hopefully people got an education/reminder on this as to proper crediting of software reuse. It is important, and the right thing to do - even on non-commercial code.

3 Likes

The reason I am so pissed about this particular rip-off is instead of the user asking me for help to modify it he goes to Dan knowing that Dan doesn't realize it's my code. That tells me the user intentional knew he was going to rip my code and pretend he made it.

That is why got I livid about it.

2 Likes

That's pretty lame, for sure. :frowning:

2 Likes

I don't mind helping to modify my code for a particular reason.... but to ask someone else ? That's rude at its finest.

Rant over.... for now.

1 Like

I didn't remove anything. The moderators did.

I came here with the intention of helping anyone who might want to use this sensor. I have tried to explain why I didn't include the original author on my modifications; in case it was defective, I didn't think it would be appropriate to tie him to it. I never took credit for anything, and never claimed to be the author.

I came here with good intentions and have been lied about (saying I used all the code and changed variables) when I used maybe 25%...been called a lazy, loser and thief, banned, threatened with a lawsuit (had a good laugh about that one), and generally attacked by a wolf pack for what amounts to an etiquette mistake.

I couldn't care less about taking credit. My self worth is not tied to recognition for a few lines of silly driver code.

So maybe I could have handled it differently, but I never intentially meant to harm anyone.

Anyway, the original post is gone, so everyone should be happy. I'm out.

1 Like