Release pimatic-raspbee@0.1.6

---

My fresh system gives also the same error.
Now i can debug it, without the need for you to dive into the inspect.

@pedder said in Release pimatic-raspbee@0.1.6:

raspbee-switch

If found the error. I was pointing to the app files in pimatic-raspbee and not pimatic-raspbee-plus. Thats why it worked on my test system and not on the refresh one.
I fixed it in 0.1.1

That seems looking good!
I will now re-discover the warning and the smart-plug, which I learned in the meantime.

Let’s see …

ok, both devices added and working.
the plug still w/o the values, but I remember, that for this I will have to update deconz, which I already did on my Dev system, but not on the Prod

well, sorry for not coming back earlier, but I’m struggeling the whole time with the Blitz Plug.
It’s not willing to learn to my Prod ConBee II / deCONZ environment.

Reseted it now mutliple times, kicked it out explicitly from the Dev environment, butting nothing helps.

will continue here …

OK, got this thing now running - wow
Had to do a factory reset via the Dev deCONZ gui and then directly kicked it out there.
And then it learned to the Prod environment, what an effort …

However, now it is switching, but it seems to be, that no data is shown
I shortly checked it via the deconz gui, but there the values are shown.

Do you have an idea on this?
Search in the log now becomes really complicated, as there is tonnes of other stuff now in …

I already played around with the sensor IDs, as on the Dev system, I used 2 and 3. But now, when setting 3, an error occures: ‘Device with ID: 3 not found’

Another point: I tried to trigger the RaspBeeWarning device buttons by rule, but wasn’t able to find the right syntax. Could you please advise?

The rules action commands are ’ set raspbee <rasp device id> [off | silent | sound | long] ’

What is the device class you use for the Blizz plug?

Hi, here comes the whole config. After scanning the device I was also thinking, if on my Dev system, the ID(s) (2+3) came along automatically? I think that was the case there, as otherwise I wouldn’t have known them.
Now on the Prod the IDs didn’t came along and I put them in manually and ID No 3 produced an error:

Thanks again for the syntax, I was again testing with push, press, …

and, over night I got again some frontend errors, but which currently seems having no further impact:

01:36:21h
error [pimatic-mobile-frontend]: Client error: Unable to process binding "if: function (){return !$root.isGroupCollapsed($data,{id:'$ungrouped'}) }"
Message: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$data.getUngroupedDevices(),afterRender:$data.afterRenderDevice} }"
Message: null is not an object (evaluating 'n[a]')
01:36:34h (2x)
error [pimatic-mobile-frontend]: Client error: TypeError: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$data.getUngroupedDevices(),afterRender:$data.afterRenderDevice} }"
Message: null is not an object (evaluating 'n[a]')
01:37:09h
error [pimatic-mobile-frontend]: Client error: Unable to process binding "if: function (){return 
!$root.isGroupCollapsed($data,{id:'$ungrouped'}) }"
Message: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$data.getUngroupedDevices(),afterRender:$data.afterRenderDevice} }"
Message: null is not an object (evaluating 'n[a]')

in the morning at short before 08:00 the same happened again

And that syntax is also for the cover: set raspbee < device> open | stop | close

You are using a different deconz / conbee for your prod system.
If so, the device ID and sensor ID’s could be different.

Can you delete the device, do a discovery and port the debug of the Blitzz discovery ?

will do …
below I meant the senosr IDs, regarding different device IDs, that’s clear

I assume these errors are the result of you using the gui?
Can you check the ‘red !’ log, when this error occurs?
I remembered that (re)starting was problematic when these error occurs.
If you want you should try a restart.

ok, not that easy to find in the log amongst >45 ZigBee devices
But I guess, that it should be:

