xKing

You should be able to mitigate that by changing the state of any node once in 24 hour period, like turn light on/off or add a motion sensor. If no events received from the bridge in a specified period - I just assume the connection is broke somewhere (firewall state expired of what not). My bridge is sending some sort of geofence event every couple minutes so I have not seen any issues with 60 minute interval so far....

Not yet, as soon as I’ll get some hardware with motion :) Interesting, it’s a watchdog that checks last time bridge sent us any event, I may bump that to 24 hours

Well, I try to kill all the lights when I watch a movie so projector screen is the only thing that lights up 😄

If you watch plugin log when it starts - it should tell you the scene order for each group. For some reason order is different depending on a room/zone.

Try adding a custom parameter to the plugin. Name: bridges Value: ['192.168.1.254']

It thinks it found your bridge at 192.168.1.46 - does this address look correct? Can you SSH to eisy and do like: curl -kv https://192.168.1.46/api -d '{"devicetype":"polyglot#huev2", "generateclientkey":true}' -H 'Content-Type: application/json' ideally you should see an error that button was not pressed: [{"error":{"type":101,"address":"","description":"link button not pressed"}}]

Please send the Hue node server log, stuff above looks like a general Polyglot log

Thank you for testing, I've added scenes just now. Effect is weird - bridge seems to accept the command but nothing happens.

Thanks, please re-install, I think I've got that fixed, I have not tested discovery from zero yet. Worst case you can add bridge IP and secret manually :)

See here

Hey, Hue v2 plugin should be in the Beta store if you are brave enough to try. Not compatible with older v1 API (lights will have different IDs), Hue and Saturation removed from API, there are bugs and crashes :-) I don't have a new Pro bridge yet so testing with my old one. Alternatively check out `huev2` branch on the Github

Analog was a community contribution so I have no idea what that does. MQTT is mostly for people who are willing to mess with the code

try maybe sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring pip3 install --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring==3.1.9

Ah I see, polyglot 3 uses separate package repo for each node server - in this case /var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/bitstring.py is unique for LiFX install. I'll need to look around to see how to make it downgrade I'm still on PG2 myself

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.