tmorse305

Thanks for the clarification!

Hi @bpwwer, The status of the NS in the AC is always True even if I stop the Node Server. I've only waited a short time, does it eventually toggle to False? Some NSs toggle immediately (VUE, Notification for example) Others have the same behavior as WeatherFlow (August, MQTT) Why do they act differently? Thank you.

Have you considered getting the PLM repaired? LINK

Fixed with update 0.3.17. Thanks again @Panda88!

Hi @Panda88, I can no longer control my blink camera from IoP. I can change the arm state in the AC and it looks like it makes the change but when I check the Blink app the change did not occur. I tried a restart of the NS but the same result. I did notice some errors were reported after restart at 2022-12-12 15:18:13,843. I'll PM you the log file. Thanks for any help you can provide.

What kind of switches are you talking about? Which switch did you replace? Was the replacement switch new or used? When you replaced the switch did you have to disconnect any other wires to gain access. Maybe a mis-wire on re assembly?

You only want the api key not the whole url. Just the x76XxXX....... part

Do you have the API key configured correctly? It looks odd in the error message above. From Jim's instructions: API Key Enter your API Key for Webhooks by going to Maker Webhooks then click on Settings. This shows a line at the bottom like https://maker.ifttt.com/use/xxxxxx the xxxxxx is your API Key. Copy and paste just that part to the API Key. It looks like you included the https://maker.ifttt.com/use part. Just enter the xxxxxx part. A typical key looks something like this: duC-0KVspL2ctf2jpgPEs1

@ISY4Me, its a program, I am using the Notification NS but of course any notification tool will work. I put the program in a screen shot so you could see the breakdown of the Notification command. ProgramName-NodeST is a customization that is: ${sys.program.#.name}: ${sys.node.#.name}=${sys.node.#.ST}. This program will fire when ever there is a change in the listed NSs so you get notified when they go offline and when they come back online.

Did you check the NS log for any errors? I find that the the connection to ecobee will drop. I don't know if it's the NS or the ecobee server. I get a notification when it drops, usually its back up in a minute but sometimes it takes longer

Thanks @Javi, if anyone else encounters this bug there is a simple workaround. It only occurs when the folder's children count matches folder's siblings count. So just add a folder or widget so the count is not the same.

@Javi, do you mean the backup file? If not where do I find the db file? The problem survives a swipe.

Hi @Javi, I was creating more widgets in a folder when the display started acting strange. I couldn't move up and down the hierarchy correctly. See screenshots. From pic1 I pressed the folder "Equipment Status". In pic 2 you can see the header changed but the contents was still the Favorites screen. I pressed edit and in Pic 3 the screen now displays the Equipment Status folder. I pressed the back arrow and you can see I'm back to the Favorites screen header but the contents is still the folder contents. Suggestions? Thank you!

This problem has been resolved with PG3 3.1.14 and a little ssh magic from @Michel Kohanim. Thank you!!

Thanks @Jimbo.Automates, it's better to keep the flexibility on dynamic IPs. I wasn't sure how much resources it was consuming or how much network traffic it was creating. Maybe I'll just keep it plugged in when not in use.

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?

It is also powerline only. The other reason I think it's a unit problem is that I had an outdoor module plugged in both outlets, same vintage. One works, the other is intermittent.

@PinchRoller, yes to all questions. With the event viewer set to level 3, the issue is there is no ack coming from the module when it doesn't work. So it's not getting the command. If I move it close to the PLM it never misses so there seems to be a loss in sensitivity.

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 have an old outdoor module (#2456SE not dual band) that I have used for years on holiday decorations. This year it's starting to have trouble getting commands. It's the same plug on my porch I always use and there is a second outdoor module plugged right in next to it that works reliably. Giving it's age I figured maybe the capacitors are finally giving up. So I took a dremel tool and cut a hole in the front and back. I changed the 3 electrolytics but the performance didn't improve. Is there anything else in the modules that causes loss of sensitivity? A couple of notes for anyone who want to try this: Components face the bottom of the module Plenty of air gap on the topside to avoid hitting the board On the bottom, the relay is tight up against the plastic be careful cutting in that area I left a wide shoulder all around the hole so I could silicone glue a piece of clear plastic to cover up the holes

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?