William Olsen

I just don't want to create an issue for any entity or person potentially getting involved with Pulseworx. I believe that Michel and I know that I also have a bad taste in our respective mouths from dealing with the Owner, I don't think much has changed.

J, verify what you propose with Michel before beginning, there may be licensing issues with Pulseworx. That may be a rabbit hole that none of us wants to go down.

I don't have ANY lighting nodes in Eisy and to avoid confusion I never used any other lighting system than the UPB in my home. I helped out with PCS's migration from X-10 to Pulseworx. I will try and make some sense from the documentation on your GitHub page. With the ISY I was able to control the UPB stuff from the ISY through a Keybus PIM on the Elk. Going forward I would like to do the same thing using the Eisy > Elk to avoid licensing conflicts.

J, for some reason the link to your Github UD-PG3 didn't copy over. That is the document I was trying to reference Did I mention that I was the proud Owner and Captain of a 41' Morgan oil screw (USCG nomenclature) from '76 until 1981? 4"draught 25 tons Net and yes I made Operation Sail in NY Harbor in 1976. Most Patriotic day of my life.

Nothing comes up as a light so none appear in my IoX tree save a pantry light mentioned as a counter Jim. I could weed through once again.

You want to just go back to the BVI's? Buy another ticket

Sorry for the confusion, I've attached my lighting from the ELK RP applicationOlsen Lighting.pdf

Just as a reminder I'm still receiving this message from the Elk NS: ERROR: 08/07/2023 00:05:09 See log for: ELK Controller: Unknown message CD: 18000000000 I'm attaching a PDF of my Elk NS Page, look at the lighting def's that didn't populate. Polyglot V3 Elk lighting table.pdfPolyglot V3 Elk lighting table.pdfPolyglot V3 Elk lighting table.pdf

Jim, I opened the file and searched for "light", this is the only reference to any of my lighting system. </node> −<node flag="0" nodeDefId="counter"> <address>n004_counter_64</address> <name>Pantry light</name> <family instance="4">10</family> <parent type="1">n004_controller</parent> <type>1.2.3.4</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n004_controller</pnode> </node> And concurrently none of my lights appear in my IoX tree and I believe that my pantry light shows up as a counter.

Ooooh, let me get my glasses on.

Jimbo as per your suggestion I opened the link http://192.168.1.12:8080/rest/nodes only to receive an XML document which I've attached. Thanks for picking up this thread again. XML screen.pdf

BTW, I'm still getting this message regularly, I think I mentioned it before: ERROR: 08/03/2023 01:09:44 See log for: ELK Controller: Unknown message CD: 18000000000

Jim, I'd like to see if together we can come to a successful resolution with the lighting portion of the Elk NS. I'm sure your catching up on work related stuff but when you're ready I'll be waiting. Did you get a good picture of the Cat you were on?

You still sailing away? S_it I'm jealous.

And I don't think my comment was included in my last attachment so I'm re-sending it again. Polyglot V3.pdf

BTW, I'm still receiving a banner on the NS stating: ERROR: 07/28/2023 23:57:36 See log for: ELK Controller: Unknown message CD: 18000000000

Jim, I might have not been clear in our first communication. Initially I was trying to find out why none of my ELK (lighting) NAMES (except for 123) didn't populate the Elk NS. I began rudimentary diagnostics by clicking on the link that you provided to list all node names. I have attached a PDF of the PG3 Elk NS webpage showing said link on page 3 that takes me to 127.0.0.1:8080 and put a yellow call out and pointer in the right margin for your convenience. Bill Olsen Polyglot V3.pdf

While trying to query ELK Nodes Server section: If light_method is ELKNAME If you want the ELK Lights to Control ISY Lights then add a Light in ElkRP2 whose name matches an existing ISY node name or address >>To see a list of all your node names and address click ISY Node<< It opens a new window in my Firefox Browser browser that states: Unable to connect Firefox can’t establish a connection to the server at 127.0.0.1:8080 and an error message in PG3 stating: ERROR: 07/28/2023 00:02:41 See log for: ELK Controller: Unknown message CD: 18000000000 What am I missing?

Rick, your elevation above sea level also affects your actual SR & SS times, that's why I suggested confirming your actual Latitude and Longitude as I did during my initial set-up of my Eisy. I've found this calculator easy and reliable: https://latlongdata.com/ Don't use a minus (-) sign when entering the Longitude as it will give an error. I hope this works for you. Bill Olsen

Rick, from the admin screen select {configuration} Tab, make sure that if you observe DST that box should be ticked. At the {Change Location} drop down I actually put in my Lat & Long as a custom item, you could also choose your nearest city Just make sure that the {Timezone Offset GMT} is accurate