xKing

so what exactly do you get in the lifx log? bitstring version is ok (3.1.9). Version 4.0 is what caused trouble

what do you see in pip3 list output? Problem is not related to hardware platform (eisy, polisy, rpi, etc), it's just a new library compatibility.

so original LiFX integration is based on LifxLAN python project that was abandoned for a few years, one of the libraries it depends on updated and broke it you can work around that by doing something like this: sudo -u polyglot bash pip3 uninstall bitstring pip3 install bitstring==3.1.9 I don't know if LifxLAN author is going to update their library...

I don't have any of those mini ones so can't really test, sorry. Also @einstein.42 is the author, I just ported it to PG3

so for motion - Hue hub is a "pull" thing, in other words - node server asks Hue hub for a status every short poll (I think it's 15 seconds by default). Even if you happen to catch motion reported - 15 seconds delay would be kinda weird. Same goes for other hue input devices - buttons, switches.

Sorry, I don't monitor forum normally. It's mostly for Sonoff device control, however people added their devices to the node server. Take it as a template and you can add any MQTT device you have.

can you git pull now? I've added it

Looks like you using older node server from my GitHub, I moved it to the UDI GitHub a while back. Just re-install the node server and you should get the one with SE3800A included.

I never remove any models from supported list. Just added SE3800A and SE3800H, should work do git pull please

sure, go for git fetch

@larryllix looks like you've set it to port 80 somehow? That is not allowed by FreeBSD. Drop the db (way to drop was mentioned before) and it will start.

That's old nodeserver that is no longer in the store. Nest2 does not poll, it uses REST Streaming.

There are no “Nest limitations” and 30 seconds sounds ridiculous - I typically get “Person” event on ISY (have a blue LED lighting up on my desk :D) couple seconds before I get push notification on my phone.

Should be within 2-3 seconds

Did you try Nest node server via Polyglot? I support Person, Motion and Sound as separate triggers

Yeah Hello shows up as a camera in my NodeServer, will show a screenshot later tonight P.S. Attached is a screenshot of how Nest Hello looks like. There is no API for the doorbell button right now, but "Event - Person" always works

Home Assistant has Ring integration already (opensource), you may want to give it a try while waiting. I sold my Ring and got Nest Hello, so can't really test that....

Maybe add a specific "driver" name for Motion like we have CLITEMP and CLIHUM for temperature and Humidity? Many things do detect "motion" from Nest Cameras and door bells to wireless tags.

Make it a bit MAP 128 bit integer, each bit would indicate a capability like for example: 0x0001 is a motion, 0x0010 is temperature 0x0011 has both

For lights I would like to see: Generic Light Dimmable Light Color Temperature Light (shades of white) Color Changing Light MultiZone Light (LED strips, tiles, etc) Thanks!

nodeType was described in NodeServer SDK version 5.0.2 and then taken out in 5.0.4, I guess that decision needs to be reconsidered? BTW, I use CLITEMP for current temperature in Nest, not ST. My understanding that ST means status of the device itself, not the status of it's surroundings?

There are no official API for Ring, but few folks figured out how to work with it unofficially. I'm wondering if you can try that script and see if it really controls the flood light? If yes - someone might be able to write a node server based on it BTW, I've noticed that Ring thru IFTTT has a horrendous delay, sometimes like 60 minutes, however Ring via Stringify is almost instant.

For those who run ISY with 5.0.X firmware please look here, this will be a solution going forward. Same functionality as ISYNNode, but now within the Polyglot v2 framework.

yup, I know...

works great unless app developer uses certificate pinning so app won't accept "fake" Fiddler's root certificate. But in that case you can sniff exchange between your browser and web portal (there is no pinning possible in this case)