-
Posts
4634 -
Joined
-
Last visited
Everything posted by Jimbo.Automates
-
Any errors in the log? Did you enable XMPP as desc in the readme? What do your configuration parameters look like? If still necessary PM me the log package. Sent from my Pixel 6 Pro using Tapatalk
-
Yes it was, but currently broken due to a new feature added recently. He is working on a fix. Sent from my Pixel 6 Pro using Tapatalk
- 1 reply
-
- 1
-
-
Great, glad you figured it out! Sent from my Pixel 6 Pro using Tapatalk
-
Sorry, currently it doesn't. I meant everything that works with the original strip will work with this one. Adding zone support will take a while. Sent from my Pixel 6 Pro using Tapatalk
-
Polyglot 3 Flume Water Node server 3.0.11
Jimbo.Automates replied to Jimbo.Automates's topic in FlumeWater
FlumeWater Node server 3.0.11 released, see the Release Notes Thanks to @stevehoyt for reporting issues and continued monitoring of the connections to the occasionally unstable Flume servers are becoming more robust. -
Great! Everything should work as expected because it's the exact same code that handles the original light strip which I have. But it's possible that I haven't tested everything. Sent from my Pixel 6 Pro using Tapatalk
-
Current Power used does not match device state
Jimbo.Automates replied to stevehoyt's topic in Kasa (TP-Link)
Fixed in 3.0.10 -
Thanks, the PM showed the issue. That device doesn't have color temperature control. Issue fixed in 3.1.10.
-
Correct. It allows you to control devices on the ISY with some other devices that support Hue, like a Harmony remote. After installing you should see a Huge Emulator Controller node in the admin console? If not please do a download log package from the PG3 UI and PM that to me. Sent from my Pixel 6 Pro using Tapatalk
-
Please make sure logging is in Debug and restart the NS then let it run for a couple minutes and turn it on and off for the AC. Then download log package in the PG UI and PM that to me. I'm out of town so won't be able to look until this weekend. Sent from my Pixel 6 Pro using Tapatalk
-
KeyError precip_accum_local_yesterday
Jimbo.Automates replied to Jimbo.Automates's topic in WeatherFlow
Still same error today as above @bpwwer -
KeyError precip_accum_local_yesterday
Jimbo.Automates replied to Jimbo.Automates's topic in WeatherFlow
Haha, yes, can wait till tomorrow unless you want to try again: 2022-04-09 15:41:43,333 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherFlow(controller) [None] 2022-04-09 15:41:45,447 Thread-1 udi_interface ERROR weatherflow:get_monthly_rain: Failed to get rain for month 1 2022-04-09 15:41:45,869 Thread-1 udi_interface ERROR weatherflow:get_monthly_rain: Failed to get rain for month 2 2022-04-09 15:41:46,269 Thread-1 udi_interface ERROR weatherflow:get_monthly_rain: Failed to get rain for month 3 2022-04-09 15:41:46,678 Thread-1 udi_interface.interface WARNING interface:db_getNodeDrivers: 194486 not found in database. 2022-04-09 15:41:46,680 Thread-1 udi_interface ERROR udi_interface:write: Exception in thread 2022-04-09 15:41:46,681 Thread-1 udi_interface ERROR udi_interface:write: Thread-1 2022-04-09 15:41:46,682 Thread-1 udi_interface ERROR udi_interface:write: : 2022-04-09 15:41:46,682 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-04-09 15:41:46,683 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-04-09 15:41:46,688 Thread-1 udi_interface ERROR udi_interface:write: self.run() 2022-04-09 15:41:46,689 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-04-09 15:41:46,692 Thread-1 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-04-09 15:41:46,693 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 115, in parameterHandler 2022-04-09 15:41:46,695 Thread-1 udi_interface ERROR udi_interface:write: self.discover(stationList) 2022-04-09 15:41:46,696 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 473, in discover 2022-04-09 15:41:46,699 Thread-1 udi_interface ERROR udi_interface:write: self.create_device_node(station['id'], device, info['units'], info['elevation']) 2022-04-09 15:41:46,699 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 299, in create_device_node 2022-04-09 15:41:46,702 Thread-1 udi_interface ERROR udi_interface:write: node.rd = self.rainList[device['device_id']] 2022-04-09 15:41:46,703 Thread-1 udi_interface ERROR udi_interface:write: KeyError 2022-04-09 15:41:46,703 Thread-1 udi_interface ERROR udi_interface:write: : 2022-04-09 15:41:46,704 Thread-1 udi_interface ERROR udi_interface:write: 194486 -
Upgraded IoP to 5.4.3 and now cannot find Polisy.
Jimbo.Automates replied to tlightne's topic in IoX Support
Can you reach it in a web browser with: http://ip_addr:8080/rest/nodes Also try to open a terminal and ssh to it. -
Hey @bpwwer, I migrated from my original weatherflow to tempest with a new hub, swapped the station id in PG3 config and restarted and it crashes with: 2022-04-09 12:03:01,238 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:bf:fc_9 - MID: 1 Result: 0 2022-04-09 12:03:01,256 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-04-09 12:03:04,211 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherFlow(controller) [None] 2022-04-09 12:03:05,418 Thread-1 udi_interface ERROR udi_interface:write: Exception in thread 2022-04-09 12:03:05,420 Thread-1 udi_interface ERROR udi_interface:write: Thread-1 2022-04-09 12:03:05,420 Thread-1 udi_interface ERROR udi_interface:write: : 2022-04-09 12:03:05,421 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-04-09 12:03:05,422 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-04-09 12:03:05,426 Thread-1 udi_interface ERROR udi_interface:write: self.run() 2022-04-09 12:03:05,426 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-04-09 12:03:05,430 Thread-1 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-04-09 12:03:05,431 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 115, in parameterHandler 2022-04-09 12:03:05,432 Thread-1 udi_interface ERROR udi_interface:write: self.discover(stationList) 2022-04-09 12:03:05,433 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 462, in discover 2022-04-09 12:03:05,435 Thread-1 udi_interface ERROR udi_interface:write: info = self.query_station(station['id']) 2022-04-09 12:03:05,436 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 190, in query_station 2022-04-09 12:03:05,438 Thread-1 udi_interface ERROR udi_interface:write: info['units'] = self.query_station_uom(station, rain_id, rain_type) 2022-04-09 12:03:05,438 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 234, in query_station_uom 2022-04-09 12:03:05,440 Thread-1 udi_interface ERROR udi_interface:write: p_rain = jdata['obs'][0]['precip_accum_local_yesterday'] 2022-04-09 12:03:05,441 Thread-1 udi_interface ERROR udi_interface:write: KeyError 2022-04-09 12:03:05,442 Thread-1 udi_interface ERROR udi_interface:write: : 2022-04-09 12:03:05,442 Thread-1 udi_interface ERROR udi_interface:write: 'precip_accum_local_yesterday'
-
PG3 IFTTT Webooks Node server 3.0.3
Jimbo.Automates replied to Jimbo.Automates's topic in IFTTT-Webhooks
Haha, yeah IFTTT is dumb, but when that's the only choice, at least it's there [emoji16] Sent from my Pixel 6 Pro using Tapatalk -
PG3 IFTTT Webooks Node server 3.0.3
Jimbo.Automates replied to Jimbo.Automates's topic in IFTTT-Webhooks
No, you create 2 applets, but in PG you create one node and set the applet for in and off -
PG3 IFTTT Webooks Node server 3.0.3
Jimbo.Automates replied to Jimbo.Automates's topic in IFTTT-Webhooks
Also, while testing you can turn on the option in IFTTT to send you a notification when the automation is run, and watch the log in PG3 with debug level enabled. -
PG3 IFTTT Webooks Node server 3.0.3
Jimbo.Automates replied to Jimbo.Automates's topic in IFTTT-Webhooks
In the AC you can test the node by turning it "On", same with a program. Just make sure you close and re-open the AC after the node was added. BTW, don't you ever one to turn the device off? If so, I would create a node called BRSensibo then define an On and Off Event. -
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
There are 2 examples showing the usage, one is the "old" way setting them on the controller: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short and the other is the new way using one program line on the service node: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short-with-params You can put any ${sys.node.somenode.name} ${sys.node.somenode.driver} where the somenode is the node address and driver is the node driver that shoes the data you want as documented here https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables -
I'm the PG3 UI under the node server log page set logging to debug and restart, and PM me the log package. It makes no sense that nodes page is empty, you should at least see a controller after installing. Sent from my Pixel 6 Pro using Tapatalk
- 1 reply
-
- 2
-
-
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
Thanks all. @asbril I added a documentation example similar to what I described to you above https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short-with-params -
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
I just made a minor change and released 3.3.3, I went to PG3 on my production machine, clicked restart and once it connected the version updated to 3.3.3 as expected. Bob also was unable to see the issue on his machine this morning. So anyone still having the issue with an update not showing properly, please describe in detail what you did and what you did not see and start a new thread so @bpwwer can help. -
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
You have mixed together 2 different methods of sending a notification. The How it Works describes these as "messages" and "notify nodes", they are used individually, not together. The first line in your then sets the "message" to 'Bad Weather', then next three lines set params on a 'notify node' then the last line sends a message on the pushover service. The best way to do this now is to create a Custom Content in the Admin Console which can contain the drivers from the NOAA Weather node to tell you the Alert and Wind speed in the message. Then the program will just have one line in the 'Then' section. -
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
Please stop saying the new version does not show in the PG3 UI after restarting. I've already said: The version info is stored in PG3 database so need help from @bpwwer so I'm sure he will look into when he has time. Sent from my Pixel 6 Pro using Tapatalk -
PG3 Notification Node server 3.3.4
Jimbo.Automates replied to Jimbo.Automates's topic in Notification
Thanks for sending the log, pushed 3.3.2 to fix the issue which happens if you add a Telegram node, but don't give it a name. You should delete it in the config, but at least now the NS won't crash when it happens.