Reactor-Editor / Reactor-ui-Status Errors

[RogerO]

My ESP32 board arrives today and I will be doing something very similar to what you are looking for. Will let you know how it goes. I have been using DS18B20's in RPI's for quite a while so this is first foray into ESP boards.

[RogerO]

Just looked at Patrick's MQTT add on and it requires an external MQTT broker, so not quite plug and play.

[a-lurker]

There's a plugin for the OW-server that works great. Been using it for years.

https://smarthome.community/topic/247/list-of-plugins-available-at-the-alternative-app-store?_=1642227742093

[Talisker]

@rogero Your experience would be very interesting to hear about. Is the ESP board limited to a specific number of one wire devices?

[Talisker]

This post is deleted!

[Talisker]

@a-lurker Does the Plugin work in U17?

[a-lurker]

@talisker said in OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality:

@a-lurker Does the Plugin work in U17?

Pretty sure it does - I'm using the plugin under openLuup but I used to have it running on a Vera.

[Talisker]

@a-lurker I took the plunge and purchased an OW server (Ethernet). The system is up an running with my one wire connected devices. I am however having a little problem with the OWServer Vera app on my Vera Plus. On the face of it the app is working and picking up the one wire devices:

However, when I go into the 'Add Devices' menu there are none of the sensors shown - the page is blank:

I did a bit of googling and found the following information: https://github.com/dbemowsk/OW-SERVER_Emulator

I did try uploading the J_OWServer.js file as @dbemowsk suggested, but it did not solve the problem I have with vera not showing the one wire devices. I have no idea what he is explaining is the problem with the original files from the app store.

I appreciate that you don't have a Vera Plus, but if you could make any suggestions as to what to try I'd appreciate any input you can offer!

I guess that unless I get up an running I will need to find another route to pulling the values into MSR.

[a-lurker]

Pretty sure you can get it to work. Use the most recent version of the plugin here. The plugin in the MIOS App Store is well out of date.

Your screen capture can be interpreted as the following - how many devices to you have attached?

Devices: 14
Chn 1 error count: 0
Chn 2 error count: 0
Chn 3 error count: 0
EDS OW server web page

You need to do a few luup engine restarts to get the child devices to show up.

You can use AltUi to install the plugin from the Alt App Store: see More->AppStore. Not using AltUI? It's highly recommended.

If I remember correctly, all the one wire devices are created automatically on first run of the plugin. So on my dashboard it says "No new devices to add" as they have already been added.

"J_OWServer.js file as @dbemowsk suggested" - this bug has already been resolved in the plugin at the link above, so please use the J_OWServer.js file that comes with the Alt App store plugin.

Many of the plugins in the MIOS App Store are hopelessly out of date - refer to the Alt App store list. for updated versions.

All else fails; check the log - once again this can be seen using AltUi -> Misc -> OS Command --> Tail Logs

[Talisker]

@a-lurker said in OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality:

Pretty sure you can get it to work. Use the most recent version of the plugin here. The plugin in the MIOS App Store is well out of date.

Noted. I rolled back to my vera backup prior to my attempts yesterday. I then downloaded the files from the github link and loaded into my vera.
I had to set up the OW Server device manually (troubles with ALTUI - see below).

Your screen capture can be interpreted as the following - how many devices to you have attached?

Devices: 14
Chn 1 error count: 0
Chn 2 error count: 0
Chn 3 error count: 0
EDS OW server web page

I get the following now:

You can see that it does not show the three channels now, but it confirms that I have fourteen devices (which is correct).

You need to do a few luup engine restarts to get the child devices to show up.

I have done numerous Luup engine restarts, but the devices still do not show up in 'Add Devices'.

You can use AltUi to install the plugin from the Alt App Store: see More->AppStore. Not using AltUI? It's highly recommended.

I did install ALTUI, but I was not able to install OW-Server using it. The first time I pressed the install button it thought about it for a few seconds but did not install the OW Server device. Now when I press it I get an error:

If I remember correctly, all the one wire devices are created automatically on first run of the plugin. So on my dashboard it says "No new devices to add" as they have already been added.

The have not been created, possibly because there is an error.....

"J_OWServer.js file as @dbemowsk suggested" - this bug has already been resolved in the plugin at the link above, so please use the J_OWServer.js file that comes with the Alt App store plugin.

Many of the plugins in the MIOS App Store are hopelessly out of date - refer to the Alt App store list. for updated versions.

All else fails; check the log - once again this can be seen using AltUi -> Misc -> OS Command --> Tail Logs

I get the following error in the Alturi app (similar in the vera UI) and Vera log:

