bpwwer

PG3 doesn't use a server.json file, that was for PG3 node servers. The information that was present in the server.json is now stored in the node server store record for the node server. Again, please read the documentation on creating plugins (node servers) https://developer.isy.io/docs/getstarted/ Most of the documentation is also available from the PG3 developers menu/

Ok, version 3.0.31 has been published to the store with the fix. It should work correctly now.

@ldb I'm not sure what you mean by "do not reset daily". There are only two fields that should reset daily; the daily rainfall and yesterday's rainfall. I do see a bug that looks like it would always set yesterday's rainfall to zero. Is that what you mean? I don't use nearcast data so I don't pay attention to what's there.

It does do something, there's just nothing visible that happens when you press it. It sends the plug-in's profile files to the IoX. It's the same thing that happens if you call the udi_interface function updateProfile() from within your plug-in.

https://developer.isy.io/docs/getstarted/

You're waiting for me. I bought a couple of the RGB Led bulbs and I think I have those working correctly. I need to apply some of the changes for the dimmers (and switch, I think). Other projects have interfered so I haven't had time to finish up and release it.

That makes sense. I had forgotten that it used the controller ID as part of the zone node addresses. Using multiple copies of the plug-in in different slots should have worked. Since all the nodes are prefixed with the slot number, there's no way they can be duplicated. Also plug-ins are restricted to only working with nodes prefixed with their slot numbers, they can't do anything to node created by plug-ins in any other slot. The other option you have is to change the controller ID's so they are unique. Then one copy of the plug-in should be able to manage all three.

Possibly. The plug-in is designed to support multiple controllers, just not when they all have the same IP address. If they are chained (Russound term), one controller acts as the master so to the plug-in, it would look like 1 controller with 18 zones.

Actually, it doesn't need the open '('. I've been doing a lot of programming lately in a different language that does require '()' in if statements. I don't have any Sensibo devices so I can't really test the changes. Version 2.0.8 with the fix was published to the store.

Do they all have the same IP address? The node address is created using the last part of the IP address so if they all have the same IP address, each new CAM/CAV you add will replace the previous one. The node addresses need to be unique and typically, the device IP address is. But if you're using a IP <-> serial box that has 1 IP address and different ports assigned to each serial port, that presents a problem. At this point, I don't have a solution.

Thanks for providing the feedback and solutions. That makes it easy to update. Version 2.0.7 is in the store and, if I made the changes correctly, should work for you now. The eisy/Polisy only accepts numbers for temperature values, there's no way to make that display a '-' or N/A.

Does this mean that it's showing all three controller nodes? If so, then it's probably configured properly. When the plug-in connects to a controller, it queries the controller for it's setup. The controller should return how many zones are configured and what those zones are named. If you're not seeing zones created for a controller, then that controller probably says it has no zones configured. Running the plug-in with debug level logging will provide a lot of details on what the plug-in is doing and what the controllers are sending back in response to queries.

Yes, the same way you added the first one. Install a second copy of the Caseta plug-in in an unused slot Set the IP address of the second hub in the plug-in configuration Press the black button on the hub to pair it when prompted by the plug-in

That's strange. I'm not able to reproduce any of that. After install, I get the "You need to set your API key" notice. I enter an API key (I don't have an Ambient system or account so I have to use someone else's key) The notice immediately disappears and the plug-in starts sending queries out. The plug-in does not have any code to send any other messages for PG3 to display. So I have no idea where the second box in #4 is coming from. The plug-in should be logging API key failures and if debug logging is enabled, it will show the URL it is using there. But there are no extra spaces in that URL. If you do re-install, please enable debug level logging before entering your API key and then download the log package (maybe even do a screen capture with both messages on the screen).

Well, that's one of my plug-ins and there shouldn't be anything that carries over from a plug-in restart. Next time it happens, download the log package and PM it to me.