bpwwer

Yeah, all my fault. Made what I thought was a simple change and didn't test it. Fixed in 2.0.10 which I just submitted to the store.

Ok, with multiple people seeing the same thing, it probably means that I screwed something up. I'll take a look and report back.

The plug-in log viewer can't show historical log entries. When you click on the log tab, it connect to the log file and then will start showing new entries as they are output to the log. If nothing is showing up, it could be because no new entries are being logged. In some cases, when the log tab isn't working, I've had to refresh/reload the log tab to get it working again.

Very rarely, or if PG3x crashes it can fail to kill running plug-ins. From your description it sounds like that's what has happened here. There is a copy of the Roomba plug-in running but PG3x thinks it has stopped that copy. Only one copy of a plug-in for a slot can be running so when you try to start a second copy, it can't and nothing happens (other than the message that it is already running). Depending on your comfort level with FreeBSD command line, you can either ssh in and kill the running copy or simply reboot the eisy/Polisy. Once that first copy is stopped/killed, you should be able to start it again from PG3x.

I don't know then, if it used to work, nothing has changed on the MH plug-in. Maybe try viewing what's happening when you press the keypad button using the diagnostics -> event view on admin console. That should show the incoming message from the keypad button and what the IOX sends out in response. If your system is busy doing a lot of stuff, it may be hard to pick those out of the view as it will also be showing all the other on-going activity.

bla I think it has something to do with the way IOX creates and handles scenes. An Insteon only scene programs the responders to respond to an Insteon broadcast message sent by the controller. In a mixed scene (Insteon + plug-in based device). That won't work because the plug-in based device (MH) doesn't use the Insteon protocol and can't respond to the broadcast message. IOX should know that the scene is a mixed device scene, but I don't think you can program a keypadlinc button to send anything but broadcast message. The keypadlinc will only send direct on/off commands for the main buttons. So that probably explains the behavior. When IOX tries to control the scene, it sends the proper command (may a broadcast) to control the Insteon devices and sends an ON command to control the MH device. So it all works as expected. But the keypadlinc only sends to broadcast command which controls the Insteon device but not MH device. The only workaround I can think of would be to supplement the scene with a program. If keypadlink button X is on, send on to MH device. This would probably be something you should submit to UDI as a ticket. They can then investigate if there's some way for IOX to handle this internally.

I'm seeing failures every few days where it seems like the device just stops responding. I'm connecting to the MQTT broker on the device itself, not remotely via the server. I haven't been able to investigate it yet, but it may just be badly designed hardware (well, probably the device firmware)

It appears that you don't have the updated roomba.py file. The failure is showing on line 42, which in the latest version is a blank line so very likely not a failure. The current version of roomba.py is 2.0.2, version 2.0.0i would have that failure on line 42

Never mind, that took about a minute to do so I just submitted version 2.0.9 to the store

Looks like that's another place that needs the workaround to enable unsafe renegotiation. When I tested, it didn't call that function, probably because the vacuum was already know to the plug-in. I'm gone for a few days so it'll probably be sometime next week that I can fix it.

I managed to find a couple of things and it seems to be working for me now. First, it looks like the newer OpenSSL liibs now being used on eisy/Polisy block the security methods Roomba uses and I wasn't able to get a connection to the Roomba. I found a workaround for that overrides the block and that allows it to connect and I was getting data from the Roomba. At some point the external library being used switch to an asyncio based library but plug-ins are not asyncio. This means you have to some modifications in the plug-in to properly call the asyncio based functions in the library. I had already make most of those changes. But there was one place I didn't have it right and it was hanging in the initialization code where it waits for the Roomba to send out the updates to get the full state of the Roomba. Once I fixed that, the node was created and I think it's working. However, there still could be places where I don't have proper code in there to access the asyncio functions. Version 2.0.8 should be in the store now.

Not really orphaned, just low priority and difficult to debug as I'm not the original author of the plug-in and it does depend on the external library for all the interaction with the Roomba. Since that external library was developed without any documentation or support from Roomba, it is also possible that Roomba has updated the firmware so that it no longer works. The external library hasn't been updated in about 4 years except for one minor change and I've added that one change and it didn't make any difference. I'll spend some more time and see if I can track down the issue.

