Reactor error (openLuup)

Having a reactor error in openluup install.

was adding reactors, and had to add manually because backup/restore not working.

any reactor modules added after than point don’t work.

plugin was already upgraded; won’t fix with restart.

Error:

an error occurred while displaying the javascript tab. devid: 0-21 err:s.match is not a function
stack:TypeError: s.match is not a function
at isEmpty (J_ReactorSensor_UI7.js:164:43)
at loadConfigData (J_ReactorSensor_UI7.js:269:10)
at getConfiguration (J_ReactorSensor_UI7.js:413:4)
at initModule (J_ReactorSensor_UI7.js:623:3)
at Object.doStatusPanel (J_ReactorSensor_UI7.js:1475:10)
at eval (eval at _deviceDrawControlPanelTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3622:20), :1:15)
at _deviceDrawControlPanelTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3622:20)
at _deviceDrawControlPanelOneTabContent (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3666:8)
at _displayActiveDeviceTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3695:4)
at _defereddisplay (http://172.16.1.133:3480/J_ALTUI_uimgr.js:4233:5)

Did you hard-refresh your browser?

furst thing. when i cleaned, and purged, system crashed. attempting to restart openluup

restarted.

still with issues on all subsequent reactors. ver 3.3.

This is a known issue. Install the hotfix files on this thread: Hotfixes for Reactor 3.3

Still happening.

Applied hotfix version to AltUI install. It updated.

Did hard refresh.

Still happening with new devices. Deleted non-working Reactors that weren’t assigned to anything, then recreated new ones, same issue.

“an error occurred while displaying the javascript tab. devid: 0-24 err:Unexpected token o in JSON at position 1
stack:SyntaxError: Unexpected token o in JSON at position 1 etc”

Latest AltUI, running Reactor hotfix. Please advise. Only happening on new Reactors, have 2 reactors working fine, plus ‘reactor’ itself.

That’s a different error. Can I have the whole message?

Yes sir!

an error occurred while displaying the javascript tab. devid: 0-24 err:Unexpected token o in JSON at position 1
stack:SyntaxError: Unexpected token o in JSON at position 1
at JSON.parse ()
at loadConfigData (J_ReactorSensor_UI7.js:272:18)
at getConfiguration (J_ReactorSensor_UI7.js:414:4)
at initModule (J_ReactorSensor_UI7.js:624:3)
at Object.doStatusPanel (J_ReactorSensor_UI7.js:1476:10)
at eval (eval at _deviceDrawControlPanelTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3622:20), :1:15)
at _deviceDrawControlPanelTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3622:20)
at _deviceDrawControlPanelOneTabContent (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3666:8)
at _displayActiveDeviceTab (http://172.16.1.133:3480/J_ALTUI_uimgr.js:3695:4)
at _defereddisplay (http://172.16.1.133:3480/J_ALTUI_uimgr.js:4233:5)

OK. Grab the hotfix branch again and see how that goes.

Appears fixed. Normal control panel options! Thank you!

So, after the above, I’m using reactor to reflect the status of a virtual switch to trigger a somfy shade of which I have many. Despite using the correct device, which is reflecteing the correct attribute in altui after all the above), I do not get the set target activity to up, down or stop, as opposed to the other 3 reactors which have it listed. the properties of all are the same (urn:schemas-micasaverde-com:device:WindowCovering:1) which are being brought over via vera bridge. what could be the problem? if I create a scene, and then call the scene, the scene displays the correct device type.

Logic Summary?

Hold up… up, down and stop are not valid values for SetTarget. SetTarget only takes on and off (0,1).

The up, down, and stop are in the WindowCovering1 service. You need to look further down the dropdown list in the list of actions.