17:28:37.992 [pimatic-raspbee-plus] debug:>  '5':
17:28:37.992 [pimatic-raspbee-plus] debug:>   { etag: '17bc9cf280a39798ed4b9e9c76f232b1',
17:28:37.992 [pimatic-raspbee-plus] debug:>     hascolor: false,
17:28:37.992 [pimatic-raspbee-plus] debug:>     lastannounced: '2021-03-19T23:49:19Z',
17:28:37.992 [pimatic-raspbee-plus] debug:>     lastseen: '2021-03-20T16:24Z',
17:28:37.992 [pimatic-raspbee-plus] debug:>     manufacturername: '_TZ3000_g5xawfcq',
17:28:37.992 [pimatic-raspbee-plus] debug:>     modelid: 'TS0121',
17:28:37.992 [pimatic-raspbee-plus] debug:>     name: 'BlitzPlug01',
17:28:37.992 [pimatic-raspbee-plus] debug:>     state: { alert: 'none', on: false, reachable: true },
17:28:37.992 [pimatic-raspbee-plus] debug:>     swversion: null,
17:28:37.992 [pimatic-raspbee-plus] debug:>     type: 'Smart plug',
17:28:37.992 [pimatic-raspbee-plus] debug:>     uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' },

Regarding the gui (restarting) you might be right for 01:37, as I have tested around here since something like that.
… and in the morning, that might have been the time, when I went up and firstly loaded the frontend via my smartphone, that far, yes that really might have been the reason.

and you see, it’s completely empty:

The log from the Blitz smartplug looks ok.
But there should be a sensor and after that a lights part after discovery.
The debug log is starting with 'sensor list … and after that starting with 'lights list …

Yes i see the sensor part is empty.
You may mail the complete debug log after discovery

ok, I will do it again and search for it.

Meanwhile quickly ran to the kitchen where I normally do have a VIS frontend running on a 10" wall-tablet.
Quickly switched there to the Pimatic frontend, but now the frontend errors didn’t occur, however, …?

However …?

however, as I do not have a clue about

ok, new scan. Hope that fits fo you:

17:46:23.632 [pimatic-raspbee-plus] debug:>   { id: '5',
17:46:23.632 [pimatic-raspbee-plus] debug:>     lastannounced: '2021-03-19T23:49:19Z',
17:46:23.632 [pimatic-raspbee-plus] debug:>     lastseen: '2021-03-20T16:46Z',
17:46:23.632 [pimatic-raspbee-plus] debug:>     manufacturername: '_TZ3000_g5xawfcq',
17:46:23.632 [pimatic-raspbee-plus] debug:>     modelid: 'TS0121',
17:46:23.632 [pimatic-raspbee-plus] debug:>     name: 'BlitzPlug01',
17:46:23.632 [pimatic-raspbee-plus] debug:>     swversion: null,
17:46:23.632 [pimatic-raspbee-plus] debug:>     type: 'Smart plug',
17:46:23.632 [pimatic-raspbee-plus] debug:>     uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' },
17:46:23.632 [pimatic-raspbee-plus] debug:>  e: 'changed',
17:46:23.632 [pimatic-raspbee-plus] debug:>  id: '5',
17:46:23.632 [pimatic-raspbee-plus] debug:>  r: 'lights',
17:46:23.632 [pimatic-raspbee-plus] debug:>  t: 'event',
17:46:23.632 [pimatic-raspbee-plus] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' }
...
17:47:23.681 [pimatic-raspbee-plus] debug: new message received
17:47:23.682 [pimatic-raspbee-plus] debug: { attr:
17:47:23.682 [pimatic-raspbee-plus] debug:>   { id: '5',
17:47:23.682 [pimatic-raspbee-plus] debug:>     lastannounced: '2021-03-19T23:49:19Z',
17:47:23.682 [pimatic-raspbee-plus] debug:>     lastseen: '2021-03-20T16:47Z',
17:47:23.682 [pimatic-raspbee-plus] debug:>     manufacturername: '_TZ3000_g5xawfcq',
17:47:23.682 [pimatic-raspbee-plus] debug:>     modelid: 'TS0121',
17:47:23.682 [pimatic-raspbee-plus] debug:>     name: 'BlitzPlug01',
17:47:23.682 [pimatic-raspbee-plus] debug:>     swversion: null,
17:47:23.682 [pimatic-raspbee-plus] debug:>     type: 'Smart plug',
17:47:23.682 [pimatic-raspbee-plus] debug:>     uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' },
17:47:23.682 [pimatic-raspbee-plus] debug:>  e: 'changed',
17:47:23.682 [pimatic-raspbee-plus] debug:>  id: '5',
17:47:23.682 [pimatic-raspbee-plus] debug:>  r: 'lights',
17:47:23.682 [pimatic-raspbee-plus] debug:>  t: 'event',
17:47:23.682 [pimatic-raspbee-plus] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' }
...
17:47:23.681 [pimatic-raspbee-plus] debug: new message received
17:47:23.682 [pimatic-raspbee-plus] debug: { attr:
17:47:23.682 [pimatic-raspbee-plus] debug:>   { id: '5',
17:47:23.682 [pimatic-raspbee-plus] debug:>     lastannounced: '2021-03-19T23:49:19Z',
17:47:23.682 [pimatic-raspbee-plus] debug:>     lastseen: '2021-03-20T16:47Z',
17:47:23.682 [pimatic-raspbee-plus] debug:>     manufacturername: '_TZ3000_g5xawfcq',
17:47:23.682 [pimatic-raspbee-plus] debug:>     modelid: 'TS0121',
17:47:23.682 [pimatic-raspbee-plus] debug:>     name: 'BlitzPlug01',
17:47:23.682 [pimatic-raspbee-plus] debug:>     swversion: null,
17:47:23.682 [pimatic-raspbee-plus] debug:>     type: 'Smart plug',
17:47:23.682 [pimatic-raspbee-plus] debug:>     uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' },
17:47:23.682 [pimatic-raspbee-plus] debug:>  e: 'changed',
17:47:23.682 [pimatic-raspbee-plus] debug:>  id: '5',
17:47:23.682 [pimatic-raspbee-plus] debug:>  r: 'lights',
17:47:23.682 [pimatic-raspbee-plus] debug:>  t: 'event',
17:47:23.682 [pimatic-raspbee-plus] debug:>  uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01' }

The first time when you load the gui after the gui is changed, this type of error can happen.
Without clear cache/refresh, the browser cache holds the ‘old code’ and then these type of errors occur. After clear/refresh the browser code is updated and the error is gone.

When there’s an error in the app code, you get the same type of error, but this error is structural.