bpwwer

re-install to get version 1.0.2. I added the missing module so it should start properly now and show the add printer button at the bottom

Doesn't say restricted, so I tried again, and this time it worked without any errors. Go figure.

You don't have the configuration correct. The Bambulab plug-in uses the custom typed parameters, not the custom parameters. If you scroll down below the custom parameters, you see the custom typed parameters. Use the Add button to add a new printer. This is what mine looks like for my two printers

fixed

I'm getting the same errors with my API key. I don't run the WeatherBit plug-in normaly and only start it for debugging purposes and I got the error with the first query I made. I don't think it's a problem of exceeded limits. Maybe they are simply trying to force people off the free plan.

I'm not sure how the app works, but when you click On or Off in the console, IoX sends the command to the plug-in and plug-in process and sends the command to the device. If the device changes state, the plug-in will see that change in state and pass that state change back to the console. Since the console isn't reflecting the state change, either the device is not sending the updated state to the plug-in or the console is not seeing the state change when the plug-in sends it. A couple of things you can check. In PG3, if you look at the nodes tab, it will show what the plug-in thinks the state of each node value is. if the ST value is getting set correctly, then the device is sending the update and the plug-in is seeing it. The PG3 log should show lines for all the messages going back and forth to the IoX. So again, when you change the state on or off, you should see a line where PG3 makes a request to IoX with the new state. If that's failing, you also see those failures in the PG3 log. For the scene, it sounds like you may need to re-create the scene, link not found seems to imply a corrupt scene. I do have a MH bulb in a scene and it continues to work as expected.

You may have to re-install the plug-in.

admin console -> configuration -> install development packages

The error indicates that one of the python library modules that the plug-in depends on is missing. Since you recently switched to a new machine, I suspect that you need to install the dev packages on that machine to get the required modules installed.

Some do it already, but the how is not standardized so how it works for each plug-in is going to be different. In my case, I have a number of plug-ins that don't need any type of control interface so each node represents a device (say a light switch or networked bulb). For those types of plug-in's I'd have a new node that does nothing but report the interface status or add the interface status to each node. I don't find either design compelling, plus it would be a bit more than a minor change. Even with plug-ins that have a controller type node, there's no standardized way to report that. The logical choice would be to report it as the node's status, but that is typically used now to report the status plugin, not it external interface. You're probably thinking it's just a couple of plugins that need this, but there's something like 188 plugins the store and some of those are no longer being actively maintained. So it's a pretty major effort for everyone to do this. I know I have very little time right now to do major plug-in development, I'm struggling just to bugfix/updates when needed. I proposed something similar to what @Goose66 wrote above while we were doing PG3 development, but it would take a bit of effort to the develop the IoX side and other issues were a much higher priority. I agree that this would be the right direction, but with so many plugins having to be changed the existing methods would have to remain in place and the conversion could take quite a while. That's assuming UDI has the resources available to do the IoX side of the implementation.

This program worked for me. If $picoon is 0 And 'Caseta Test Devices / Test_Pico - Middle' is switched Button Pressed Then $picoon = 1 Set 'Office / Office:Ceiling Cans' On Else Set 'Office / Office:Ceiling Cans' Off $picoon = 0 It triggers on the middle button of a 3 button pico and toggles an Insteon controlled light on/off with each button press. It simply uses a variable to keep track of the current state instead of trying to do that with programs. The variable can just be an integer variable since we're not triggering on the variable. As an aside - This only works with a Pico remote. Caseta switches don't send button press events. I have a case where I want a Caseta dimmer switch to also control an Insteon lamp. To do that I have to trigger on the dimmer switch status and then send the commands to the Insteon device. It's not ideal as there's a pretty large delay between the button press and status change.

I don't know for sure. The plug-in uses the rain value in field 12 for rain (both local and remote) and field 19 for nearcast rain. That implies that they should be separate and you should not be seeing nearcast values at all if you're using just local. But, it is certainly possible that they update field 12 with nearcast values at some point.

@Techman Looks like the disconnect and re-connect was caused by the MQTT broker. It disconnected from the plug-in and the plug-in then properly re-connected. There is a nearcast node that is created when you configure the plug-in to get it's data from the server vs. from the local hub. WeatherFlow only provides the nearcast data via the server feed. That data is supposedly separate fields in the data stream, but I can't control what they push out in the feed. Since historical rain data is only available from the server, when the plug-in starts, it makes queries to get the historical data and populate those values. Once it's running, it pulls the current rain data from the feed and updates the historical values as appropriate.

That is interesting. I bet whatever micro-controller that is in the remote can't do floating point so they had to approximate the conversion formula.

RE: temperature range/step. That makes sense. It looks like internally it works with Celsius and just converts & rounds for Fahrenheit values. We could just hard code the editor range to match, but as we discussed above, that may not work for other mini-splits. I was looking the Home Assistant code and they pull the range from the device capabilities and use that. That's what I'd like to do here too. The only issue I see is that the editor profile is global so what happens if someone has two different units with two different ranges.