jkosharek

Last night my UD Mobile was updated to 1.1.35 and a few things that are broken. The scaling and favorites jumping around is almost completely fixed, which is great but... 1. Text scaling went to tiny with no way to configure it, it's like the UD Mobile app is no longer honoring the device scaling setting. It's almost unreadable. 2. I have variables configured for status on a number of devices, programs, and timers. Since this update they are no longer being read or displayed in real time. I have the setting to request state and integer values when opening and that is still working. If I change from the page and go back the variable updates. If I open the variable directly it updates in real time. 3. I found that one of my pages that is 3 wide and I have a button that is 2 wide, most of the other buttons that are 1 wide will not go next to it. I tried specifying the button span manually and default.

I am running NodeLink on a Debian VM and have CAI WebControl, Brultech GreenEye Monitor, and the ISY Data Logger configured with my EISY/IoX on 5.7.0 with no issues. I am looking to get the Brultech GreenEye Monitors in to a PG3x Node, anyone know someone with the skills?

Any thought in to adding a working status for if the device if offline?

Shouldn't be an issue, I am monitoring generator start battery voltage on A0 and will add some relays and temp sensors.

Support was able to resolve the MQTT Non-Prod install error on the Node install, it now prompts for a slot to install it.

Support was able to resolve this error on the Node install, it now prompts for a slot to install it.

On an eISY PG3x 3.2.14 IoX 5.7.0 Thank you

@xKing or @TriLife Trying to install the MQTT On the Non-Prod Store on my EISY/PG3x and getting an error Any help on getting this installed? I am trying to setup a ESP8266 Board with tasmota for battery monitoring like @EWhite setup and had this node server tweaked.

@TriLife Trying to install MQTT from the non-prod store on my EISY/PG3x for the same exact setup as @EWhite. I switch to the non-prod store, select install, then purchase, then get this error: Tried the instructions on https://github.com/Trilife/udi-mqtt-pg3x which fail at the first command: cd: /home/admin/.polyglot/nodeservers: No such file or directory How do I get this installed?

Looks like the ESP Board is sending data to EISY MQTT (10.11.12.9) My

I guess I am a little confused how this is supposed to work. I have an EISY running PG3x where Arduino_Mqtt is installed. The Arduino_Mqtt node has config options are the values for the ESP Board info or EISY: mqtt_server mqtt_port mqtt_user mqtt_password mqtt_topic and the ESP Board has these config options: Host Port Client User Password Topic Full Topic

The ESP was up and running, I deleted the node and reinstalled/configured and it didn't create the node. what should be in mqtt_user and mqtt_password?

Where is the discover done? The Arduino_Mqtt node doesn't have discover option and Arduino_Mqtt node didn't create a parent node in the admin console which would normally have a discover button.

Ok, that was wrong on my setup. I thought the mqtt_server was the SP8266 Board. The SP8266 Board seems to be connected to the Arduino_Mqtt now but it didn't create node(s) under 'Nodes' in PG3x nor in the Admin Console. I assume it should?

@kevin Trying to configure this Node to connect to a Mini ESP8266 Board similar to what @EWhite did for the chicken coupe. I have the device and the node configured but am getting this in the log, any ideas: 2023-11-06 19:04:17,805 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9025fc4_14/main.py", line 625, in <module> Controller(polyglot, 'controller', 'controller', 'Arduino MQTT') File "/var/polyglot/pg3/ns/0021b9025fc4_14/main.py", line 91, in __init__ self.mqttc.connect(self.mqtt_server, self.mqtt_port, 60) File "/var/polyglot/pg3/ns/0021b9025fc4_14/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 914, in connect return self.reconnect() File "/var/polyglot/pg3/ns/0021b9025fc4_14/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1044, in reconnect sock = self._create_socket_connection() File "/var/polyglot/pg3/ns/0021b9025fc4_14/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source) File "/usr/local/lib/python3.9/socket.py", line 844, in create_connection raise err File "/usr/local/lib/python3.9/socket.py", line 832, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 61] Connection refused

ratgdo device connects to wifi and the node server would connect to it's IP

My light has a motion sensor on it, but doesn't look like it's in the list you showed. I suppose if the Node Light state could be a controller in my garage light scene, that would work.

I didn't have light or motion in the MyQ node, which I believe was a limitation of the API. I would love to see control or at least status of the light, motion, lock, and obstruction sensors.

Didn't seem to work without a delay in between the select and play, like the EISY/IoX sends the commands so fast the Speaker Hub doesn't select the message in time. But after reading the throttling YoLink is doing, it could have been that. I just took the wait out and it seems to be working ok now.

I the program for Play you only get this That is why I am having to select the message, wait, then play: But if the select message is local, then it doesn't matter from a call count, other than the delay being there. Overall the Node seems to operate very well. Nice work!

That would be fire.

So if I am turning on a relay or announcing a message over the Speaker Hub, that counts. To play a message on the Speaker Hub I have a program that selects the message, waits 2 seconds and then plays message. Thats 2 calls, is there a better way?

I bought some YoLink stuff to play with, my first impressions is, it will work and is very responsive. But if the ratgdo v2.5 gives me access to control or at least view other properties of the opener system, like the motion, light, and other sensors that will be where I end up. YoLink is interesting but they are restricting API calls and putting devices offline. I am running into that with some testing I am doing with the Speaker Hub and open/close sensor I put in the mailbox. So, I am not sure I want to hitch my wagon to another system out of my control.

I plan to use this device to leverage the battery backup in the opener. https://www.amazon.com/Converter-DROK-Regulator-Inverter-Transformer/dp/B01NALDSJ0/ref=sr_1_4

Yeah, that does sound promising. I also just ordered one, I could assist in testing if needed.