Panda88

Is there a way to only select one of multiple devices registered on the account. I have devices in different houses and only need data from one of the locations Are there hidden parameters to hide some of the devices

Is there a way to limit the number of nodes - i.e. I only use 8 sensors - but it defaults to 16

got it

Hi Installed the trial version - I have 2 AirThings sensors so I am supposed to set the poll rate to more than 60 sec - however when I do so after restart it reverts to 60 sec and complains - is this a bug Also, I noticed the particle count is not reported 2025-02-02 18:21:09.641 Thread-2173 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm1=0.0 2025-02-02 18:21:09.641 Thread-2173 (handler_poll) udi_interface WARNING Sensor:query: Unknown param pm25=0.0

Can you send a log with debug enabled - That way I can see if an error occur preventing the update to happen Are you running local or cloud?

I did not do it, but I can give it a try - was trying to keep system "clean"

Hi This is a heads up - Tesla is planning to charge for access to the API. We are working on an option for streaming changes to the car (vs. polling) and this should be lower cost, but is still work in progress. Note this only works for newer cars + 2021 Suggest to lower the update rate to the case and only wake it if it makes sense When developing the streaming option - are there fields of interest that should be added (I'll see if it is available) - there is a lot more data available

hi I get the following message after installing with a VUE3 device 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: import boto3 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2025-01-25 22:22:54.449 MainThread udi_interface ERROR udi_interface:write: : 2025-01-25 22:22:54.450 MainThread udi_interface ERROR udi_interface:write: No module named 'boto3' any ideas?

I think it is possble to dim Yolink from an Inseton switch, but operation is very differnt - Insteon sends a start-dim and stop-dim - I can decrease the level in a loop but it will be difficult matching a rate of the insteon - If dimming using the yolink switch it only reports the new level (after user stops dimming) - so I must wait until a level is selected before I can send the dim command to Insteon and again the DIM level I do not know how to send to Insteon (only a command to start/stop dimming) - If I know the rate maybe I can estimate the time to send the DIM commands). I think a program approach is easier If it needs to work, we need to specify a DIM rate as a minimum

found the bug - I think the doorbell will update if you press it It is difficult to test as the LockV2 reports data different compared to the old lock (which I have) Is it ok if I wait to release a new version - working on getting the dimmer to work in scenes - should be a few days (I hope)

Can you send a log again?

It can take a few hours from what I know

Hi Just installed - I have 2 sensors (in different locations) I try to set the short Poll to more than 60 (say 120) - but when I restart the node it resets to 60 and stops Also - note there is a warning that PM1 ad PM2.5 is missing 2025-01-18 17:33:58.869 Thread-26 (handler_start) udi_interface WARNING Sensor:query: Unknown param pm1=1.0 2025-01-18 17:33:58.869 Thread-26 (handler_start) udi_interface WARNING Sensor:query: Unknown param pm25=1.0

changed release to 1.3.23

It has to go through Amazon cloud before changes occur when using a zip file.

It may take a little while to propagate There is an issue with the zip file so i moved to different approach

Try to install once more. There was an issue with the install file

released 1.3.22 - give it a try

Does the new lock include a doorbell - if so can you try to press it and send me a log

can you include the latest log - I'll try to fix the battery - should be easy - probably just reported differently

can you try 1.3.16

Can you try 1.3.15 I will only pick switches and locks - The code somehow gets the online status wrong, but I cannot figure out why - added some more debug info

Can you try 1.3.14

Hi Does the node handle more than 1 VUE device? E.g. can I have a VUE in my main panel and a sub panel?

thanks it will not work yet as the syntax is not correct yet I'll get to it early next week