[No Longer Maintained] Withings Integration

[thebearmay]

Not a lawyer, but 2 ways I can think to approach this:

1. Use the code as an abandoned work as it is marked “No Longer Maintained”

2. Use it as the source for a derivative work
   a) Would need to acknowledge the original copyright

   b) dman2306 would retain all rights to the original code and may have some rights to the deriviative

[JustinL]

I actually happen to be an IP attorney…without any granting of a license, we can’t do any of that. At least not legally. I saw in one of his posts for HPM that made it sound like he just didn’t even think about a license, so I suspect it is just an oversight on his part. Just proving challenging to get in touch with him.

[thebearmay]

@JustinL

I actually happen to be an IP attorney

There’s the problem …

[JustinL]

@thebearmay

There’s the problem

Ha, at least I’m not chasing ambulances! I just wish I had noticed this license issue earlier. Since using HPM, I haven’t had to even look at the code, so didn’t think about it. Maybe that was his plan all along with HPM

[csteele]

dcmeglio/hubitat-packagemanager/blob/master/LICENSE

[csteele]

[BETA] Hubitat Package Manager

100%. All I can say to that is, can I guarantee I'll maintain my code years from now? No. Can I think of a scenario where I'll take down all of my code? Nope? My reasoning? I'm not 12 The thing with any of these solutions, forking, cloning, anything else really, it's not going to automatically grab changes. So if the original author makes changes, your fork doesn't automatically update those. HPM is released under the BSD license which essentially means you can't change the l…

He did explain his License in the last line of that message. And again:

[BETA] Hubitat Package Manager

Hmm a screenshot would be great, I'm not sure I understand the request so that would help. Nope. That said, I've kind of also made it clear that I'm not really interested in that. At the same time, the code is released under the BSD 3.0 license so as long as they respect that license they'd be free to take my code, change it up, etc. without even telling me.

This is a Withings Topic and I'll note that there's no License added in his Github repo for that code.

[rlithgow1]

As a layman I think that last bit answers @JustinL 's question.

[JustinL]

@rlithgow1

I think that last bit answers @JustinL 's question.

Well, as @csteele suggested, that last bit gives us good insight into Dominic's intent for licensing the HPM app, but isn't dispositive on Dominic's intent for licensing the Withings integration. If I read between the lines, I think Dominic would / will license the Withings integration in the same way as HPM, but he hasn't actually done so yet. Hopefully Dominic will respond to my github pull request / issue soon.

[rlithgow1]

[JustinL]

Heard from Dominic on github. He’s indeed going to apply BSD to this integration as well.

[JustinL]

Dominic just accepted my pull request on GitHub to add the BSD-3 license. So it’s officially open source and able to be maintained by anyone able and willing!

[jrfarrar]

Is this app still working?

[rlithgow1]

Works for me.

[rabell]

I use it every day.

[DiverRich]

Same here. My whole presence scheme in node-red relies heavily on it.

[rlithgow1]

[jrfarrar]

Ok, I see my issue...my device is somehow now there anymore...no idea how it would have gotten deleted. Is there a way to get it back? My virtual switch is working fine.

[rlithgow1]

If it's not in a backup (settings backup and restore) you'll have to recreate it

[jrfarrar]

so just delete the connection in the app and reconnect?

[rlithgow1]

You should only need to create the virtual device then assign the driver. As long as the app is authenticated everything else should run fine