Xathros

Thanks all. Michel remoted in and helped me out today. It was mostly my Kasa node server. I have 7 polys running and had all of the logs set to debug. Kasa with 50 nodes is *VERY* chatty and filled the 10G allotment for the polyglot filesystem. Between Kasa and the other 6 polys, it ran out of space with less than 2 weeks of logs! With no free space, pg3 would not start. It appears to me that in the current version, logs are not being compressed daily if at all. We deleted all the logs and I have set my log levels to error instead of debug. I think there will be some changes coming to prevent this sort of thing from happening again. -Xathros

Hello everyone, pg3 is down on my eISY. After some research, I have determined that pg3 is not starting because it has exceeded its disk quota. Looks like the database has ballooned and I've reached the 10G limit. Pretty sure this is my fault for having the log level set to debug on my Kasa node server. I didn't realize that the log data was stored in the database. My bad. How to clean up the log data, compact the DB and get back online? Any assistance is greatly appreciated. -Xathros

Hello all- All working now for me too. I did need to enable SNI on all of my web hook resources which is new but now they work after IFTTT's patch rollout. Thanks all for the community support! -Xathros

Hello guags99, My first failure was: Tue 2021/11/30 04:23:52 PM System -170001 [TCP-Conn] -256/-140002, Net Module Rule: 2 Also CST and was the first time a maker event was called since the week before as we were away and the events would not have fired while we were gone. I saw mention of 11/29 earlier in this thread as well so I suspect your right. -Xathros

Found the dashboard - here are my client settings:

Hello all, I have tested with SNI checked and unchecked. Timeout set to 20,000 - no noticeable difference in time to failure from timeout of 1000. Where do I find the Client settings to check (or uncheck) the Verify box? Seems like something changed outside the scope of the ISY for this to all of a sudden be affecting so many clients. Probably something at the IFTTT host side but that'd just a guess on my part. Thanks in advance for any guidance. -Xathros

Hello all, I'm seeing the same thing with all of my outbound maker network resources. Get, Post, URL Encoded or not, SNI or not, they all fail. Every failure results in the same error in my error log - example follows: Wed 2021/12/01 04:45:49 PM System -170001 <s:Envelope><s:Body><u:TestNetResource xmlns:u= Wed 2021/12/01 04:45:49 PM System -170001 [TCP-Conn] -256/-140002, Net Module Rule: 5 I can call the web hook just fine from a browser on my computer. Any insight would be appreciated. -Xathros

Me Too! Spent about an hour troubleshooting. Should have come here first... Thanks all!

All, Thanks to everyone that jumped in here to help. I just completed a remote support session with UDI. Looks like the database had become corrupted likely due to a power failure. They very quickly had it repaired and I'm back up and running with no lost config or anything. As always, the support offered by UDI is unmatched by anyone! -Xathros

Ugh. Lets see if my second attempt to open a ticket was a success... Thanks. -Xath

Hi Bumbershoot, My polys are there with proper ownership. When I run top, I see one of them running - the KASA NodeServer. Must not be fully running though as the nodes are not making it through to the ISY. I have already submitted a ticket with UDI. I'll follow up here as things progress. Thanks! -Xath

Sure did. Same result as with the user I had configured.

Hello all, After a recent power outage at my lake house, I am no longer able to log into my Polisy via the web interface. I noticed I had no data from my node servers. I attempted to log into polisy and can't gat past the username/password page. No error or any other kind of feedback when submitting credentials. I used my PDU to remotely reboot the polisy and get the same result. I am able to login via SSH but only with the default reds admin/admin. The user I had created for myself no longer appears to exist. I followed the little bit if guidance I could find in the documentation to update and reboot from the CLI only to find everything up to date and no change after reboot. Any/all help here is appreciated. Thanks in advance. -Xathros

Nailed it! All better now. -Xathros

Thanks. I tried that and still showing the old FW version. -Xathros

Hello All, After a bit of playing with the forum search function I have decided this was the most appropriate place to ask my question. I have an ISY-994 Pro with Wave that was running 5.0.16C as I had the older Wave 300 module and couldn't't upgrade beyond that. Yesterday I received my Wave 500 module and installed. After getting my Wave devices re-registered on the new module I upgraded the ISY firmware to 5.2.0. (Screenshot below) I recently purchased a Polisy Pro and have had it working nicely with the ISY with 4 node servers running on it. After upgrading the ISY to 5.2.0, the Polisy still shows the ISY at version 5.0.16C. (Screenshot below) I have rebooted both the ISY and the Polisy. How do I get the Polisy to recognize the newer ISY firmware version? There doesn't seem to be any ill effect. All node servers are working as expected. Just mostly curious about this discrepancy. Thanks. -Xathros

You need to adjust both the Device On Level (Local) and the Device's On Level within the scene. The terminology is a bit different between 4.x and 5.x firmware branches. What firmware are you on? I don't think you need the scene at all given the description. Just modify the device's on level with your program. Hope this helps. -Xathros

Cool. I'll let you know after I get it up and running. I believe the resolution will be 800x480. Thinking either a larger number of buttons or a split screen with buttons on half and info (Clock / weather / custom status info) on the other half would be good. Dimming isn't important on this one as this will be a desk based unit. For the bedroom, I will probably go with a 3.5" screen like yours. That will be round 2. Does this depend on the Raspbian GUI or will this run on a CLI only setup? -Xathros

Well, I just ordered another Pi3 with a 7" capacitive touchscreen and case. Hoping I can make this all work on a 7" screen when my parts arrive. I enjoyed reading through this thread again today and look forward to getting this up and going on my ISY. Has anyone tried this with a 5.X ISY yet? Are there settings that allow for landscape vs portrait display? -Xathros

I don't believe this is correct. I have been able to set a device's local on-level to 0 to prevent the device from turning on with a single on tap. A fast on will override this and go directly to 100% and holding the on paddle will ramp up at the specified locally applied ramp rate but a single tap of the on paddle will go to the locally applied on-level. -Xathros

For the devices in the scene, you can adjust 2 on-levels. On of them is the Scene On-Level which affects what happens when the scene is commanded on by any controller, the other is the Device's On-Level (Applied Locally) which controls how the device responds to it's own paddle when tapped. You will need to set both to 0 for the device in question. Select the scene, set the on-level for the device, then select the device and set the on-level there as well. Hope this helps. -Xathros

With the exception of the period of time between the ISY booting and the first signal received from the MS during which the ISY will show NO status for the MS. -Xathros

Another question would be: Is the ISY aware that the light is on? Check the status of the light in the admin console to see what the ISY thinks. If the ISY is unaware of the state change of the bulb, there may be other things affecting the bulb. I on occasion have devices that will start responding to other devices or scenes due to what I believe is a corrupted link table on the affected device. A restore device issued from the ISY against the problem device usually fixes this. I too think a review of the programs is in order. Hope this helps. -Xathros

It does not matter. The ports are per IP address and the devices should have different addresses. Sounds mode like the ISY is being bogged down with lots of traffic at times. -Xathros

Larry, delete your the ac from your desktop and re download it from the 5.0.10 announcement post. Sent from my iPhone using Tapatalk