hart2hart

Michel I ran the steps and during the update of the node server MagicHome in slot two the follow occurred: updating MagicHome Collecting git+git://github.com/fahrer16/flux_led (from -r requirements.txt (lin e 2)) Cloning git://github.com/fahrer16/flux_led to /tmp/pip-req-build-548hdu25 Running command git clone -q git://github.com/fahrer16/flux_led /tmp/pip-req-b uild-548hdu25 ERROR: Error [Errno 2] No such file or directory: 'git' while executing comman d git clone -q git://github.com/fahrer16/flux_led /tmp/pip-req-build-548hdu25 ERROR: Cannot find command 'git' - do you have 'git' installed and in your PATH? The Node will only show disconnected after stopping and starting. It has following in its Polisy log: 2021-06-15 15:06:11,082 MainThread polyinterface INFO polyinterface:init_interface: Received Config from STDIN. 2021-06-15 15:06:11,083 MainThread polyinterface INFO __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting... 2021-06-15 15:06:11,087 MainThread polyinterface ERROR polyinterface:write: Traceback (most recent call last): 2021-06-15 15:06:11,088 MainThread polyinterface ERROR polyinterface:write: File "./magichome.py", line 9, in <module> 2021-06-15 15:06:11,090 MainThread polyinterface ERROR polyinterface:write: from flux_led import BulbScanner, WifiLedBulb 2021-06-15 15:06:11,091 MainThread polyinterface ERROR polyinterface:write: ModuleNotFoundError 2021-06-15 15:06:11,092 MainThread polyinterface ERROR polyinterface:write: : 2021-06-15 15:06:11,092 MainThread polyinterface ERROR polyinterface:write: No module named 'flux_led'_led'

It is correct.

Scene exists in the devices and ISY knows about the scene to get status control if good comms exist. It operates independently of ISY. Same as manual just easier to create and ISY can be used to replace a defective device and of course can control or see status.

I agree. I’d create a scene that does what you need using the ISY by bringing them close to ISY for scene creation and then moving to desired location. When you can get a dual band device update so ISY will see scene status.

Not to lessen or devalue anyone else’s point and experiences, I received a sidewalk notification and turned it off. My dealings with Amazon have been nothing but positive.

If you’re using Polisy, The Vitrtual nodeserver I mentioned lets you add a virtual switch to a scene making it easy to test for scenes being on or off and then based on time of day etc adjust the scene or scene segment. You’ve got right thought process. Good luck and post back if you think we can assist. I’ve posted and got remarks that i didn’t use but made me approach it from a different perspective.

Agree but he said he’d factored in keypads as multiple devices so I’m at a close starting point. Again was just a thought.

I’ve got 299 Insteon devices and 84 scenes which translates to 665 plm links. Your number just sounds high but obviously I don’t know complexities of what you’ve done. I seem to recall that orphan links can occur in plm if you make lots of changes. Has anyone suggested doing a restore plm which will clear and add back links in ISY database to the PLM so you can confirm something has not occurred and inflated the actual number. Also, there is a Virtual Nodesever I’ve started usingits variables as placecholdrrs that might eliminate any hidden keypadlincs you have. Additionally, I have several scenes with the right lights included snd use adjust scene in programs instead of duplicating scene with different settings. Don’t know if this would help but FWIW. Good luck.

Have you used the nodeserver ISY inventory or happen to know how many Insteon devices and scenes you have?

Watch it closely, when that happens it may mean a full PLM failure is imminent.

Watch it closely, when that happens it may mean a full PLM failure is imminent.

One thing to look at is the IP address. I set the IP address of the Polisy the same as the RPi polyglot was installed on. And cut off RPi before bringing up the Polisy and doing the restore. The ISY store s IP address of nodes.

Gotcha. Fantastic, I think the light is on. Lol When entering it in configuration, is the id just supposed to be unique number within the Virtual Nodeserver … not be a pointer to an ISY variable? This is fantastic tool ! Thank you.

@markv58 or others... I just added the node server to create a couple virtual switches. I read this thread but it is very focused on temperatures so maybe I missed what I need. I want simple switches that are linked to state variables with a value of 1 for On and 0 for Off. I entered their variable ids in node config and they showed in ISY as expected. My question is with virtual switches do I need programs to move the 1 and 0 as On and Off or for switches is that part of the nodeserver purpose? It appears I do since turning On or Off the virtual switch does not impact the variable and changing the variable value does not impact the virtual switch state. I don't want to add programs if they are a duplication of the nodeserver programming and its not working as I've done something else wrong or its one of the polling intervals. Thanks!

Y is a crystal and I’m of no help beyond that on specs. Have you run continuity checks to confirm that there are no broken traces where capacitors leaked snd failed. Board looks rough next to them.

Are there any If conditions on the folder that contains the non running programs. If a folder is not true no programs in it will run. Also I’d put wait 15 seconds to get a picture of what’s going on. It’s on so short at 1 second before it gets turned off. The second it’s off the program will revaluated and become false. One more consideration is that those fans are big electrical line noise generators. I did similar so I repeated the off command 3 - 5 times with 1 second in between to try snd get through. Especially true if switches are not dual band or do not another dual band device nearby to serve as alternative path to control it.

Thanks [mention]fahrer16 [/mention] I updated successfully and UD Mobile sync parse error is gone. I have two LED strips. They are not automatically discovered so I hard coded them in node configuration which works great. Today when I updated , I saw two parse errors in the log and I could not control LED strips. Realized both had gone offline to Wifi. Power cycled lights and restarted Polisy. The parse errors are gone and I can control lights. I’ll be fine from now on but might be good if parse error said can’t find the hard coded light set for first time users.

You can add it as a widget on latest versions of iOS. It might benefit from a smaller widget tile option.

If I recall correctly, the ISY send a scene command and expects all associated devices to get and process it. For critical lights, I wait a few seconds in program and then send an off command to the switch that actually controls the load(light) to ensure it is off. The device command vs scene command has built in retry logic.

You send reboot ISY relay command to nodelink . I don’t know what it actually sends to ISY. I assumed it was a REST command but not sure. I’ll edit prior post.

If you added zwave devices, wait for other advice as I’m less than a novice with them. Otherwise,Restore your last 5.0.16C backup. Factory reset the devices you’ve added and ten add them again including any scene setup. You will need to recreate any new programs so copy them into a text document to make it easy to create them.

I used new feature of nodelink that sends via relay a reboot ISY command. I save the value of DST in a variable. When the saved value does not equal the current value. I just reboot ISY. This prevents me from having to remember to add programs that have the time change Sensitivity. I’ve been doing same manually for years. I’ve got run at startup on all programs to ensure they set heartbeat etc in motion.

Do you have another power supply? If not, do you have a multimeter to test voltage of current PS? I’ve seen voltage be enough to get small bit of led activity but not enough to power full devices. Not specific to Polisy.

Try taking out the “and status is off section” out and see if it turns on all 3 lights. The first set to 40% makes the if condition no longer true. I thought it would be atomic transaction unless it hit a wait but worth trying. As a simple test select the program and select run then.

I’ve used the same method and don’t necessarily disagree. Just know if any of the conditions that caused the currently running Then or Else path change, the program will reevaluate and may stop or take the other path depending on values. To OP posting a copy of program may be useful.