tmorse305

Hi @Jimbo.Automates, I have a few devices that I used for holiday lighting but most of the year they are unplugged. I noticed in the log that the NS is constantly looking for them. Is there a way to disable that or do I have to delete them? If I need to delete, what's the best way to do that? Thank you.

When I'm going to be away from home for a while I leave a PC running. I bring a laptop with me, if I need to get into anything I use the laptop and TeamViewer to access the PC at home remotely.

Without the Else the light would never shut off unless there is another program somewhere that controls the driveway light scene. Are there other programs?

You probably should open a ticket on this. Have you looked at the log to see what kind of errors are showing up? I had a similar problem many revs ago, it wasn't all NSs just a few. I deleted them and when I added it back it was fine. Maybe try to delete just one and see what happens? A ticket is probably the best way to go though.

I just upgraded to 3.1.12. My experience was identical to the 3.1.11 upgrade in that I had to restart Polyglot twice in order to get the NSs to start up. With the first reboot, all the NS show up but none are running. A second reboot and all is well.

I thought I would share this with other users of Emporia Vue and Plugs in case you run into it. The 1 second data collection on the smart plugs is actually a 5 second average which can yield some surprising values. From Emporia: "The Gen 2 does save real time one-second averaged power for its measurements, the Smart Plugs themselves will report five-second averages for the same. So the behavior you're noticing as the difference is simply down to the fact that the Gen 2 has a higher measurement resolution than the Smart Plugs do at the moment. That also covers the timing/time-window offsets as well since the Gen 2 will be able to assign usage to specific one-second buckets whereas the Smart Plug has to pick a 5-second bucket for usage as well (which has them look offset when applied on top of each other)." I attached a few example to show what the reported differences can look like. The blue trace is Vue, the orange is the plug. X axis is seconds.

Do you think it's problem that 2 of thermostats have the same name on the NS side. Maybe I should delete one and re- add?

Hi @Jimbo.Automates, I added a new thermostat to my home today so now I have have 3 ecobees. The new one installed fine and showed up in the AC however it seems to be stuck with the green writing arrow to all nodes. I'm wondering if I have confused things for the NS. I moved the 'Greatroom' thermostat to the basement and renamed it 'Basement'. I then installed the new one and named it 'Greatroom'. If I look in the node list in the NS I don't see a 'Basement' node, it's still 'Greatroom'. BTW, the new thermostat is the Premium model with air quality. Thank for adding the support for that!

Are there 3 actual states that the node can be in? In other words is "unknown" an actual state that can be tested or is unknown like blank until it gets updated the first time? I am using another NS and "unknown" is an actual state that I am using programmatically. If I understand you only want to be notified when you leave so program it that when true>false occurs it's locked out from further notifications until it becomes true again when you get home. You also said: if the homelink nearby indicator goes from "true" to "unknown" while I'm away from home. Can it be true if you're not home?

Might be time for a support ticket.

Any errors in the log file? Mine says: 10/21/2022, 18:32:03 [pg3] info: Starting Backup Creation 10/21/2022, 18:32:05 [pg3] info: Backup Successful

What version of PG3 are you running? Have you tried a restart of PG3?

Maybe the password got reset somehow? Try admin/admin

If on a PC, check the download folder. I don't get a prompt either but it saves it in the download folder. I'm using Firefox.

Thank you @Panda88 for fixing this in version 0.3.1! For anyone else trying to use this, the name of the sync module is the name you assigned to your Blink system.

Thanks @bpwwer, I'll do that.

Hi @Panda88, I install the Blink NS and am not sure I have it configured correctly. I have a Blink XT2 which may be a camera model that you haven't incorporated yet. I attached the log after updating the camera. I have a Sync module but the NS could not find the camera when I enter the name 'Sync Module' in the configuration. I didn't give the Sync Module a new name in fact I'm not sure that's the name, I don't see any way to change it in the Blink app. When I tried 'NONE' it found the camera. It is partially working, the temperature seems to be correct, but I cannot control the Arm Status. I can change it in the AC but it does not change the actual camera status. Thank you for developing this NS! Using it will allow me to eliminate a work around using a Hubitat to allow IoP to monitor camera status Blink_10-13-2022_94051_AM.zip

Hi @bpwwer, VUE will not restart after I upgraded to 3.1.11. I tried to delete the NS and add it back but still no luck. Log is attached, there are many errors showing. Thanks for your help with this. VUE_10-13-2022_85819_AM.zip

Upgrade to PG3 3.1.11 fixed the problem

Hi @Panda88, I tried to install the node server(trial) but I get an error, see attached. The NS actually looks like it installs. It appears on the dashboard but only for a few minutes but then disappears as though it was never installed. The process is repeatable. Suggestions? Thanks Update. I tried to restart PG3 to see if it would make a difference, it did not. PG3 log attached from PG3 reboot. I see 1 error related to Blink: 10/12/2022, 19:27:01 [pg3] error: createNS: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3/lib/services/node servers.js:688:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3/lib/services/node servers.js:451:5) log from boot.zip

Update: I don't think this is a NS problem but more fundamental with IoP. I'm going to create a new thread to see it anyone else is seeing this problem

Anything Insteon with a clear backing is easy to tell because the antenna is visible if it's dualband.

@Jimbo.Automates, I noticed my notifications coming through do not include actual data just the outline for what the message should be. This use to work: Notify Test sys_short - [ID 00C9][Parent 007A] If 'Greatroom / Ecobee Controller' Node server Online is Disconnected Or 'Greatroom / Ecobee Controller' Node server Online is Connected Then Set 'Notifications / Notification Controller / Service Pushover HomePush' Device Tims_Phone Set 'Notifications / Notification Controller / Service Pushover HomePush' Priority High Set 'Notifications / Notification Controller' Short Custom Content 16 Notfiication ID Set 'Notifications / Notification Controller / Service Pushover HomePush' Send Sys Short (old from controller) Else - No Actions - (To add one, press 'Action') There are a 2 other choices for the send command, the one above is the only one that does anything. The others send no notification at all: Send Sys Short with Params Send Sys Short Did something change? Thank you Update: I also tried this version of the program, same result, no data in notification. However the Send Sys Short does send a message. I noticed there was an error in the log 'Message is blank" so that was why I changed the program. Notify Test sys_short - [ID 00C9][Parent 007A] If 'Greatroom / Ecobee Controller' Node server Online is Disconnected Or 'Greatroom / Ecobee Controller' Node server Online is not Disconnected Then Set 'Notifications / Notification Controller / Service Pushover HomePush' Device Tims_Phone Set 'Notifications / Notification Controller / Service Pushover HomePush' Priority High Set 'Notifications / Notification Controller / Service Pushover HomePush' Short Custom Content 16 Notfiication ID Set 'Notifications / Notification Controller / Service Pushover HomePush' Send Sys Short Else - No Actions - (To add one, press 'Action')

If you're talking about Insteon leak sensors then just press the button on top of the sensor. Look in the AC, the wet and dry nodes should toggle on/off with each button press. Leave it with the dry node "on" . Then place the sensor on a wet sponge and it should toggle to wet.

@Javi, thank you for widgets in iOS! So far all of the new widget types I've tried are working great. I did run into one problem which I don't think is related to the widgets. I added a program to the favorite screen, and when I go to save it after changing anything I get this error. But if I discard the changes when I get back to the favorite screen the changes have been made and it is operational. I tried a 2nd program and got the same result.