You can see from the vera log (http://192.168.68.103/cgi-bin/cmh/log.sh?Device=LuaUPnP) the requisite jasn.lua library file cannot be found. Now I am hoping this is all I need (deposited in the right place in vera) to get the OW Server device up an running. So, where do I get this file and where do I put it (please be polite!!).![768cd707-8727-4ce9-a06e-717661411e31-image.png]

[a-lurker]

Looking at the log it says its missing json.lua. This message tells me you are still running the old plugin from the MIOS store.

Not sure what hardware you are using? The old Vera 3 can't access the Alt App store as the comms library is too antiquated. Regardless you can just download the files from GitHub and overwrite the mios ones. Use the Vera user interface (ie not directly with SSH) as Vera compresses the files when you upload them via the UI. In Vera 3 they end up in etc\cmh-ludl as "lzo" files

The latest version of the plugin looks for ten different possibly available json libraries - see this GitHub link.

If you look in (a Vera 3) /usr/lib/lua you may find dkjson.lua, which in this case is a sym link to /mios/usr/lib/lua/dkjson.lua

You can use the command in AltUI --> Misc --> OsCommand -->Find Json to see what might be available to you. Note that this search doesn't always find what's available. But I would expect dkjson.lua is available and will be found and used by the latest version of the plugin.

[Talisker]

@a-lurker Next instalment (sorry!). I re-downloaded the files from Github following the link you kindly provided in your previous post. There were three files plus a number of other files in a separate folder. I copied all the files from the .zip file into a folder on my desktop and uploaded them to my vera plus and tried a number of luup reloads. Was that correct - i.e. should I have uploaded all files (including the ones in the folder) as separate files and not in the actual folder?

Anyhow, something happened because now I get the following (note I have 14 devices:

and in 'Add Devices'

So I did not see the previous result before. But you can see that my devices are not being found. I have looked in the luup logs and there are no errors I can see. I also cannot see the device number listed in the log. I don't know if that means that anything.

Thanks.

[a-lurker]

Not quite right. You only need the files in the folder called "Luup_device". When uploaded they should not be uploaded as a folder. Here is the list of files that need to be directly uploaded:

S_OWServer.xml
D_OWPressureSensor.json
D_OWPressureSensor.xml
D_OWServer.json
D_OWServer.xml
I_OWServer.xml
J_OWServer.js
L_OWServer.lua
S_OWPressureSensor.xml

Did you check for a json library using AltUI? Because you will need one of some description.

[Talisker]

@a-lurker I meticulously installed all the files in the folder only as you stated. I trawled the luup log and found the following. It appears that the plugin does see my 14 one wire temperature devices, but for some reason will not let me set them up as devices:

Could this be a fundamental problem with my particular vera plus, because I have to install the device manually. It will not install via ALTUI?

[a-lurker]

Looks promising - hopefully you should see under the AltUI variables tab "DebugEnabled". You can set it to one and restart the Luup engine and get more log info. You should also see "PluginVersion", which should probably be 0.52? No mention on whether AltUI detected a json library?

"Could this be a fundamental problem with my particular vera plus, because I have to install the device manually. It will not install via ALTUI?" No don't think so.

[Talisker]

@a-lurker Sorry, yes the AltUI did detect a json library (or at least I think so):

Yes, it looks like the PluginVersion os 0.52:

One Log:

50 01/22/22 13:06:03.101 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
50 01/22/22 13:06:03.399 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: New device found F0000801B4209010 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found A7000801B4562810 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found 88000801B4467410 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found 2E000801B423AC10 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 03000801B43A3210 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 84000801B4368A10 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 2E000801B44B7910 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found C8000801B45C5510 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 12000801B43A2F10 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 33000801B442DF10 DS18S20 <0x7155a520>
50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found B50000021D3DE028 DS18B20 <0x7155a520>
50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 3E0000021D47F028 DS18B20 <0x7155a520>
50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found FB0000021D4C4628 DS18B20 <0x7155a520>
50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 080000021D6EAE28 DS18B20 <0x7155a520>
50 01/22/22 13:06:03.404 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
50 01/22/22 13:06:03.404 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520>
06 01/22/22 13:06:04.100 Device_Variable::m_szValue_set device: 911 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1642856762 now: 1642856764 #hooks: 0 upnp: 0 skip: 0 v:0x154d730/NONE duplicate:0 <0x7695a520>
06 01/22/22 13:06:04.101 Device_Variable::m_szValue_set device: 911 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 1 upnp: 0 skip: 0 v:0x154d600/NONE duplicate:0 <0x7695a520>
50 01/22/22 13:06:06.100 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
01 01/22/22 13:06:06.342 IOPort::Connect connect -1 192.168.68.111:60128 <0x6de60520>
50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
50 01/22/22 13:06:06.400 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
50 01/22/22 13:06:06.400 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520>
50 01/22/22 13:06:09.100 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
50 01/22/22 13:06:09.398 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
50 01/22/22 13:06:09.398 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520

Any clues there?

[a-lurker]

All looks fine to me. It's now got a json library and it's reading from the one wire server and finding all the devices. It's also the correct plugin version number. Have you checked the "No room" for see if the child temperature sensors have turned up. If none - need to do a luup engine restart. It can take a while before actual temperatures are displayed ( I think it works out to 45 seconds). They then update at the default rate of every 20 seconds.

[Talisker]

@a-lurker So I think we proved that I have the correct plugin version, the plugin is correctly set up as the one wire devices IDs are listed in the logs. What is not happening is the devices (14 No. in my case) are not showing up in add devices (similar in ALTUI):

I have tried multiple luup re-loads and vera restarts, but the devices just aren't showing. I feel I am so close, yet not quite at the finish line! Is there anything else I can do or try? Thanks.

[a-lurker]

This post is deleted!

[a-lurker]

This post is deleted!