PG2 didn't support any time of licensing/purchasing of node servers. That capability was one of the major features added by PG3. If you paid something for a PG2 node server, that would have been between you and the developer and any license would be incompatible with PG3's licensing scheme. However, I am not aware of any PG2 node servers that weren't free, PG2 had no way to restrict loading and running of node servers. While some PG2 node servers were ported to PG3 with only minor changes, it's not possible to run PG2 node servers on PG3. Even for those that were simply converted to run on PG3, you have to install the PG3 version. The initial migration process from PG2 to PG3, would look at the installed PG2 node server and attempt to pre-install the PG3 version, that only worked in very few cases.

This isn't a plug-in issue. The plug-in sends a map that links the numeric value to a string to IoX. IoX won't read this until it is restart (at least prior to version 6.0 it wouldn't). Until it reads this map file for the plug-in , it will only send out the numeric value as that's what the plug-in is sending to it. This mainly effects UD mobile. The admin console also reads these plug-in map files when it starts. This is way most instructions for installing plug-ins say to restart the admin console after installing the plug-in. How the new 6.0 release of IoX effects all of this, I'm not really sure.

I think you should have included this information along with a list of features that are not yet present in the eisy-ui in the release announcement. I'd also be interested in seeing a time line when each feature will be added (roughly, like maybe in each quarter of the year). About the only thing I see eisy-ui currently doing is replacing the PG3 main menu and showing nodes and programs. I'm not really convinced that the way eisy-ui shows nodes is actually an improvement over the way the admin console does. Also, I wouldn't classify this as beta software. Beta typically means feature complete although not all features may work correctly and there are certainly bugs. By your own admission, this is not feature complete. What's there tends to work pretty good. I like how the variables are displayed and modified. However, I was a bit shocked that I couldn't even look at programs. I am looking forward to seeing how this evolves, it does seem to be a good start.

At 12:24 after you turn the light off, the last message from the plug-in is "waiting for response from device". There aren't any error messages and it doesn't show that the response timed out so I really don't know what happened, it seems like the plug-in got stuck at that point but there's no information as to why. At 12:38, when you dim the device, it does dim, but the fact that it turned off first seems to be device behavior. All the plug-in sends in this case is a set level 99% command. It looks like setting the level of a dimmer (or at least that model of dimmer) causes the dimmer to turn off and then ramp up to the set level. I don't believe the bulbs have this behavior. Maybe check if there's a firmware update for the dimmers. After that it hit a bug in the plug-in and the plug-in crashed. I've fixed the bug. As I mentioned before, there are a lot of time outs waiting for a response from the device (or rather a response from the Meros broker service). That's going to cause some issues although most of the time, the plug-in doesn't really care and assumes the device was set based on any commands sent. It could effect polling so if the device is controlled via the app, the plug-in may not see those changes right away. I'm a bit hesitant to increase the timeout value, because when it's waiting for the response, the plug-in is basically pausing until it either gets the response or it times out.

This device is a dimmer switch, right? I have a note about dimmer switch behavior: So when setting a level on a dimmer, I first send the command to set the level then I send the command to turn the device on (in case it is off). It doesn't seem like that should be causing it to turn the device off unless the set level command does that automatically. Can you try the bright and dim commands? They should bump the luminance 1% up or down. This command will only send the command to set the level so I'm curious if this will cause the dimmer to turn off or simply set the level. It's possible that the various models of dimmers behave differently. I don't have any real documentation from Meros on how any of this works so all my info is coming from other projects on github. I did find the log entries where you send a OFF, ON, Level 40%, Level 100% but the log doesn't show anything that would indicate that the dimmer was set to 0% or off other than when the original OFF command was sent.

I see the disconnects in the log. The error is: Unexpected MQTT disconnect. Reason code: Unspecified error. So no real information about why. The MQTT connection is managed by a common interface library that is used by all the plug-ins so it's probably not something the plug-in is doing that's causing it. I also see quite a few "meross:send_to_broker: Timeout waiting for respsonse from device", which means the Meross broker isn't responding, at least not within 15 seconds. I could increase that, but 15 seconds seems like more than enough time for the broker to respond. I have not found that the connection to the Meross broker to be all that reliable. Does that log include you changing the level of the light? If so, do you know approximately what time you were doing that. The log is fairly long so searching through the whole thing looking for a level change is a bit more than I want to do right now.

I don't see anywhere in the plug-in code where it would send an off command before sending the level command. When you execute the command to set the level, it just sends the command to set that level to the device. I haven't tried doing any level changes from the plug-in, but I do have a bulb that is now part of a scene in one room of my house, which is why I made a few changes lately so I could get that working correctly.

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.