Everything posted by pjjameso
-
Demo worked fine, purchased version does not
Thanks Bob, Only thing that changed was the latest update to pg3x. Could that be the cause? Interesting in the log it has found the MAC addresses and the names of the units but will not create the individual nodes. Wonder if there is someway I could create them manually. If someone has a working system would you mind letting me know the node information in Polisy so I can create the node there. Update: was able to add Family Room to Polisy but didnt create node in PG3x., guess its a one-way deal only. Interesting that if in Polisy I set the volume to a level the request shows up in PG3x log as being received. 2023-12-30 15:18:31 debug: NS: Message Received: { command: { address: '8b16614', cmd: 'SVOL', value: '17', uom: '51', query: {} } } 2023-12-30 15:18:31 error: POLY: Node 8b16614 not found The log actually shows the family room unit playing and does indicate the actual volume level when I change it up or down. ST-Sonos_12-30-2023_23418-PM.zip
-
Demo worked fine, purchased version does not
Thanks for taking a look at this... ST-Sonos_12-29-2023_74022-AM.zip
-
Demo worked fine, purchased version does not
Thanks Bob, Have done this multiple times even using different slots. Have rebooted Polisy serveral times before and after the NS was installed. Im stumped at this point. Not sure if the following entries from the log would help 2023-12-28 11:14:37 error: POLY: Queue Message Queue Processor process error caught. Currently processing 1: TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) at initializeCustomParams (/var/polyglot/pg3/ns/000db95d9b48_10/st-sonos.js:165:35) at Interface.<anonymous> (/var/polyglot/pg3/ns/000db95d9b48_10/st-sonos.js:78:3) at Interface.emit (node:events:513:28) at Interface._onMessageQueued (/var/polyglot/pg3/ns/000db95d9b48_10/node_modules/polyinterface-v3/lib/Interface.js:416:16) at dataq.process (/var/polyglot/pg3/ns/000db95d9b48_10/node_modules/polyinterface-v3/lib/Queue.js:28:26) at /var/polyglot/pg3/ns/000db95d9b48_10/node_modules/polyinterface-v3/lib/Queue.js:37:16 at process.processTicksAndRejections (node:internal/process/task_queues:77:11) 2023-12-28 11:14:38 error: POLY: Node db87bfe not found 2023-12-28 11:14:38 error: POLY: Node 8b16614 not found 2023-12-28 11:14:39 error: POLY: Node c0ea726 not found 2023-12-28 11:14:39 error: POLY: Node c0ea726 not found 2023-12-28 11:14:39 error: POLY: Node afa4fca not found 2023-12-28 11:14:39 error: POLY: Node afa4fca not found 2023-12-28 11:14:39 error: POLY: Node afa563a not found 2023-12-28 11:14:39 error: POLY: Node afa563a not found 2023-12-28 11:14:39 error: POLY: Node c0ea6ed not found 2023-12-28 11:14:39 error: POLY: Node c0ea6ed not found 2023-12-28 11:14:39 error: POLY: Node 8b16614 not found 2023-12-28 11:14:39 error: POLY: Node 8b16614 not found 2023-12-28 11:14:39 error: POLY: Node c0ea6ed not found 2023-12-28 11:14:39 error: POLY: Node c0ea6ed not found 2023-12-28 11:14:39 error: POLY: Node a0916de not found 2023-12-28 11:14:39 error: POLY: Node a0916de not found 2023-12-28 11:14:39 error: POLY: Node c0ea726 not found 2023-12-28 11:14:39 error: POLY: Node c0ea726 not found 2023-12-28 11:14:39 error: POLY: Node 8041df3 not found 2023-12-28 11:14:39 error: POLY: Node 8041df3 not found 2023-12-28 11:14:39 error: POLY: Node 822d6a0 not found 2023-12-28 11:14:39 error: POLY: Node 822d6a0 not found 2023-12-28 11:14:39 error: POLY: Node afa4fca not found 2023-12-28 11:14:39 error: POLY: Node afa4fca not found 2023-12-28 11:14:39 error: POLY: Node afa563a not found 2023-12-28 11:14:39 error: POLY: Node afa563a not found 2023-12-28 11:14:39 error: POLY: Node 8041df3 not found 2023-12-28 11:14:39 error: POLY: Node 8041df3 not found 2023-12-28 11:14:39 error: POLY: Node a0916de not found 2023-12-28 11:14:39 error: POLY: Node a0916de not found 2023-12-28 11:14:39 error: POLY: Node db87bfe not found 2023-12-28 11:14:39 error: POLY: Node db87bfe not found 2023-12-28 11:14:42 error: NS: undefined 2023-12-28 11:14:43 error: NS: undefined 2023-12-28 11:14:47 error: NS: undefined 2023-12-28 11:14:48 error: NS: undefined 2023-12-28 11:14:49 error: NS: undefined 2023-12-28 11:14:50 error: NS: undefined 2023-12-28 11:14:55 error: NS: undefined 2023-12-28 11:14:57 error: NS: undefined 2023-12-28 11:14:59 error: NS: undefined
-
Demo worked fine, purchased version does not
Used the demo and it worked fine for six days. Purchased NS and now does not discover any of the sonos players. Have discovered, deleted, reinstalled, booted Polisy multiple times to no avail. Have attached log, any thoughts? ST-Sonos_12-28-2023_115350-AM.zip
-
Can no longer delete old scenes within Alexa.
Thank you so much! Solution works perfectly!
-
Does Nodeserver Support LG CX TV?
No luck on my side...thanks for the guidance
-
Does Nodeserver Support LG CX TV?
Cant seem to get this to work for me. Everything is installed but its not able to control the TV. My settings are attached, Broadcast Address is my SubNet AVRemote_12-21-2023_24336-PM.zip
-
Can no longer delete old scenes within Alexa.
Benoit Mercier wrote: ‘Amazon support would probably be in a better position to help.’ Looks like we are stuck……
-
Can no longer delete old scenes within Alexa.
I have the same problem! Scene tab in Alexa app is gone.
-
How to join two or more Sonos (group) together with scene
I would like a scene where if I tell alexa to turn on 'entertainment' it would group the family room and living room sonos speakers together. Off would ungroup them. Would work like party mode. Sonos has group functionality but the nodeserver currently doesnt seem to support it. Group functionality via the nodeserver would allow for this functionality.
-
How to join two or more Sonos (group) together with scene
I would like to be able to join two sonos units together via a scene. One sonos would always be the master and the other unit the slave. Is this possible? I currently have groups created in the sonos app accomplishing this and would like to be able to execute the same via a scene which would be executed by Alexa.
-
Open Close vs On Off Amazon Command
Guess I should have been more specific, the on/off alexa command runs a scene which turns on/off a keypadlinc dimmer 5 button. A program monitors the status of the button on or off and then sets relay 1 on for open or relay 2 on for close. Im thinking i made this too difficult and should just create separate scenes for on and off and then associate open and close to each in the portal. Thanks for helping me think this through.
-
Open Close vs On Off Amazon Command
I have relays which control curtain motors. Currently issue command 'Alexa turn on yard' and the curtains open. Is there a way to setup the portal or Polisy to get Alexa to recognize the command open vs on?
-
I am open to the use of my code!
@Michel Kohanim Is there a cost to become a developer? Quite generous of Steven!
-
Admin Console Text Size
OMG so much better, Thank you!
-
Admin Console Text Size
It would be great if there was, or is there, a way to make the fonts larger in the Admin Console. Thoughts?
-
What am I doing wrong with this subject variable?
Hi Jimbo, Im out of town for the next two weeks. I will send upon my return.
-
What am I doing wrong with this subject variable?
Dont suppose the node definition is too long? Wonder if anyone else has come across this using ambient weather. Thanks again for taking a look at the issue.
-
What am I doing wrong with this subject variable?
Looks like file is too big when zipped for the forum
-
What am I doing wrong with this subject variable?
192.168.4.6_8443_rest_nodes.zip192.168.4.6_8443_rest_nodes.zipReinstalled nodes server, no change. Attached rest/nodes in case you see something I missed.
-
What am I doing wrong with this subject variable?
-
What am I doing wrong with this subject variable?
As far as I can tell the ambient weather nodes do not show up with the above https
-
What am I doing wrong with this subject variable?
Unfortunately, same result when typed in manually.
- What am I doing wrong with this subject variable?