switch to on/off module throws errors

swapped out a dimmer module for an on/off module (insteon) and now the device throws this error whenever it's accessed, can't sort why, and i've re-linked a couple times and restarted, even upgraded to latest indigo and still error. how can i track down why/where this is having an issue? any thoughts appreciated. thx

Error device "living/fire lamp" state key brightnessLevel not defined

[jay (support)]

I wonder if you have something (an action or script) that's trying to set the brightness of that device. That would generate some weird errors.

thanks jay!

yes, i've searched through things and even deleted and reinserted the links to this device in powerlinc scenes etc. when the module changed the system did automatically switch almost all the entries to simply ON instead of a rate and brightness, but even after manually changing the links the error is still being thrown. so.. not sure. there's no other script that's being called as far as i can tell.

could this have anything to do with the checkbox 'retain persistent link even after relink' or whatever that one is...? that is checked by default on all entries.. might that have saved the params for the dimmer module even though it's no longer applicable..?

thanks

[jay (support)]

Ok, I think somewhere you are referencing the brightness of that device: perhaps in a Control Page? The error happens when Indigo tries to get the value of the brightnessLevel state, which no longer exists. So the most likely place for a device state to be referenced (outside of a script) is in a control page somewhere. Another alternative is if you have a Trigger defined that looks for that device's brightness state/property - that would also cause this kind of error. I think your next step is to right click on the device, and select Show Dependencies, which will show you a list of stuff that the device is used in. That should help narrow it down.

thanks jay.

yes, i checked dependencies, tried to clear up anything lingering; i did remove and re-add the popup controls setting on one page and now do not seem to have the error anymore, so thanks! *fingers crossed*

i do however have a bunch of this from time to time, when accessing controls on web pages.. anything to do, or just let it sort itself? is everything in the right place/folder, do i need to check? i don't perceive anything missing in my interactions, but the control popups are new so i'm not sure what it should look like... thx!

Mar 4, 2023 at 2:38:00 PM
Web Server Warning HTTP 503 error for request /apple-touch-icon-114x114.png from 192.168.100.127
Web Server Warning HTTP 503 error for request /apple-touch-icon-120x120.png from 192.168.100.127
Sent INSTEON "living/fire lamp" on

Mar 4, 2023 at 2:38:24 PM
Web Server Warning HTTP 503 error for request /apple-touch-icon-76x76.png from 192.168.100.127
Web Server Warning HTTP 503 error for request /apple-touch-icon-114x114.png from 192.168.100.127
Web Server Warning HTTP 503 error for request /apple-touch-icon-60x60.png from 192.168.100.127
Web Server Warning HTTP 503 error for request /apple-touch-icon-72x72.png from 192.168.100.127
Sent INSTEON "living/fire lamp" off

[matt (support)]

Those warnings are a bit odd – I'm not sure what is causing them. If I try to access one of those images directly from Safari on my Indigo Server Mac it loads without a problem (no Event Log warning/error and the image shows). Does it for you as well?

http://localhost:8176/apple-touch-icon-114x114.png

hm. no. the only apple touch icon that shows up in a full volume search is one from 2009 in an old backup...?

what exact folder path should it be? i looked through whole web assets ƒ...

thx matt!

this did though, no prob.

http://192.168.100.100:8000/apple-touch ... 14x114.png. that's my lan access path. (as does http://localhost:8000/apple-touch-icon-114x114.png on server)

got me this -- below.

does this mean the webpage is trying to access a wrong asset ƒ?

[matt (support)]

I think my URL example didn't work just because it has the default port of 8176 but you have a port override of 8000. (historical fact: default port Indigo used was 8000 a very long time ago, so you may have actually had the default port but the default is now different so you now have a custom port number ).

Therefore, I think it is working correctly (at least most of the time) and the errors you saw were just transient. If you see it (those warnings in the log) a lot or find a pattern as to when it occurs let me know.

haha ok.

i remember when it changed (?) to 1176 and 8176, i think i purposely changed it back to 8000 internally/lan and to a bespoke port for wan access.

thanks matt, much appreciated.