William Olsen

I also neglected to tell you that I can't seem to be able to install your latest NS 2023.01.9, I can only load 2023.01.09. I even "Purchased" another copy of .9 and installed it in a different slot and it came up as .09. Lastly I thought it prudent to attach my discreet ON command after I removed the OFF to see if two commands together created an issue. For the life of me I can't turn off BOLD after I pasted something from a NS screen. Thanks in advance for your help Javier - Bill Olsen function, code1, hexcode1, code2, hexcode2 "Power ON","sendir,1:1,1,40000,1,1,96,24,24,24,48,24,48,24,48,24,24,24,48,24,24,24,48,24,24,24,24,24,24,24,24,1014,96,24,24,24,48,24,48,24,48,24,24,24,48,24,24,24,48,24,24,24,24,24,24,24,24,1014,96,24,24,24,48,24,48,24,48,24,24,24,48,24,24,24,48,24,24,24,24,24,24,24,24,1014,96,24,24,24,48,24,48,24,48,24,24,24,48,24,24,24,48,24,24,24,24,24,24,24,24,1014,96,24,24,24,48,24,48,24,48,24,24,24,48,24,24,24,48,24,24,24,24,24,24,24,24,1014",,

Javi, During the recent update to PG3 I was instructed to reload all of my NS's which I did. Something has broken ITach flex IR. After reloading this NS I couldn't get my custom typed configuration parameters (1) to be transferred to IoX I only had two functions, discreet power ON and OFF, I cut the string down to only "Power ON" and only the example ported over to IoX. I had saved the working string to Notepad after I tweaked it, it had been fully functional on the previous PG3. I'll attach the log. Thanks for your help in advance.iTach-IR_9-7-2023_25439_PM.zip

Javi, I need to take a brief respite from my tasks until our location cools off a bit, the current heatwave that we're in followed by a perfect week of 75 F and 40% RH which is normal for this latitude, Its been 95+ with an RH which would typically be a cuss word and though I have proper Air Conditioning, visits outdoors suck the energy out of me. With the back Surgery I went through in 11 of 2016 has restored a few parts of my normal ability I'm very limited by the local weather conditions. I sorry for the delay of a response but most of my time this week has been spent horizontal. Please excuse my lack of functional ability that has caused my delayed response. (the word "sucks" comes to mind). I'll get back to you when I have some tolerable "sitting" time at my desk. And as always, thanks for being an obvious Professional in your field of expertise. Your actions and diligence appear more often than as in past years

Jim, I upgraded to PG3x Version 3.2.3 Frontend Version: 3.2.3 IoX Version: 5.6.4 over the weekend and as instructed re-installed all of my Node Servers from the PG3 menu. I've found that iTach version 2023.01.09 [Beta] was the only version of the NS that PG would install not 2023.01.9. the one custom entry (a Power ON test string no longer works although it shows up in the "Main" tree. iTach-IR_9-5-2023_30701_PM.zip

This will stop when I disable the audio section on the M1XEP, low priority for me as long as we know why it was generated and as I said earlier "good catch" It might be an issue if someone else is either using the M1XEP or another 3rd party program like eKeypad. I really appreciate your timely response to issues, it clearly reflects your dedication and competence.

I hope you find these document helpful.russound-rs-232-V01_00_01.pdf

Wow good call Jim, I've been offloading programs from my M1 and writing the equivalent to my Eisy. Both the Elk and IoX share the same IP to serial converter. Are you able to enlighten me as what's causing this to happen, an unexpected response from the CAM or something else. The M1 shuts off my TV and Russound audio when I turn off the basement (my office) lights. Clearly the instructions about Zone Nodes were clearly explained in MD#Zone Node, I must have not used the Git search option properly or the Find utility in Firefox. I think I explained why my "sitting" time is really limited, I get a couple of hours if the weather's good, less if I do something physical I shouldn't. Even though I can walk again after spinal surgery Narcotics just mask the pain, It really sucks. Thank you for your prompt reply with information I can rely on (they used to say "take to the bank" 🙂

Jim, I read through your entire repository on GitHub and couldn't find any answer to my original question so my question up above remains 🧐 Another issue Jim, I'm still getting this message: ERROR: 09/01/2023 01:39:10 See log for: ELK Controller: Unknown message CD: 18000000000 I can't find an error in either the PG or Elk log that corresponds to that time (12 hr format assumed)

Me too

Jim, I just found a set of very well written of instructions at Would anybody able to put this as a sticky at the beginning of the Elk forum? Thanks

Jimbo, Could you describe how these options are used? Thank you kindly.

😁

Bob: I hate being a problem child but; I don't know what this represents. I've attached the log from 2.12, there are a couple of errors that may help and I've lost my 5th source "Tivo". For a reason unknown to me "Inactive" appears as my 1st choice of sources, "Tuner 1" as my 2nd, "Tuner 2" as my 3rd, "SonosName6 as my 4th and Verizonme2 my 5th. My actual sources start physically as "Tuner 1" being the 1st source then "Tuner 2", "Sonos", "Verizon" and finally "Tivo". The text that I've emboldened has no business being there as it doesn't show up on any of my keypads. Russound_8-31-2023_122058_PM.zip

You should probably see this Russound_8-30-2023_62520_PM.zip

Bob, does this mean anything to you?

I will re-load it, thanks for the quick response just please see below.

I hope this helps B. Russound_8-29-2023_80055_PM.zip

Log, not NS

Thanks for the prompt reply Bob, I will post a copy of the NS tomorrow morning, I have to be brief as my dinner bell (spouse) just shouted down the stairs that dinner is ready, I've been at my desk since 7 this morning. Shall I PM or Post a copy of the Russound NS? BTW I did mention that "Zone OFF & ON" both work from the admin screen so a comm issue seems unlikely.

As of the recent PG#3 v3.2.2 the Russound NS in my case no longer populates nor does it allow control of any features (excluding zone off and on) for any of my zones. Most items operated correctly prior to the PG# update. I can still control all features of the CAM from my Elk M1. (since the early 2000's) I am also unable to find in Programs an "and" command that has anything to do with my CAM although I have been able to use the "if". And I'm having a devil of a time with DHCP reservation and I've had to place my Eisy in the dreaded "DMZ zone" to be able to communicate with any of my NS's

Jimbo, I am absolutely unaware of how the PG3 interacts with the individual Node Servers, the IoX or the Eisy as I've really been out of coding since my back surgery in '16, I just can not sit for very long spells. It might be just as easy within your Elk NS to label everything after 192 as ELK SCENE instead if LIGHT without getting into yet another Rabbit hole. The table method that Elk uses in the RP application to display lighting names and options remains the same regardless of the choice of lighting Vendor. With respect to the lighting portion within your NS, the NS doesn't have to know how to create a scene, it is generally defined by the manufacturer's design and is commonly held within the lighting hardware itself, in my case Pulseworx. I hope this information might be helpful to persons new to either product ( Eisy or Elk M1) and using any of the several lighting formats that the M1 can accommodate.

Looks like a wonderful job J, one short factlet that I thought you should know. In most lighting applications regardless of communications technique use a group of addresses that control one single point, the other that UPB and Elk refer to in context are scenes which control multiple devices within the lighting network with only one external command. I'd like to point that Elk treats points 1 thru 192 as individual points and 193 thru 256 as scenes which follow a slightly different command structure. I hope this helps.

No, i didn't initially however when I saw your reply I changed it and re-booted the IoX. I had a couple of entries at the beginning of the log, I don't know if they would be of interest to you: And thanks for staying on this for me. 2023-08-13 15:03:46,473 Thread-53 pyisy.events WARNING events:_route_message: ISY Received Malformed XML: <?xml version="1.0"?><Event seqnum="1647" sid="uuid:28"><control>_7</control><action>1</action><node></node><eventInfo>U7 Rest: submitCmd([n006_d_off_discreet],[COMMAND],[BUTTON.25=1&CODE.25=1&CONNECTOR.25=1&REPEAT.56=1])</eventInfo></Event> 2023-08-13 15:04:23,762 Thread-53 pyisy.events WARNING events:_route_message: ISY Received Malformed XML: <?xml version="1.0"?><Event seqnum="1651" sid="uuid:28"><control>_7</control><action>1</action><node></node><eventInfo>U7 Rest: submitCmd([n006_ony_power_2btn],[COMMAND],[BUTTON.25=0&CODE.25=1&CONNECTOR.25=1&REPEAT.56=1])</eventInfo></Event> 2023-08-13 15:04:58,361 Thread-53 pyisy.events WARNING events:_route_message: ISY Received Malformed XML: <?xml version="1.0"?><Event seqnum="1658" sid="uuid:28"><control>_7</control><action>1</action><node></node><eventInfo>U7 Rest: submitCmd([n006_ony_power_2btn],[COMMAND],[BUTTON.25=0&CODE.25=1&CONNECTOR.25=1&REPEAT.56=1])</eventInfo></Event> 2023-08-13 15:46:07,620 Thread-620 udi_interface WARNING Controller:elk_restart: ELK Controller: Restarting ELK Connection

Got it loaded after a few hiccups mainly with PG3. The NS is still not properly differentiate between tasks, counters and lights. I'm attaching the "long form" log. Thank you for the quick turnaround Jim! ELK_8-13-2023_30207_PM.zip

Jimbo, would you happen to have one of the older versions of the Elk NS before you removed the lighting option?